PTechCharge Component
Properties Methods Events Configuration Settings Errors
The PTechCharge component is used to authorize credit card transactions with the Paymentech NetConnect system on the Tampa platform. This component supports Direct Marketing, e-Commerce, and Retail environments, and allows for simple, direct, secure communication to the Paymentech TLS/SSL gateway through a standard Internet connection. This component can be integrated into web pages or stand-alone Point Of Sale applications. Because all TLS/SSL communications are handled inside the component, any application or web page can be deployed without the need for expensive dedicated TLS/SSL servers.
Syntax
nsoftware.InPayDirect.Ptechcharge
Remarks
Setting up the component and authorizing a transaction is easy. First, set the MerchantNumber, TerminalNumber, ClientNumber, UserId, and Password with the information given to you when you signed up for Paymentech service. You should also set your IndustryType and PINCapability at this time.
After the merchant information is setup, you may enter transaction data. When the Credit Card's EntryDataSource is Manually Entered, the merchant should fill the Number, ExpMonth, and ExpYear fields. Address Verification Service (AVS) data may be sent by filling the CustomerAddress and CustomerZip properties. For any other EntryDataSource , the MagneticStripe field should be filled. In addition, the TransactionAmount should be set with the total amount for the transaction, including any taxes.
Now simply call the Sale or AuthOnly method to send the authorization to the Paymentech Server.
The result of the authorization request will be stored in the Response property. The Code field will contain the status of the request and the Text field will contain the human-readable response message. The contents of the Response should be logged after a successful transaction.
Once an authorization request is approved, one of three things happen. If you are using the Host Capture SettlementMode, and your Paymentech account is setup with the Host Auto Close feature, you need take no further action. The host will close the current open batch at a designated time each day. This means that there is no end of day batch processing required from the merchant. In order for the merchant's batch to be included in the Paymentech Host Auto Close process, the merchant parameter file on the host must indicate that the merchant is Auto Close. Without this flag being set, the merchant's transactions must be settled with a Manual Batch Release.
If you are using the Host Capture SettlementMode, and your Paymentech account not setup with Host Auto Close, then after an authorization is approved the transaction is added to the current batch on the Paymentech Server, and the money in the customer's account is blocked and tagged for the merchant. The transaction must go through the Manual Batch Release Settlement process in order for the blocked money to be transferred to the merchant's account. To release a batch for settlement, please see the PTechHostSettle component.
If you are using the Terminal Capture SettlementMode, you must store the XML aggregate returned from the GetDetailAggregate method and submit it at the end of the day in a manual batch settlement. A detail aggregate for each authorized transaction must be sent in a batch using the PTechManualSettle component. A transaction that has been authorized and then subsequently voided with this component must NOT be added to the batch settlement, and must not be submitted with the PTechManualSettle component. Any transaction not submitted with PTechManualSettle will eventually time out, and the block on the customer's card will be removed (essentially, you may void transactions by simply not sending them in the batch settlement). The Terminal Capture SettlementMode is required for the Restaurant and Hotel IndustryTypes. This is because both IndustryTypes will generally have additional charges added on to the original authorization (for example: a tip for your server, or a drink from the hotel bar charged to your room). Other IndustryTypes may benefit from this functionality as well, but if you do not require your transactions to be authorized for one amount and then settled for a different amount, it is highly recommended you use the much simpler Host Capture SettlementMode.
Note that a transaction authorized in the Host Capture SettlementMode MUST be released for settlement using the PTechHostSettle component. It cannot be added to a manual batch settlement using the PTechManualSettle component. Doing so will result in charging the customer twice! Likewise, transactions authorized with SettlementMode set to Terminal Capture cannot be released using the PTechHostSettle component, because no record of the transaction has been stored on the Paymentech Server.
Also note that you cannot mix Host Capture and Terminal Capture SettlementModes on the same MerchantNumber / TerminalNumber pair. Contact Paymentech to setup your merchant account for Terminal Capture.
Property List
The following is the full list of the properties of the component with short descriptions. Click on the links for further details.
Card | Contains the customer's credit card information. |
ClientNumber | Merchant configuration property, assigned by Paymentech. |
CustomerAddress | The customer's billing address. |
CustomerZip | Customer's zip code (or postal code if outside of the USA). |
DebitCashBack | Optional cash back amount for debit transactions. |
DebitKSN | Clear-text Key Sequence Number, used for Debit transactions. |
DebitPIN | DUKPT DES encrypted PIN block, used for Debit transactions. |
DuplicateChecking | Indicates whether duplicate checking is enabled. |
ECI | Electronic Commerce Indicator. |
GoodsIndicator | Indicates the type of goods being sold by an e-Commerce merchant. |
GratuityAmount | Gratuity amount for restaurant industry transactions. |
IndustryType | Determines the merchant's industry type. |
InvoiceNumber | Merchant-generated invoice number. |
Level2Data | Supplies extra information for Commercial or Purchasing cards. |
MerchantNumber | A unique number used to identify the merchant, assigned by Paymentech. |
Password | Password for authentication with the NetConnect Server . |
PINCapability | Indicates if the terminal device supports a PIN pad. |
POSRetrievalNumber | Merchant-generated reference number, used for reversals. |
Proxy | A set of properties related to proxy access. |
Response | Contains the response to an authorization. |
SequenceNumber | Sequence number of the transaction. |
Server | The URL for the PaymenTech NetConnect server. |
ServerNumber | Used for restaurant transactions: Id number of the server making the transaction. |
SettlementMode | Indicates whether the component uses Paymentech's Host Capture or Terminal Capture system. |
SSLAcceptServerCert | Instructs the component to unconditionally accept the server certificate that matches the supplied certificate. |
SSLCert | The certificate to be used during SSL negotiation. |
SSLServerCert | The server certificate for the last established connection. |
TerminalNumber | Terminal number assigned by Paymentech. |
Timeout | A timeout for the component. |
TransactionAmount | Purchase amount for an authorization. |
UserId | UserId for authentication with the NetConnect Server . |
Method List
The following is the full list of the methods of the component with short descriptions. Click on the links for further details.
AuthOnly | Sends an AuthOnly transaction to the host. |
Capture | Sends a capture transaction to the PaymenTech Server. |
Config | Sets or retrieves a configuration setting . |
Credit | Credits a cardholder's account. |
GetDetailAggregate | Returns an aggregate containing details of this transaction, which is then used for manual settlement. |
Interrupt | Interrupt the current method. |
Reset | Clears all properties to their default values. |
Sale | Sends a Sale transaction to the host. |
VoidTransaction | Voids a transaction in the current batch. |
Event List
The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.
DataPacketIn | Fired when receiving a data packet from the transaction server. |
DataPacketOut | Fired when sending a data packet to the transaction server. |
Error | Information about errors during data delivery. |
SSLServerAuthentication | Fired after the server presents its certificate to the client. |
SSLStatus | Shows the progress of the secure connection. |
Configuration Settings
The following is a list of configuration settings for the component with short descriptions. Click on the links for further details.
CustomerDefinedData | Additional transaction identification data. |
ECommerceIndicator | Used to specify the indicator describing the type of internet transaction. |
IndustryTypes | Industry Information. |
HostProcessingTypes | Host Processing Platform. |
EMVSupportTypes | EMV Support. |
PeripheralTypes | Currently installed and enabled peripheral devices. |
ComplianceCertificationTypes | Compliance Certification. |
CAVV | AuthenticationCAVV data from a ThreeDSecure authentication. |
XID | TransactionId from a 3D Secure authentication. |
AllowPartialAuths | Indicates whether partial authorizations are to be supported. |
DeviceID | Used to specify the device user, retail lane, fuel pump, etc. to identify where the transaction originated from. |
RecurringSubmissionType | Specifies whether the payment is the first or subsequent submission of a recurring transaction. |
RequestBalanceInfo | Specifies whether to request balance information. |
ResponseBalanceAmount1 | Credit Prepaid Available Balance #1. |
ResponseBalanceAmount2 | Credit Prepaid Available Balance #2. |
ResponseBalanceCurrency1 | Currency code for ResponseBalanceAmount1. |
ResponseBalanceCurrency2 | Currency code for ResponseBalanceAmount2. |
ResponsePartialAuthCode | The authorization code for a transaction where partial authorizations are supported. |
Healthcare | Indicates this is a Healthcare auto-substantiation transaction. |
ClinicItems | Total amount of Clinic or Other qualified medical items for Healthcare auto-substantiation. |
DentalItems | Total amount of Dental items for Healthcare auto-substantiation. |
PrescriptionItems | Total amount of Prescription/Rx items for Healthcare auto-substantiation. |
VisionItems | Total amount of Vision or Optical items for Healthcare auto-substantiation. |
MedicalItemsTotal | Sum total of the above medical items. |
SystemInformation | System Information field for Batch Inquiry and Release transactions. |
SettlementMode | Indicates whether the component uses Paymentech's Host Capture or Terminal Capture system. |
ResponsePOSRetrievalNumber | POS Retrieval Number sent in the request, echoed back in the response. |
EMVData | The EMV data returned from a Pin Pad after reading an EMV card. |
EMVEntryDataSource | The EMV Data Entry Source (DES). |
ResponseEMVData | The response EMV data. |
ResponseEMVCardAuthCode | The ChaseNet and Visa card authentication results code. |
ResponseEMVDownloadIndicator | Whether EMV parameters should be updated. |
EMVOnlinePIN | DUKPT DES encrypted PIN block for EMV Online PIN transactions. |
EMVOnlineKSN | Clear-text Key Sequence Number for EMV Online PIN transactions. |
AcceptEncoding | Used to tell the server which types of content encodings the client supports. |
AllowHTTPCompression | This property enables HTTP compression for receiving data. |
AllowIdenticalRedirectURL | Allow redirects to the same URL. |
Append | Whether to append data to LocalFile. |
Authorization | The Authorization string to be sent to the server. |
BytesTransferred | Contains the number of bytes transferred in the response data. |
EncodeURL | If set to true the URL will be encoded by the component. |
FollowRedirects | Determines what happens when the server issues a redirect. |
GetOn302Redirect | If set to true the component will perform a GET on the new location. |
HTTPVersion | The version of HTTP used by the component. |
IfModifiedSince | A date determining the maximum age of the desired document. |
KeepAlive | Determines whether the HTTP connection is closed after completion of the request. |
MaxRedirectAttempts | Limits the number of redirects that are followed in a request. |
OtherHeaders | Other headers as determined by the user (optional). |
ProxyAuthorization | The authorization string to be sent to the proxy server. |
ProxyAuthScheme | The authorization scheme to be used for the proxy. |
ProxyPassword | A password if authentication is to be used for the proxy. |
ProxyPort | Port for the proxy server (default 80). |
ProxyServer | Name or IP address of a proxy server (optional). |
ProxyUser | A user name if authentication is to be used for the proxy. |
TransferredDataLimit | The maximum number of incoming bytes to be stored by the component. |
TransferredHeaders | The full set of headers as received from the server. |
UseChunkedEncoding | Enables or Disables HTTP chunked encoding for transfers. |
ChunkSize | Specifies the chunk size in bytes when using chunked encoding. |
UserAgent | Information about the user agent (browser). |
KerberosSPN | The Service Principal Name for the Kerberos Domain Controller. |
ConnectionTimeout | Sets a separate timeout value for establishing a connection. |
FirewallAutoDetect | Tells the component whether or not to automatically detect and use firewall system settings, if available. |
FirewallHost | Name or IP address of firewall (optional). |
FirewallPassword | Password to be used if authentication is to be used when connecting through the firewall. |
FirewallPort | The TCP port for the FirewallHost;. |
FirewallType | Determines the type of firewall to connect through. |
FirewallUser | A user name if authentication is to be used connecting through a firewall. |
KeepAliveTime | The inactivity time in milliseconds before a TCP keep-alive packet is sent. |
KeepAliveInterval | The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received. |
Linger | When set to True, connections are terminated gracefully. |
LingerTime | Time in seconds to have the connection linger. |
LocalHost | The name of the local host through which connections are initiated or accepted. |
LocalPort | The TCP port in the local host where the component binds. |
MaxLineLength | The maximum amount of data to accumulate when no EOL is found. |
MaxTransferRate | The transfer rate limit in bytes per second. |
RecordLength | The length of received data records. |
TCPKeepAlive | Determines whether or not the keep alive socket option is enabled. |
UseIPv6 | Whether to use IPv6. |
TcpNoDelay | Whether or not to delay when sending packets. |
TLS12SignatureAlgorithms | Defines the allowed TLS 1.2 signature algorithms when UseManagedSecurityAPI is True. |
ReuseSSLSession | Determines if the SSL session is reused. |
SSLCipherStrength | The minimum cipher strength used for bulk encryption. |
SSLEnabledProtocols | Used to enable/disable the supported security protocols. |
SSLProvider | The name of the security provider to use. |
SSLSecurityFlags | Flags that control certificate verification. |
OpenSSLCADir | The path to a directory containing CA certificates. |
OpenSSLCAFile | Name of the file containing the list of CA's trusted by your application. |
OpenSSLCipherList | A string that controls the ciphers to be used by SSL. |
OpenSSLPrngSeedData | The data to seed the pseudo random number generator (PRNG). |
AbsoluteTimeout | Determines whether timeouts are inactivity timeouts or absolute timeouts. |
FirewallData | Used to send extra data to the firewall. |
InBufferSize | The size in bytes of the incoming queue of the socket. |
OutBufferSize | The size in bytes of the outgoing queue of the socket. |
CodePage | The system code page used for Unicode to Multibyte translations. |