PTechCanadianDebit Class
Properties Methods Events Config Settings Errors
The PTechCanadianDebit class is used to authorize face-to-face Interac (Canadian) debit card transactions with the Paymentech NetConnect system on the Tampa platform. This class allows for simple, direct, secure communication to the Paymentech TLS/SSL gateway through a standard Internet connection. This class can be integrated into web pages or stand-alone Point Of Sale applications. Because all TLS/SSL communications are handled inside the class, any application or web page can be deployed without the need for expensive dedicated TLS/SSL servers.
Class Name
DPaymentsSDK_PTechCanadianDebit
Procedural Interface
dpaymentssdk_ptechcanadiandebit_open(); dpaymentssdk_ptechcanadiandebit_close($res); dpaymentssdk_ptechcanadiandebit_register_callback($res, $id, $function); dpaymentssdk_ptechcanadiandebit_get_last_error($res); dpaymentssdk_ptechcanadiandebit_get_last_error_code($res); dpaymentssdk_ptechcanadiandebit_set($res, $id, $index, $value); dpaymentssdk_ptechcanadiandebit_get($res, $id, $index); dpaymentssdk_ptechcanadiandebit_do_authorize($res); dpaymentssdk_ptechcanadiandebit_do_config($res, $configurationstring); dpaymentssdk_ptechcanadiandebit_do_getrequestdatatomac($res); dpaymentssdk_ptechcanadiandebit_do_getresponsedatatomac($res); dpaymentssdk_ptechcanadiandebit_do_interrupt($res); dpaymentssdk_ptechcanadiandebit_do_macreversal($res); dpaymentssdk_ptechcanadiandebit_do_requestcurrentkeys($res); dpaymentssdk_ptechcanadiandebit_do_reset($res); dpaymentssdk_ptechcanadiandebit_do_reversaladvice($res, $originaltransactiontype, $reasoncode);
Remarks
Canadian debit card processing on the Paymentech system is fundamentally different than authorizing US Debit cards. The US protocol requires an encrypted PIN block and Key Sequence Number (KSN), retrieved from a PIN Pad utilizing the DUKPT (DES/3DES) encryption protocols. However, Interac (Canadian) Debit uses Master/Session key authentication to retrieve an encrypted key from a PIN Pad. This is a much more complex procedure, and requires the use of a Chase Paymentech certified PIN pad (we recommend the Ingenico i3070).
A unique key per device for both the PIN key and the MAC key is required. All PIN pads must have a unique key injected at the time of deployment. In order for Chase Paymentech to identify the Master Key being used by the device, the PIN pad serial number (PinPadSerialNumber) is required to be sent with every transaction.
Before you can send any debit card transactions, you must first load the PIN Pad with a current session key. This is retrieved from Paymentech via the RequestCurrentKeys method. Two keys will be returned in the response: ResponsePINKey (also known as TPK) and ResponseMACKey (also known as TAK). Both keys must be loaded into the PIN pad device. The PIN key is used by the PIN pad to encrypt the customer's PIN, and the MAC key is used to generate hash values used in requests and responses. These keys are updated after every transaction, and the PIN pad must be updated with the current keys each time a response is received.
Each transaction you send (excluding RequestCurrentKeys and MACReversals) requires an accompanying MACValue. This value is a hash of the contents of GetRequestDataToMAC, and is hashed by the PIN Pad device using the ResponseMACKey returned in response to the last transaction.
In each response there is also a ResponseMACValue. You must use the PIN Pad to calculate the hash of the value returned by GetResponseDataToMAC for each response, and make sure that calculated value matches the ResponseMACValue. If they do not match, you cannot accept the transaction, and you must send an MACReversal transaction (tor MACReversals you may send the MACValue used in the original request, or omit it entirely - do not calculate a new one).
The following code illustrates the steps necessary to initialize the PIN Pad and begin sending transactions:
First, set up the class with your merchant information.
' Set up the class
class.MerchantNumber = "yourMerchantNumber"
class.TerminalNumber = "100"
class.ClientNumber = "0002"
class.UserId = "yourUserId"
class.Password = "yourPassword"
Then, retrieve the current PIN and MAC encryption keys with the RequestCurrentKeys method, as shown below.
(The following code will also update the EncryptedKeyIndex).
class.SequenceNumber = 1
class.PinPadSerialNumber = "FFFFFFFFFFFFFFFF" ' retrieved from your PIN Pad
class.RequestCurrentKeys()
After receiving a valid response to RequestCurrentKeys, it is essential that you update the PIN pad
with the ResponsePINKey and ResponseMACKey. The ResponsePINKey is used by the PIN pad to
encrypt the customer's pin, and the ResponseMACKey is used by the PIN pad's MAC function. Now we
are able to send an actual customer sale transaction. First, set up the transaction details:
class.SequenceNumber = 2
class.InteracTransactionType = ittSale ' Set this before calling GetRequestDataToMAC method
class.TransactionAmount = "1.00"
Now, have the customer swipe his card, and pass the TransactionAmount, CardNumber, and
GetRequestDataToMAC to the PIN pad in a PURCHASE transaction. After the customer enters his PIN, use
the response from the PIN pad to fill the following properties:
class.CardTrack2Data = "9999999800002773=05121015432112345678" ' retrieved from your card reader
class.AccountType = acctChecking ' retrieved from your PIN pad
class.EncryptedPIN = "FFFFFFFFFFFFFFFF" ' retrieved from your PIN pad
class.MACValue = "FFFFFFFF" ' retrieved from your PIN pad
Once all the above properties are set, you can call the Authorize method to send the transaction to
Paymentech for authorization.
class.Authorize()
If the transaction was successful, the ResponseCode property will contain "A" (for Approval).
Before processing the response, you must first analyze the response with the PIN pad to verify that the
ResponseMACValue is correct, load the newly returned keys, and print the transaction's success or
failure on the PIN pad device for the customer to read. To do this, you send the
ResponsePINKey, ResponseMACKey, and GetResponseDataToMAC to the PIN pad in a "Response Analysis" transaction.
The PIN Pad response will indicate if the MAC value matches and the keys were successfully loaded.
If the MAC validated correctly, you're done with this transaction. However, if it did not validate, then you must send a MACReversal to abort the transaction, and then re-send it. If you are unable to verify the contents of the ResponseMACValue after another transaction attempt, refresh your keys via the RequestCurrentKeys method and try again. You must call RequestCurrentKeys any time the PIN pad loses sync with the Paymentech server, or whenever the ResponseForceKeyRequest property is true (or when initializing the PIN pad for the first time).
The status of any of the above transactions will be stored in the ResponseCode property, with human-readable text appearing in ResponseText. Like the PTechCharge class, there are several other Response fields which will contain data that should be logged. However, there are a few new properties specific to the PTechCanadianDebit class that must be printed on each customer's receipt. These include ResponseRetrievalNumber, ResponseTime, and ResponseTrace.
Debit card transactions are instant funds transfers. There is no block placed on the debit card, funds are immediately removed and sent to the merchant. Therefore, only the Host Capture settlement mode is supported. At the end of the day you should release the current batch using the PTechHostSettle class (the batch may contain other authorizations that were made using different classs from this product. See the documentation for the other classs you are using for more information).
Note: All PIN pads must be certified with Chase Paymentech and Interac prior to being used or deployed. All injection services must be approved and certified by Chase Paymentech.
Property List
The following is the full list of the properties of the class with short descriptions. Click on the links for further details.
AccountType | Account type selected by the cardholder. |
CardNumber | The credit card number parsed from the CardTrack2Data . |
CardTrack2Data | The Track2 portion of the debit card's magnetic stripe. |
ClientNumber | Merchant configuration property, assigned by Paymentech. |
DebitCashBack | Optional cash back amount for debit transactions. |
DebitSurcharge | Extra amount the merchant charges the customer for using a debit card. |
EncryptedKeyIndex | Specifies the current keys that are in use in the PIN pad and by Paymentech. |
EncryptedPIN | Customer's PIN, encrypted by a PIN pad under the current PINKey . |
InteracTransactionType | Indicates the type of transaction to authorize. |
LastRetrievalNumber | The last RetrievalNumber received from the host. Used for Void transactions. |
MACValue | Hash of transaction data used to verify message was not tampered with. |
MerchantNumber | A unique number used to identify the merchant, assigned by Paymentech. |
Password | Password for authentication with the NetConnect Server . |
PinPadSerialNumber | The serial number retrieved from the PIN pad. |
ProxyAuthScheme | This property is used to tell the class which type of authorization to perform when connecting to the proxy. |
ProxyAutoDetect | This property tells the class whether or not to automatically detect and use proxy system settings, if available. |
ProxyPassword | This property contains a password if authentication is to be used for the proxy. |
ProxyPort | This property contains the Transmission Control Protocol (TCP) port for the proxy Server (default 80). |
ProxyServer | If a proxy Server is given, then the HTTP request is sent to the proxy instead of the server otherwise specified. |
ProxySSL | This property determines when to use a Secure Sockets Layer (SSL) for the connection to the proxy. |
ProxyUser | This property contains a username if authentication is to be used for the proxy. |
ResponseApprovalCode | Contains an authorization code when a transaction has been approved, or an error code. |
ResponseAuthSource | Indicates the source of the authorization code stored in ApprovalCode . |
ResponseBatchNumber | Current open batch number This property is returned after sending a BatchInquiry or BatchRelease transaction with the PTECHHOSTSETTLE class, or after a SendSettlement sent using the PTECHMANUALSETTLE class. |
ResponseCode | Indicates the status of the authorization request. |
ResponseForceKeyRequest | Indicates the host requires the class to re-synchronize keys. |
ResponseMACKey | MAC Encryption key to be loaded into the PIN pad device. |
ResponseMACValue | Hash value that must be validated by the PIN pad after each response. |
ResponsePINKey | PIN Encryption key to be loaded into the PIN pad device. |
ResponseRetrievalNumber | Reference number returned from the Paymentech host. |
ResponseSequenceNumber | SequenceNumber echoed from the authorization. |
ResponseText | Approval/Decline/Error text message information This property contains a response or display text message, and is used by the terminal to display the authorization result. |
ResponseTime | The server-normalized Date and Time of the transaction. |
ResponseTrace | Trace number returned for Canadian Interac Debit transactions. |
RetrievalNumberToVoid | Indicates the transaction to void. |
SequenceNumber | Sequence number of the transaction. |
Server | The URL for the PaymenTech NetConnect server. |
SSLAcceptServerCertEncoded | This is the certificate (PEM/Base64 encoded). |
SSLCertEncoded | This is the certificate (PEM/Base64 encoded). |
SSLCertStore | This is the name of the certificate store for the client certificate. |
SSLCertStorePassword | If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store. |
SSLCertStoreType | This is the type of certificate store for this certificate. |
SSLCertSubject | This is the subject of the certificate used for client authentication. |
SSLProvider | This specifies the SSL/TLS implementation to use. |
SSLServerCertEncoded | This is the certificate (PEM/Base64 encoded). |
TerminalNumber | Terminal number assigned by Paymentech. |
Timeout | A timeout for the class. |
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 class with short descriptions. Click on the links for further details.
Authorize | Authorizes a Canadian debit card transaction. |
Config | Sets or retrieves a configuration setting. |
GetRequestDataToMAC | Returns a string of data for the PIN pad to hash with the MAC algorithm. |
GetResponseDataToMAC | Returns a string containing data to validate against the MACValue using a PIN pad device. |
Interrupt | Interrupt the current method. |
MACReversal | Reverses a transaction when MAC validation fails. |
RequestCurrentKeys | Used to retrieve the current encryption keys from Paymentech. |
Reset | Clears all properties to their default values. |
ReversalAdvice | Used if no response is received from the Server to void the authorization. |
Event List
The following is the full list of the events fired by the class 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 | Fired when secure connection progress messages are available. |
Config Settings
The following is a list of config settings for the class with short descriptions. Click on the links for further details.
CustomerDefinedData | Additional transaction identification data. |
EMVData | The EMV data returned from a Pin Pad after reading an EMV card. |
EMVEntryDataSource | The EMV Data Entry Source (DES). |
ResponseEMVCardAuthCode | The ChaseNet and Visa card authentication results code. |
ResponseEMVData | The response EMV data. |
ResponseEMVDownloadIndicator | Whether EMV parameters should be updated. |
ResponsePOSRetrievalNumber | POS Retrieval Number sent in the request, echoed back in the response. |
SettlementMode | Indicates whether the class uses Paymentech's Host Capture or Terminal Capture system. |
SystemInformation | System Information field for Batch Inquiry and Release transactions. |
AcceptEncoding | Used to tell the server which types of content encodings the client supports. |
AllowHTTPCompression | This property enables HTTP compression for receiving data. |
AllowHTTPFallback | Whether HTTP/2 connections are permitted to fallback to HTTP/1.1. |
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. |
ChunkSize | Specifies the chunk size in bytes when using chunked encoding. |
CompressHTTPRequest | Set to true to compress the body of a PUT or POST request. |
EncodeURL | If set to True the URL will be encoded by the class. |
FollowRedirects | Determines what happens when the server issues a redirect. |
GetOn302Redirect | If set to True the class will perform a GET on the new location. |
HTTP2HeadersWithoutIndexing | HTTP2 headers that should not update the dynamic header table with incremental indexing. |
HTTPVersion | The version of HTTP used by the class. |
IfModifiedSince | A date determining the maximum age of the desired document. |
KeepAlive | Determines whether the HTTP connection is closed after completion of the request. |
KerberosSPN | The Service Principal Name for the Kerberos Domain Controller. |
LogLevel | The level of detail that is logged. |
MaxRedirectAttempts | Limits the number of redirects that are followed in a request. |
NegotiatedHTTPVersion | The negotiated HTTP version. |
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. |
SentHeaders | The full set of headers as sent by the client. |
StatusCode | The status code of the last response from the server. |
StatusLine | The first line of the last response from the server. |
TransferredData | The contents of the last response from the server. |
TransferredDataLimit | The maximum number of incoming bytes to be stored by the class. |
TransferredHeaders | The full set of headers as received from the server. |
TransferredRequest | The full request as sent by the client. |
UseChunkedEncoding | Enables or Disables HTTP chunked encoding for transfers. |
UseIDNs | Whether to encode hostnames to internationalized domain names. |
UsePlatformHTTPClient | Whether or not to use the platform HTTP client. |
UseProxyAutoConfigURL | Whether to use a Proxy auto-config file when attempting a connection. |
UserAgent | Information about the user agent (browser). |
ConnectionTimeout | Sets a separate timeout value for establishing a connection. |
FirewallAutoDetect | Tells the class 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. |
KeepAliveInterval | The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received. |
KeepAliveTime | The inactivity time in milliseconds before a TCP keep-alive packet is sent. |
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 port in the local host where the class binds. |
MaxLineLength | The maximum amount of data to accumulate when no EOL is found. |
MaxTransferRate | The transfer rate limit in bytes per second. |
ProxyExceptionsList | A semicolon separated list of hosts and IPs to bypass when using a proxy. |
TCPKeepAlive | Determines whether or not the keep alive socket option is enabled. |
TcpNoDelay | Whether or not to delay when sending packets. |
UseIPv6 | Whether to use IPv6. |
LogSSLPackets | Controls whether SSL packets are logged when using the internal security API. |
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). |
ReuseSSLSession | Determines if the SSL session is reused. |
SSLCACertFilePaths | The paths to CA certificate files on Unix/Linux. |
SSLCACerts | A newline separated list of CA certificate to use during SSL client authentication. |
SSLCheckCRL | Whether to check the Certificate Revocation List for the server certificate. |
SSLCheckOCSP | Whether to use OCSP to check the status of the server certificate. |
SSLCipherStrength | The minimum cipher strength used for bulk encryption. |
SSLEnabledCipherSuites | The cipher suite to be used in an SSL negotiation. |
SSLEnabledProtocols | Used to enable/disable the supported security protocols. |
SSLEnableRenegotiation | Whether the renegotiation_info SSL extension is supported. |
SSLIncludeCertChain | Whether the entire certificate chain is included in the SSLServerAuthentication event. |
SSLKeyLogFile | The location of a file where per-session secrets are written for debugging purposes. |
SSLNegotiatedCipher | Returns the negotiated cipher suite. |
SSLNegotiatedCipherStrength | Returns the negotiated cipher suite strength. |
SSLNegotiatedCipherSuite | Returns the negotiated cipher suite. |
SSLNegotiatedKeyExchange | Returns the negotiated key exchange algorithm. |
SSLNegotiatedKeyExchangeStrength | Returns the negotiated key exchange algorithm strength. |
SSLNegotiatedVersion | Returns the negotiated protocol version. |
SSLSecurityFlags | Flags that control certificate verification. |
SSLServerCACerts | A newline separated list of CA certificate to use during SSL server certificate validation. |
TLS12SignatureAlgorithms | Defines the allowed TLS 1.2 signature algorithms when SSLProvider is set to Internal. |
TLS12SupportedGroups | The supported groups for ECC. |
TLS13KeyShareGroups | The groups for which to pregenerate key shares. |
TLS13SignatureAlgorithms | The allowed certificate signature algorithms. |
TLS13SupportedGroups | The supported groups for (EC)DHE key exchange. |
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. |
BuildInfo | Information about the product's build. |
CodePage | The system code page used for Unicode to Multibyte translations. |
LicenseInfo | Information about the current license. |
MaskSensitive | Whether sensitive data is masked in log messages. |
ProcessIdleEvents | Whether the class uses its internal event loop to process events when the main thread is idle. |
SelectWaitMillis | The length of time in milliseconds the class will wait when DoEvents is called if there are no events to process. |
UseInternalSecurityAPI | Whether or not to use the system security libraries or an internal implementation. |
AccountType Property (DPaymentsSDK_PTechCanadianDebit Class)
Account type selected by the cardholder.
Object Oriented Interface
public function getAccountType(); public function setAccountType($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 1 ); dpaymentssdk_ptechcanadiandebit_set($res, 1, $value );
Default Value
0
Remarks
Canadian debit cards allow the customer to choose the account he or she wishes to pay with. Allowable account types are listed below:
acctNotSet (0) | Account Type is not set |
acctChecking (1) | This transaction is paid for with funds from the customer's Checking account. |
acctSavings (2) | This transaction is paid for with funds from the customer's Savings account. |
Note that sending an Authorize transaction with AccountType set to acctNotSet will result in an error.
Data Type
Integer
CardNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
The credit card number parsed from the CardTrack2Data .
Object Oriented Interface
public function getCardNumber();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 2 );
Default Value
''
Remarks
This read-only property will be computed by the class after the CardTrack2Data property is set.
This property is read-only.
Data Type
String
CardTrack2Data Property (DPaymentsSDK_PTechCanadianDebit Class)
The Track2 portion of the debit card's magnetic stripe.
Object Oriented Interface
public function getCardTrack2Data(); public function setCardTrack2Data($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 3 ); dpaymentssdk_ptechcanadiandebit_set($res, 3, $value );
Default Value
''
Remarks
This property should contain the track 2 data read from the debit card's magnetic stripe. This includes everything after but not including the start sentinel (;) and up to but not including the end sentinel (?) and LRC check character. You may only set this property with track 2 data, track 1 data will cause an error.
So if the full magnetic stripe read from the card is "%B4788250000028291^PAYMENTECH^05121015432112345678?;4788250000028291=05121015432112345678?", then this property should be set as follows:
class.CardTrack2Data = "4788250000028291=05121015432112345678"
Industry regulations do not allow merchants or processors to store track data in any form of persistent storage. Failure to abide by this regulation can result in significant fines and other penalties.
Data Type
String
ClientNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
Merchant configuration property, assigned by Paymentech.
Object Oriented Interface
public function getClientNumber(); public function setClientNumber($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 4 ); dpaymentssdk_ptechcanadiandebit_set($res, 4, $value );
Default Value
''
Remarks
The ClientNumber will be supplied to you by Paymentech.
Data Type
String
DebitCashBack Property (DPaymentsSDK_PTechCanadianDebit Class)
Optional cash back amount for debit transactions.
Object Oriented Interface
public function getDebitCashBack(); public function setDebitCashBack($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 5 ); dpaymentssdk_ptechcanadiandebit_set($res, 5, $value );
Default Value
''
Remarks
This property may contain an optional cash back amount when authorizing a debit card transaction. The value of the TransactionAmount must reflect the cost of the goods or service purchased plus this DebitCashBack amount. This property is presented in CA Dollars with a decimal point in the proper position. The maximum value for this property is "999999.99". To send a transaction without cashback, set DebitCashBack to "".
This must be formatted as a dollar amount with a real decimal point, excluding the dollar sign. For instance "12.00"
Data Type
String
DebitSurcharge Property (DPaymentsSDK_PTechCanadianDebit Class)
Extra amount the merchant charges the customer for using a debit card.
Object Oriented Interface
public function getDebitSurcharge(); public function setDebitSurcharge($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 6 ); dpaymentssdk_ptechcanadiandebit_set($res, 6, $value );
Default Value
''
Remarks
Surcharging in Canada is optional at the point of sale terminal device. The amount of the surcharge is defined at the Point of Sale (POS) and must be accepted by the cardholder prior to the transaction being processed. If the DebitSurcharge property contains a value, the surcharge amount will be logged to the transaction record on the Host. The Surcharge Amount must be included as part of the transaction amount. Regulations require that this fee amount print on the receipt and be clearly labeled as "TERMINAL FEE" or "FRAIS D'OPER." For example:
Amount of sale | $10.00 |
Cardholder desired DebitCashBack | $ 5.00 |
A DebitSurcharge was applied of | $ .50 |
Total TransactionAmount sent to Host | $15.50 |
In this case, the receipt would read:
SALE $10.00
CASH BACK $ 5.00
TERMINAL FEE $ .50
TOTAL CHARGED $15.50
Data Type
String
EncryptedKeyIndex Property (DPaymentsSDK_PTechCanadianDebit Class)
Specifies the current keys that are in use in the PIN pad and by Paymentech.
Object Oriented Interface
public function getEncryptedKeyIndex(); public function setEncryptedKeyIndex($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 7 ); dpaymentssdk_ptechcanadiandebit_set($res, 7, $value );
Default Value
0
Remarks
The EncryptedKeyIndex specifies the current keys that are in use on the host (Paymentech) and in the PIN pad. This EncryptedKeyIndex is updated after every transaction, and is required to be sent in all transactions except a RequestCurrentKeys transaction. The normal range is from 1 through 9. The default is zero (0), and indicates that no encryption keys have been established. Transaction requests should never be sent with a value of zero (0). Note that MACReversals must be sent with the EncryptedKeyIndex from the original transaction to insure that the EncryptedPIN can be properly translated by the host.
Keys are required to be renewed every:
- 200 Transactions
- 24 Hours
- Each time a Batch is released for settlement
- Whenever the PIN pad loses sync with the server
If the ResponseForceKeyRequest property is True after any transaction, you must immediately perform a RequestCurrentKeys transaction before sending any more authorizations.
Data Type
Integer
EncryptedPIN Property (DPaymentsSDK_PTechCanadianDebit Class)
Customer's PIN, encrypted by a PIN pad under the current PINKey .
Object Oriented Interface
public function getEncryptedPIN(); public function setEncryptedPIN($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 8 ); dpaymentssdk_ptechcanadiandebit_set($res, 8, $value );
Default Value
''
Remarks
The EncryptedPIN block is required by all InteracTransactionTypes, as well as the MACReversal and ReversalAdvice methods. Only the RequestCurrentKeys method does not require this property. The maximum length for this property is 16 characters.
Data Type
String
InteracTransactionType Property (DPaymentsSDK_PTechCanadianDebit Class)
Indicates the type of transaction to authorize.
Object Oriented Interface
public function getInteracTransactionType(); public function setInteracTransactionType($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 9 ); dpaymentssdk_ptechcanadiandebit_set($res, 9, $value );
Default Value
27
Remarks
This property indicates the type of transaction that is to be sent in an Authorize request. The GetRequestDataToMAC method also uses this property when generating the data which must be MAC'ed by the PIN pad device. In addition to the transaction types listed below, this class also allows you to send MAC Reversals, Current Key Requests, and Reversal Advice transactions using the MACReversal, RequestCurrentKeys, and ReversalAdvice methods, respectively. Allowable transactions types include:
ittSale (27) | A regular sale transaction. |
ittSaleWithCashBack (28) | A sale transaction with DebitCashBack returned to the customer. |
ittReturn (29) | Interac only allows returns to offset a purchase; returns by themselves are not allowed. |
ittVoidSale (44) | Voids a previous ittSale transaction. |
ittVoidReturn (45) | Voids a previous ittReturn transaction. |
ittReversalAdvice (47) | This is only used for generating GetRequestDataToMAC. Calling Authorize with this InteracTransactionType will result in an error. Please see ReversalAdvice for more information. |
Data Type
Integer
LastRetrievalNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
The last RetrievalNumber received from the host. Used for Void transactions.
Object Oriented Interface
public function getLastRetrievalNumber(); public function setLastRetrievalNumber($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 10 ); dpaymentssdk_ptechcanadiandebit_set($res, 10, $value );
Default Value
''
Remarks
When sending a transaction with the InteracTransactionType set to ittVoidSale or ittVoidReturn, this property must contain the ResponseRetrievalNumber from the very last transaction that you sent to the Paymentech Server. RetrievalNumberToVoid should be set with the ResponseRetrievalNumber of the transaction you wish to void.
Data Type
String
MACValue Property (DPaymentsSDK_PTechCanadianDebit Class)
Hash of transaction data used to verify message was not tampered with.
Object Oriented Interface
public function getMACValue(); public function setMACValue($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 11 ); dpaymentssdk_ptechcanadiandebit_set($res, 11, $value );
Default Value
''
Remarks
Each transaction you send (excluding RequestCurrentKeys and MACReversals) requires an accompanying MACValue. This value is a hash of the contents of GetRequestDataToMAC, and is hashed by the PIN Pad device using the ResponseMACKey returned in response to the last transaction.
The GetRequestDataToMAC method returns a string containing the values of several transaction properties. This string must be MAC'ed by the PIN pad, so it is essential that the following properties be set before calling GetRequestDataToMAC:
- MerchantNumber
- TerminalNumber
- InteracTransactionType
- CardTrack2Data
- TransactionAmount
- SequenceNumber
- and optionally AccountType
Note that VeriFone pinpads support a PURCHASE transaction where the CardTrack2Data, EncryptedPIN, AccountType, and MACValue are returned in a single step. When using a VeriFone pad make sure AccountType is set to acctNotSet, otherwise the MACValue will not be calculated correctly. (AccountType must be set before calling GetRequestDataToMAC for Ingenico pads)
class.MerchantNumber = "yourMerchantNumber"
class.TerminalNumber = "100"
class.ClientNumber = "0002"
class.UserId = "yourUserId"
class.Password = "yourPassword"
class.SequenceNumber = 2
class.TransactionAmount = "1.00"
class.PinPadSerialNumber = "30700015P3600000" ' from label on back of PIN pad
class.InteracTransactionType = ittSale
class.AccountType = acctChecking
class.CardTrack2Data = "9999999800002773=05121015432112345678" ' from card reader
class.EncryptedPIN = "FFFFFFFFFFFFFFFF" ' from the PIN pad
' Now use the PIN pad to MAC the value returned from GetRequestDataToMAC
' and then set MACValue with the results
class.MACValue = "FFFFFFFF"
class.Authorize()
Data Type
String
MerchantNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
A unique number used to identify the merchant, assigned by Paymentech.
Object Oriented Interface
public function getMerchantNumber(); public function setMerchantNumber($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 12 ); dpaymentssdk_ptechcanadiandebit_set($res, 12, $value );
Default Value
''
Remarks
This 12 digit field contains a unique number to identify the merchant to the host.
Data Type
String
Password Property (DPaymentsSDK_PTechCanadianDebit Class)
Password for authentication with the NetConnect Server .
Object Oriented Interface
public function getPassword(); public function setPassword($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 13 ); dpaymentssdk_ptechcanadiandebit_set($res, 13, $value );
Default Value
''
Remarks
The Password will be supplied to you by Paymentech.
Data Type
String
PinPadSerialNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
The serial number retrieved from the PIN pad.
Object Oriented Interface
public function getPinPadSerialNumber(); public function setPinPadSerialNumber($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 14 ); dpaymentssdk_ptechcanadiandebit_set($res, 14, $value );
Default Value
''
Remarks
Your PIN pad will have a function that will return the PIN pad serial number. This number is used to identify the key being used by the PIN pad device to the Paymentech transaction sever, and is required to be sent in every transaction.
All PIN pad serial numbers MUST be unique. You must update the PinPadSerialNumbers property with a new value retrieved from the PIN pad device before each transaction.
All PIN Pad Serial Numbers can be variable in length, but must be a minimum of 9-bytes long, and a maximum of 16-bytes long.
The serial number of a PIN pad is usually printed on the label on the bottom of the unit. The PIN pad may also include the option of displaying the serial number on the screen or returning it through a COM interface. Please see the developer documentation for your specific PIN pad for more information.
Data Type
String
ProxyAuthScheme Property (DPaymentsSDK_PTechCanadianDebit Class)
This property is used to tell the class which type of authorization to perform when connecting to the proxy.
Object Oriented Interface
public function getProxyAuthScheme(); public function setProxyAuthScheme($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 15 ); dpaymentssdk_ptechcanadiandebit_set($res, 15, $value );
Default Value
0
Remarks
This property is used to tell the class which type of authorization to perform when connecting to the proxy. This is used only when the ProxyUser and ProxyPassword properties are set.
ProxyAuthScheme should be set to authNone (3) when no authentication is expected.
By default, ProxyAuthScheme is authBasic (0), and if the ProxyUser and ProxyPassword properties are set, the component will attempt basic authentication.
If ProxyAuthScheme is set to authDigest (1), digest authentication will be attempted instead.
If ProxyAuthScheme is set to authProprietary (2), then the authorization token will not be generated by the class. Look at the configuration file for the class being used to find more information about manually setting this token.
If ProxyAuthScheme is set to authNtlm (4), NTLM authentication will be used.
For security reasons, setting this property will clear the values of ProxyUser and ProxyPassword.
Data Type
Integer
ProxyAutoDetect Property (DPaymentsSDK_PTechCanadianDebit Class)
This property tells the class whether or not to automatically detect and use proxy system settings, if available.
Object Oriented Interface
public function getProxyAutoDetect(); public function setProxyAutoDetect($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 16 ); dpaymentssdk_ptechcanadiandebit_set($res, 16, $value );
Default Value
false
Remarks
This property tells the class whether or not to automatically detect and use proxy system settings, if available. The default value is false.
Data Type
Boolean
ProxyPassword Property (DPaymentsSDK_PTechCanadianDebit Class)
This property contains a password if authentication is to be used for the proxy.
Object Oriented Interface
public function getProxyPassword(); public function setProxyPassword($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 17 ); dpaymentssdk_ptechcanadiandebit_set($res, 17, $value );
Default Value
''
Remarks
This property contains a password if authentication is to be used for the proxy.
If ProxyAuthScheme is set to Basic Authentication, the ProxyUser and ProxyPassword are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].
If ProxyAuthScheme is set to Digest Authentication, the ProxyUser and ProxyPassword properties are used to respond to the Digest Authentication challenge from the server.
If ProxyAuthScheme is set to NTLM Authentication, the ProxyUser and ProxyPassword properties are used to authenticate through NTLM negotiation.
Data Type
String
ProxyPort Property (DPaymentsSDK_PTechCanadianDebit Class)
This property contains the Transmission Control Protocol (TCP) port for the proxy Server (default 80).
Object Oriented Interface
public function getProxyPort(); public function setProxyPort($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 18 ); dpaymentssdk_ptechcanadiandebit_set($res, 18, $value );
Default Value
80
Remarks
This property contains the Transmission Control Protocol (TCP) port for the proxy ProxyServer (default 80). See the description of the ProxyServer property for details.
Data Type
Integer
ProxyServer Property (DPaymentsSDK_PTechCanadianDebit Class)
If a proxy Server is given, then the HTTP request is sent to the proxy instead of the server otherwise specified.
Object Oriented Interface
public function getProxyServer(); public function setProxyServer($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 19 ); dpaymentssdk_ptechcanadiandebit_set($res, 19, $value );
Default Value
''
Remarks
If a proxy ProxyServer is given, then the HTTP request is sent to the proxy instead of the server otherwise specified.
If the ProxyServer property is set to a domain name, a DNS request is initiated. Upon successful termination of the request, the ProxyServer property is set to the corresponding address. If the search is not successful, an error is returned.
Data Type
String
ProxySSL Property (DPaymentsSDK_PTechCanadianDebit Class)
This property determines when to use a Secure Sockets Layer (SSL) for the connection to the proxy.
Object Oriented Interface
public function getProxySSL(); public function setProxySSL($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 20 ); dpaymentssdk_ptechcanadiandebit_set($res, 20, $value );
Default Value
0
Remarks
This property determines when to use a Secure Sockets Layer (SSL) for the connection to the proxy. The applicable values are as follows:
psAutomatic (0) | Default setting. If the URL is an https URL, the class will use the psTunnel option. If the URL is an http URL, the class will use the psNever option. |
psAlways (1) | The connection is always SSL enabled. |
psNever (2) | The connection is not SSL enabled. |
psTunnel (3) | The connection is made through a tunneling (HTTP) proxy. |
Data Type
Integer
ProxyUser Property (DPaymentsSDK_PTechCanadianDebit Class)
This property contains a username if authentication is to be used for the proxy.
Object Oriented Interface
public function getProxyUser(); public function setProxyUser($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 21 ); dpaymentssdk_ptechcanadiandebit_set($res, 21, $value );
Default Value
''
Remarks
This property contains a username if authentication is to be used for the proxy.
If ProxyAuthScheme is set to Basic Authentication, the ProxyUser and ProxyPassword properties are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].
If ProxyAuthScheme is set to Digest Authentication, the ProxyUser and ProxyPassword properties are used to respond to the Digest Authentication challenge from the server.
If ProxyAuthScheme is set to NTLM Authentication, the ProxyUser and ProxyPassword properties are used to authenticate through NTLM negotiation.
Data Type
String
ResponseApprovalCode Property (DPaymentsSDK_PTechCanadianDebit Class)
Contains an authorization code when a transaction has been approved, or an error code.
Object Oriented Interface
public function getResponseApprovalCode();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 22 );
Default Value
''
Remarks
Contains an authorization code when a transaction has been approved, or an error code. This six character field contains an authorization code when a transaction has been approved. If the ResponseCode returned indicates that the transaction has not been approved, then this field will contain an error code, and the ResponseText property will contain the description. Note that the host does not send back an actual authorization code for Credit Returns. Instead, the host sends back six blank spaces in the authorization code field. Credit VOIDS return the original authorization number.
See the list of errors for this class for more information.
This property is read-only.
Data Type
String
ResponseAuthSource Property (DPaymentsSDK_PTechCanadianDebit Class)
Indicates the source of the authorization code stored in ApprovalCode .
Object Oriented Interface
public function getResponseAuthSource();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 23 );
Default Value
''
Remarks
Indicates the source of the authorization code stored in ResponseApprovalCode. This field contains a one character code indicating the source of the ResponseApprovalCode. The received code must be stored and submitted in the batch settlement. Valid source codes:
Code | Description |
1 | STIP (Stand-In Processing): time-out response. |
2 | STIP: amount below issuer limit. |
3 | STIP: issuer in Suppress Inquiry mode. |
4 | STIP: issuer unavailable. |
5 | Issuer generated response. |
6 | Off-line approval: POS device generated. |
7 | Acquirer approval: Base I unavailable. |
8 | Acquirer approval of a referral. |
9 | Use for non-authorized transactions; such as credit card credits. |
D | Referral: authorization code manually keyed. |
E | Off-line approval: authorization code manually keyed. |
F | CAFIS Interface Off-Line Post-Auth.* |
G | Issuer Approval: Post-Auth.* |
T | Advice of a Telcode File change initiated by the VisaPhone Issuer Direct Service. |
This property is read-only and not available at design time.
Data Type
String
ResponseBatchNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
Current open batch number This property is returned after sending a BatchInquiry or BatchRelease transaction with the PTECHHOSTSETTLE class, or after a SendSettlement sent using the PTECHMANUALSETTLE class.
Object Oriented Interface
public function getResponseBatchNumber();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 24 );
Default Value
''
Remarks
Current open batch number This property is returned after sending a BatchInquiry or BatchRelease transaction with the PTechHostSettle class, or after a SendSettlement sent using the PTechManualSettle class.
This property is read-only.
Data Type
String
ResponseCode Property (DPaymentsSDK_PTechCanadianDebit Class)
Indicates the status of the authorization request.
Object Oriented Interface
public function getResponseCode();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 25 );
Default Value
''
Remarks
Indicates the status of the authorization request. This is the property used to determine whether a transaction has been approved or not. Valid values for this property are:
A | Transaction is Approved. |
E | Error condition or card declined (see the Error section of the help file for more information). |
See the list of errors for this class for more information.
This property is read-only.
Data Type
String
ResponseForceKeyRequest Property (DPaymentsSDK_PTechCanadianDebit Class)
Indicates the host requires the class to re-synchronize keys.
Object Oriented Interface
public function getResponseForceKeyRequest();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 26 );
Default Value
false
Remarks
Indicates the host requires the class to re-synchronize keys. If after any transaction the ForceKeyRequest is True, you must immediately perform a RequestCurrentKeys transaction to refresh the PIN and MAC keys on the PIN pad. If you do not call RequestCurrentKeys your PIN pad will be out of sync with Paymentech and further transactions may fail.
This property is read-only.
Data Type
Boolean
ResponseMACKey Property (DPaymentsSDK_PTechCanadianDebit Class)
MAC Encryption key to be loaded into the PIN pad device.
Object Oriented Interface
public function getResponseMACKey();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 27 );
Default Value
''
Remarks
MAC Encryption key to be loaded into the PIN pad device. MAC encryption key encrypted under the PIN pad master key. This key changes as required by Interac regulations, and should be loaded into the PIN pad device upon receipt. The developer should validate the MACValue returned in the host response using this key. Future transactions must contain a MACValue that was computed by the PIN pad using this key.
Keys are required to be renewed every:
- 200 Transactions
- 24 Hours
- Each time a Batch is released for settlement
- Whenever the PIN pad loses sync with the server
If the ResponseForceKeyRequest property is True after any transaction, you must immediately perform a RequestCurrentKeys transaction before sending any more authorizations.
This property is read-only.
Data Type
String
ResponseMACValue Property (DPaymentsSDK_PTechCanadianDebit Class)
Hash value that must be validated by the PIN pad after each response.
Object Oriented Interface
public function getResponseMACValue();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 28 );
Default Value
''
Remarks
Hash value that must be validated by the PIN pad after each response. Each successful response to a transaction will include a ResponseMACKey and a ResponseMACValue. The ResponseMACKey (and ResponsePINKey) should be loaded into the PIN pad device upon receipt. The ResponseMACValue is a string encrypted by the Paymentech server using the ResponseMACKey, and is included in every successful response message. The original unencrypted data is returned by the GetResponseDataToMAC method. After loading the ResponseMACKey into the PIN pad device, send both ResponseMACValue and GetResponseDataToMAC to the PIN pad device for validation. If the PIN pad indicates the MAC matches, you're done, and you can continue processing transactions. However, if the PIN pad indicates the MAC did not match, you must immediately perform a MACReversal transaction, and consider the request as not approved.
A mismatched MAC value may mean that something was corrupted in data transmission, the response packet was tampered with, or that the keys loaded into your PIN pad device are not synchronized with Paymentech. Try synchronizing your keys with the RequestCurrentKeys method and then re-submitting the transaction.
This property is read-only.
Data Type
String
ResponsePINKey Property (DPaymentsSDK_PTechCanadianDebit Class)
PIN Encryption key to be loaded into the PIN pad device.
Object Oriented Interface
public function getResponsePINKey();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 29 );
Default Value
''
Remarks
PIN Encryption key to be loaded into the PIN pad device. PIN encryption key encrypted under the PIN pad master key. This key changes as required by Interac regulations, and should be loaded into the PIN pad device upon receipt. Future transactions must contain an encrypted PIN block (EncryptedPIN) that was computed by the PIN pad using this key.
Keys are required to be renewed every:
- 200 Transactions
- 24 Hours
- Each time a Batch is released for settlement
- Whenever the PIN pad loses sync with the server
If the ResponseForceKeyRequest property is True after any transaction, you must immediately perform a RequestCurrentKeys transaction before sending any more authorizations.
This property is read-only.
Data Type
String
ResponseRetrievalNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
Reference number returned from the Paymentech host.
Object Oriented Interface
public function getResponseRetrievalNumber();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 30 );
Default Value
''
Remarks
Reference number returned from the Paymentech host. This is the reference number of the transaction as assigned by the Paymentech host. This number must remain with the transaction for the duration of the transaction's life cycle. This information is sent as a parameter in the VoidTransaction method.
If the SettlementMode is set to manual this property will contain the POSRetrievalNumber submitted in the authorization. If no POSRetrievalNumber was sent, this property will contain all zeros, and you will not have a reference number for the transaction.
If the SettlementMode is set to host settle, this property will always contain the Paymentech-generated retrieval number returned by the transaction server, regardless of the value contained in the POSRetrievalNumber property.
In all cases, the ResponseRetrievalNumber will contain the number used to reference the transaction when issuing voids or reversals.
This property is read-only.
Data Type
String
ResponseSequenceNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
SequenceNumber echoed from the authorization.
Object Oriented Interface
public function getResponseSequenceNumber();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 31 );
Default Value
''
Remarks
SequenceNumber echoed from the authorization. After any transaction this property will contain the same value sent in the SequenceNumber property.
This property is read-only.
Data Type
String
ResponseText Property (DPaymentsSDK_PTechCanadianDebit Class)
Approval/Decline/Error text message information This property contains a response or display text message, and is used by the terminal to display the authorization result.
Object Oriented Interface
public function getResponseText();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 32 );
Default Value
''
Remarks
Approval/Decline/Error text message information This field contains a response or display text message, and is used by the terminal to display the authorization result. This property will contain human-readable text indicating whether the transaction was approved or declined, or will contain a description of the error. The actual error code will be returned in the ResponseApprovalCode property. The ResponseText property is for informational use only, and should not be used in determining whether a transaction has been approved or not. Instead, use the ResponseCode property to determine this.
See the list of errors for this class for more information.
This property is read-only.
Data Type
String
ResponseTime Property (DPaymentsSDK_PTechCanadianDebit Class)
The server-normalized Date and Time of the transaction.
Object Oriented Interface
public function getResponseTime();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 33 );
Default Value
''
Remarks
The server-normalized Date and Time of the transaction. After a transaction completes (successful or not) this property will contain the date and time of the transaction, returned by the server. The format is "MMddyyyyHHmmss". For example, "01192008171543" indicates the date "January 19th, 2008 5:15:43 pm".
If the host-adjusted date/time is different than what the Point Of Sale has currently, the Point of Sale date/time should be updated to match.
This property is read-only.
Data Type
String
ResponseTrace Property (DPaymentsSDK_PTechCanadianDebit Class)
Trace number returned for Canadian Interac Debit transactions.
Object Oriented Interface
public function getResponseTrace();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 34 );
Default Value
''
Remarks
Trace number returned for Canadian Interac Debit transactions. This field is returned in the response to an Interac debit card transaction. The returned value is used for transaction tracking purposes, and must be printed on the customer's receipt.
This property is read-only.
Data Type
String
RetrievalNumberToVoid Property (DPaymentsSDK_PTechCanadianDebit Class)
Indicates the transaction to void.
Object Oriented Interface
public function getRetrievalNumberToVoid(); public function setRetrievalNumberToVoid($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 35 ); dpaymentssdk_ptechcanadiandebit_set($res, 35, $value );
Default Value
''
Remarks
When sending a transaction with the InteracTransactionType set to ittVoidSale or ittVoidReturn, this property must contain the ResponseRetrievalNumber from the transaction you wish to void. The LastRetrievalNumber is also required for void transactions, and must be set with the LAST ResponseRetrievalNumber received from the Paymentech Server. If LastRetrievalNumber is left blank, the current contents of the ResponseRetrievalNumber property will be used instead.
Data Type
String
SequenceNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
Sequence number of the transaction.
Object Oriented Interface
public function getSequenceNumber(); public function setSequenceNumber($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 36 ); dpaymentssdk_ptechcanadiandebit_set($res, 36, $value );
Default Value
0
Remarks
This field is user definable and can be used at the users discretion. When submitting any type of transaction for approval, this sequence number may be any numeric value 0 to 2400. This is a purely optional field for the Host Capture SettlementMode, and you may choose to send a unique number or simply send every transaction with zeros. The host will echo the sequence number submitted from the authorization request back in the ResponseSequenceNumber property.
However, if you are processing with the Terminal Capture SettlementMode, SequenceNumber CANNOT remain zero, and must contain a number that is incremented for each transaction you authorized. When it reaches 2400, the SequenceNumber should then start over at 1 again.
Data Type
Integer
Server Property (DPaymentsSDK_PTechCanadianDebit Class)
The URL for the PaymenTech NetConnect server.
Object Oriented Interface
public function getServer(); public function setServer($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 37 ); dpaymentssdk_ptechcanadiandebit_set($res, 37, $value );
Default Value
'https://netconnect1.chasepaymentech.com/NetConnect/controller'
Remarks
This property contains the server to which all transactions are sent.
Data Type
String
SSLAcceptServerCertEncoded Property (DPaymentsSDK_PTechCanadianDebit Class)
This is the certificate (PEM/Base64 encoded).
Object Oriented Interface
public function getSSLAcceptServerCertEncoded(); public function setSSLAcceptServerCertEncoded($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 39 ); dpaymentssdk_ptechcanadiandebit_set($res, 39, $value );
Default Value
''
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLAcceptServerCertStore and SSLAcceptServerCertSubject properties also may be used to specify a certificate.
When SSLAcceptServerCertEncoded is set, a search is initiated in the current SSLAcceptServerCertStore for the private key of the certificate. If the key is found, SSLAcceptServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLAcceptServerCertSubject is set to an empty string.
This property is not available at design time.
Data Type
Binary String
SSLCertEncoded Property (DPaymentsSDK_PTechCanadianDebit Class)
This is the certificate (PEM/Base64 encoded).
Object Oriented Interface
public function getSSLCertEncoded(); public function setSSLCertEncoded($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 67 ); dpaymentssdk_ptechcanadiandebit_set($res, 67, $value );
Default Value
''
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLCertStore and SSLCertSubject properties also may be used to specify a certificate.
When SSLCertEncoded is set, a search is initiated in the current SSLCertStore for the private key of the certificate. If the key is found, SSLCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLCertSubject is set to an empty string.
This property is not available at design time.
Data Type
Binary String
SSLCertStore Property (DPaymentsSDK_PTechCanadianDebit Class)
This is the name of the certificate store for the client certificate.
Object Oriented Interface
public function getSSLCertStore(); public function setSSLCertStore($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 83 ); dpaymentssdk_ptechcanadiandebit_set($res, 83, $value );
Default Value
'MY'
Remarks
This is the name of the certificate store for the client certificate.
The SSLCertStoreType property denotes the type of the certificate store specified by SSLCertStore. If the store is password protected, specify the password in SSLCertStorePassword.
SSLCertStore is used in conjunction with the SSLCertSubject property to specify client certificates. If SSLCertStore has a value, and SSLCertSubject or SSLCertEncoded is set, a search for a certificate is initiated. Please see the SSLCertSubject property for details.
Designations of certificate stores are platform dependent.
The following designations are the most common User and Machine certificate stores in Windows:
MY | A certificate store holding personal certificates with their associated private keys. |
CA | Certifying authority certificates. |
ROOT | Root certificates. |
When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).
Data Type
Binary String
SSLCertStorePassword Property (DPaymentsSDK_PTechCanadianDebit Class)
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
Object Oriented Interface
public function getSSLCertStorePassword(); public function setSSLCertStorePassword($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 84 ); dpaymentssdk_ptechcanadiandebit_set($res, 84, $value );
Default Value
''
Remarks
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
Data Type
String
SSLCertStoreType Property (DPaymentsSDK_PTechCanadianDebit Class)
This is the type of certificate store for this certificate.
Object Oriented Interface
public function getSSLCertStoreType(); public function setSSLCertStoreType($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 85 ); dpaymentssdk_ptechcanadiandebit_set($res, 85, $value );
Default Value
0
Remarks
This is the type of certificate store for this certificate.
The class supports both public and private keys in a variety of formats. When the cstAuto value is used, the class will automatically determine the type. This property can take one of the following values:
0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user.
Note: This store type is not available in Java. |
1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store.
Note: This store type is not available in Java. |
2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. |
3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. |
4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates.
Note: This store type is only available in Java. |
5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format.
Note: this store type is only available in Java. |
6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. |
8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. |
11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. |
12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. |
13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store).
Note: This store type is only available in Java and .NET. |
22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format.
Note: This store type is only available in Java and .NET. |
23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface.
To use a security key, the necessary data must first be collected using the CertMgr class. The ListStoreCertificates method may be called after setting CertStoreType to cstPKCS11, CertStorePassword to the PIN, and CertStore to the full path of the PKCS#11 DLL. The certificate information returned in the CertList event's CertEncoded parameter may be saved for later use. When using a certificate, pass the previously saved security key information as the SSLCertStore and set SSLCertStorePassword to the PIN. Code Example. SSH Authentication with Security Key:
|
99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |
Data Type
Integer
SSLCertSubject Property (DPaymentsSDK_PTechCanadianDebit Class)
This is the subject of the certificate used for client authentication.
Object Oriented Interface
public function getSSLCertSubject(); public function setSSLCertSubject($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 86 ); dpaymentssdk_ptechcanadiandebit_set($res, 86, $value );
Default Value
''
Remarks
This is the subject of the certificate used for client authentication.
This property must be set after all other certificate properties are set. When this property is set, a search is performed in the current certificate store to locate a certificate with a matching subject.
If a matching certificate is found, the property is set to the full subject of the matching certificate.
If an exact match is not found, the store is searched for subjects containing the value of the property.
If a match is still not found, the property is set to an empty string, and no certificate is selected.
The special value "*" picks a random certificate in the certificate store.
The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=support@nsoftware.com". Common fields and their meanings are as follows:
Field | Meaning |
CN | Common Name. This is commonly a hostname like www.server.com. |
O | Organization |
OU | Organizational Unit |
L | Locality |
S | State |
C | Country |
E | Email Address |
If a field value contains a comma, it must be quoted.
Data Type
String
SSLProvider Property (DPaymentsSDK_PTechCanadianDebit Class)
This specifies the SSL/TLS implementation to use.
Object Oriented Interface
public function getSSLProvider(); public function setSSLProvider($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 94 ); dpaymentssdk_ptechcanadiandebit_set($res, 94, $value );
Default Value
0
Remarks
This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic) the class will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.
Possible values are:
0 (sslpAutomatic - default) | Automatically selects the appropriate implementation. |
1 (sslpPlatform) | Uses the platform/system implementation. |
2 (sslpInternal) | Uses the internal implementation. |
In most cases using the default value (Automatic) is recommended. The class will select a provider depending on the current platform.
When Automatic is selected, on Windows the class will use the platform implementation. On Linux/macOS the class will use the internal implementation. When TLS 1.3 is enabled via SSLEnabledProtocols the internal implementation is used on all platforms.
Data Type
Integer
SSLServerCertEncoded Property (DPaymentsSDK_PTechCanadianDebit Class)
This is the certificate (PEM/Base64 encoded).
Object Oriented Interface
public function getSSLServerCertEncoded();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 96 );
Default Value
''
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLServerCertStore and SSLServerCertSubject properties also may be used to specify a certificate.
When SSLServerCertEncoded is set, a search is initiated in the current SSLServerCertStore for the private key of the certificate. If the key is found, SSLServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLServerCertSubject is set to an empty string.
This property is read-only and not available at design time.
Data Type
Binary String
TerminalNumber Property (DPaymentsSDK_PTechCanadianDebit Class)
Terminal number assigned by Paymentech.
Object Oriented Interface
public function getTerminalNumber(); public function setTerminalNumber($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 123 ); dpaymentssdk_ptechcanadiandebit_set($res, 123, $value );
Default Value
''
Remarks
3-digit field assigned by Paymentech, which identifies the terminal to the host.
Data Type
String
Timeout Property (DPaymentsSDK_PTechCanadianDebit Class)
A timeout for the class.
Object Oriented Interface
public function getTimeout(); public function setTimeout($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 124 ); dpaymentssdk_ptechcanadiandebit_set($res, 124, $value );
Default Value
60
Remarks
If the Timeout property is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered.
If Timeout is set to a positive value, the class will wait for the operation to complete before returning control.
The class will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not "freeze" and remains responsive.
If Timeout expires, and the operation is not yet complete, the class fails with an error.
Please note that by default, all timeouts are inactivity timeouts, i.e. the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.
The default value for the Timeout property is 60 seconds.
Data Type
Integer
TransactionAmount Property (DPaymentsSDK_PTechCanadianDebit Class)
Purchase amount for an authorization.
Object Oriented Interface
public function getTransactionAmount(); public function setTransactionAmount($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 125 ); dpaymentssdk_ptechcanadiandebit_set($res, 125, $value );
Default Value
''
Remarks
This field contains the transaction amount to be authorized. The transaction amount is presented in CA Dollars with a decimal point in the proper position. If sending a Debit transaction and the customer requests cash back, the TransactionAmount must include the total cost of the purchase, PLUS the DebitCashBack amount.
This must be formatted as a dollar amount with a real decimal point, excluding the dollar sign. For instance "12.00"
Data Type
String
UserId Property (DPaymentsSDK_PTechCanadianDebit Class)
UserId for authentication with the NetConnect Server .
Object Oriented Interface
public function getUserId(); public function setUserId($value);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_get($res, 126 ); dpaymentssdk_ptechcanadiandebit_set($res, 126, $value );
Default Value
''
Remarks
The UserId will be supplied to you by PaymenTech.
Data Type
String
Authorize Method (DPaymentsSDK_PTechCanadianDebit Class)
Authorizes a Canadian debit card transaction.
Object Oriented Interface
public function doAuthorize();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_authorize($res);
Remarks
This method sends a Canadian (Interac) debit card transaction to the Paymentech Server The transaction sent is based on the InteracTransactionType. Authorize can only be used to send customer-initiated transactions that require that the customer physically enter his PIN on the PIN pad device - meaning Sales, Returns, and Voids. Administrative transactions are handled via the RequestCurrentKeys, ReversalAdvice, and MACReversal methods.
An example sale is shown below:
class.MerchantNumber = "yourMerchantNumber"
class.TerminalNumber = "100"
class.ClientNumber = "0002"
class.UserId = "yourUserId"
class.Password = "yourPassword"
class.SequenceNumber = 2
class.TransactionAmount = "1.00"
class.PinPadSerialNumber = "30700015P3600000" ' from label on back of PIN pad
class.InteracTransactionType = ittSale
class.AccountType = acctChecking
class.CardTrack2Data = "9999999800002773=05121015432112345678" ' from card reader
class.EncryptedPIN = "FFFFFFFFFFFFFFFF" ' from the PIN pad
' Now use the PIN pad to MAC the value returned from GetRequestDataToMAC
' and then set MACValue with the results
class.MACValue = "FFFFFFFF"
class.Authorize()
If the ResponseCode is "A", load the PIN pad device with the
ResponsePINKey and ResponseMACKey, and then validate the ResponseMACValue
against the value returned by GetResponseDataToMAC using the PIN pad. If the MAC does
not validate, call MACReversal to reverse the transaction.
Config Method (DPaymentsSDK_PTechCanadianDebit Class)
Sets or retrieves a configuration setting.
Object Oriented Interface
public function doConfig($configurationstring);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_config($res, $configurationstring);
Remarks
Config is a generic method available in every class. It is used to set and retrieve configuration settings for the class.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
GetRequestDataToMAC Method (DPaymentsSDK_PTechCanadianDebit Class)
Returns a string of data for the PIN pad to hash with the MAC algorithm.
Object Oriented Interface
public function doGetRequestDataToMAC();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_getrequestdatatomac($res);
Remarks
Each transaction you send (excluding RequestCurrentKeys and MACReversals) requires an accompanying MACValue. This value is a hash of the contents of GetRequestDataToMAC, and is hashed by the PIN Pad device using the ResponseMACKey returned in response to the last transaction.
The GetRequestDataToMAC method returns a string containing the values of several transaction properties. This string must be MAC'ed by the PIN pad, so it is essential that the following properties be set before calling GetRequestDataToMAC:
- MerchantNumber
- TerminalNumber
- InteracTransactionType
- CardTrack2Data
- TransactionAmount
- SequenceNumber
- and optionally AccountType
Note that VeriFone pinpads support a PURCHASE transaction where the CardTrack2Data, EncryptedPIN, AccountType, and MACValue are returned in a single step. When using a VeriFone pad make sure AccountType is set to acctNotSet, otherwise the MACValue will not be calculated correctly. (AccountType must be set before calling GetRequestDataToMAC for Ingenico pads)
class.MerchantNumber = "yourMerchantNumber"
class.TerminalNumber = "100"
class.ClientNumber = "0002"
class.UserId = "yourUserId"
class.Password = "yourPassword"
class.SequenceNumber = 2
class.TransactionAmount = "1.00"
class.PinPadSerialNumber = "30700015P3600000" ' from label on back of PIN pad
class.InteracTransactionType = ittSale
class.AccountType = acctChecking
class.CardTrack2Data = "9999999800002773=05121015432112345678" ' from card reader
class.EncryptedPIN = "FFFFFFFFFFFFFFFF" ' from the PIN pad
' Now use the PIN pad to MAC the value returned from GetRequestDataToMAC
' and then set MACValue with the results
class.MACValue = "FFFFFFFF"
class.Authorize()
GetResponseDataToMAC Method (DPaymentsSDK_PTechCanadianDebit Class)
Returns a string containing data to validate against the MACValue using a PIN pad device.
Object Oriented Interface
public function doGetResponseDataToMAC();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_getresponsedatatomac($res);
Remarks
Each successful response to a transaction will include a ResponseMACKey and a ResponseMACValue. The ResponseMACKey (and ResponsePINKey) should be loaded into the PIN pad device upon receipt. The ResponseMACValue is a string encrypted by the Paymentech server using the ResponseMACKey, and is included in every successful response message. The original unencrypted data is returned by the GetResponseDataToMAC method. After loading the ResponseMACKey into the PIN pad device, send both ResponseMACValue and GetResponseDataToMAC to the PIN pad device for validation. If the PIN pad indicates the MAC matches, you're done, and you can continue processing transactions. However, if the PIN pad indicates the MAC did not match, you must immediately perform a MACReversal transaction, and consider the request as not approved.
A mismatched MAC value may mean that something was corrupted in data transmission, the response packet was tampered with, or that the keys loaded into your PIN pad device are not synchronized with Paymentech. Try synchronizing your keys with the RequestCurrentKeys method and then re-submitting the transaction.
Interrupt Method (DPaymentsSDK_PTechCanadianDebit Class)
Interrupt the current method.
Object Oriented Interface
public function doInterrupt();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_interrupt($res);
Remarks
If there is no method in progress, Interrupt simply returns, doing nothing.
MACReversal Method (DPaymentsSDK_PTechCanadianDebit Class)
Reverses a transaction when MAC validation fails.
Object Oriented Interface
public function doMACReversal();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_macreversal($res);
Remarks
After sending a transaction with the Authorize method, the ResponseMACValue must be validated against the GetResponseDataToMAC using the PIN pad device's MAC functionality. It must be validated under the latest ResponseMACKey returned from Paymentech. If the ResponseMACValue cannot be validated, you should immediately send a MACReversal to void the authorization. Note that you do not need to calculate a new MACValue for a MACReversal. You may simply send the MACValue from the original authorization request (the Paymentech server will not validate the MACValue). All other properties must match the properties sent during the original authorization, including the EncryptedPIN, CardTrack2Data, and EncryptedKeyIndex.
RequestCurrentKeys Method (DPaymentsSDK_PTechCanadianDebit Class)
Used to retrieve the current encryption keys from Paymentech.
Object Oriented Interface
public function doRequestCurrentKeys();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_requestcurrentkeys($res);
Remarks
This method retrieves the current encryption keys from Paymentech, and stores them in the ResponsePINKey and ResponseMACKey properties. These keys are used by the PIN pad device to encrypt customer PINs and to create and validate MAC hash values, and are normally updated after every Authorize transaction. But when the PIN pad is first initialized (or when the PIN pad becomes out of sync with the Paymentech Server) you must retrieve the current keys using this method.
Keys are required to be renewed every:
- 200 Transactions
- 24 Hours
- Each time a Batch is released for settlement
- Whenever the PIN pad loses sync with the server
If the ResponseForceKeyRequest property is True after any transaction, you must immediately perform a RequestCurrentKeys transaction before sending any more authorizations.
For example:
class.MerchantNumber = "yourMerchantNumber"
class.TerminalNumber = "100"
class.ClientNumber = "0002"
class.UserId = "yourUserId"
class.Password = "yourPassword"
class.SequenceNumber = 1
class.PinPadSerialNumber = "FFFFFFFFFFFFFFFF" ' retrieved from your PIN Pad
class.RequestCurrentKeys()
Now load the
ResponsePINKey and ResponseMACKey into the PIN Pad device.
Reset Method (DPaymentsSDK_PTechCanadianDebit Class)
Clears all properties to their default values.
Object Oriented Interface
public function doReset();
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_reset($res);
Remarks
This method clears all properties to their default values.
ReversalAdvice Method (DPaymentsSDK_PTechCanadianDebit Class)
Used if no response is received from the Server to void the authorization.
Object Oriented Interface
public function doReversalAdvice($originaltransactiontype, $reasoncode);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_do_reversaladvice($res, $originaltransactiontype, $reasoncode);
Remarks
If no response is returned after sending an authorization with the Authorize method, and the status of the response is unknown, you must send a ReversalAdvice transaction. This will advise the Paymentech Server that you did not receive a response to your authorization request, and that the original request is to be voided. If no request is found (meaning your original authorization request never made it to Paymentech) or if the authorization is successfully reversed (ResponseCode is "A"), you may try to resubmit the transaction.
This method takes two parameters, OriginalTransactionType and Reason Code. The former indicates the InteracTransactionType of the original authorization, and the latter indicates the reason for the reversal. Allowable values for these parameters are listed below:
Allowable OriginalTransactionType values:
27 | ittSale |
28 | ittSaleWithCashBack |
29 | ittReturn |
Reason Code values:
1 | No response from host |
2 | Late response from host |
3 | Unable to deliver to PIN pad |
DataPacketIn Event (DPaymentsSDK_PTechCanadianDebit Class)
Fired when receiving a data packet from the transaction server.
Object Oriented Interface
public function fireDataPacketIn($param);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_register_callback($res, 1, array($this, 'fireDataPacketIn'));
Parameter List
'datapacket'
Remarks
This event fires when a packet is received. The entire data packet (including all framing and error detection characters) is contained in the parameter "DataPacket". This parameter may be inspected for advanced troubleshooting, or to extract additional response properties beyond the scope of this class.
DataPacketOut Event (DPaymentsSDK_PTechCanadianDebit Class)
Fired when sending a data packet to the transaction server.
Object Oriented Interface
public function fireDataPacketOut($param);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_register_callback($res, 2, array($this, 'fireDataPacketOut'));
Parameter List
'datapacket'
Remarks
This event fires right before each data packet is sent. The entire data packet (including all framing and error detection characters) is contained in the parameter "DataPacket". This parameter may be inspected for advanced troubleshooting.
Error Event (DPaymentsSDK_PTechCanadianDebit Class)
Information about errors during data delivery.
Object Oriented Interface
public function fireError($param);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_register_callback($res, 3, array($this, 'fireError'));
Parameter List
'errorcode'
'description'
Remarks
The Error event is fired in case of exceptional conditions during message processing.
ErrorCode contains an error code and Description contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.
SSLServerAuthentication Event (DPaymentsSDK_PTechCanadianDebit Class)
Fired after the server presents its certificate to the client.
Object Oriented Interface
public function fireSSLServerAuthentication($param);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_register_callback($res, 4, array($this, 'fireSSLServerAuthentication'));
Parameter List
'certencoded'
'certsubject'
'certissuer'
'status'
'accept'
Remarks
During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.
When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.
SSLStatus Event (DPaymentsSDK_PTechCanadianDebit Class)
Fired when secure connection progress messages are available.
Object Oriented Interface
public function fireSSLStatus($param);
Procedural Interface
dpaymentssdk_ptechcanadiandebit_register_callback($res, 5, array($this, 'fireSSLStatus'));
Parameter List
'message'
Remarks
The event is fired for informational and logging purposes only. This event tracks the progress of the connection.
Config Settings (PTechCanadianDebit Class)
The class accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.PTechCanadianDebit Config Settings
Valid values are:
Value | Device Capability | Presentation Method | Supported Card Types/Comments | |
36 | Chip and Contactless Capable | Track 2 read from inserted | Allowed on American Express, Canadian Debit, ChaseNet, Discover, International Maestro, JCB, MasterCard, *US Debit and Visa transactions | |
37 | Chip and Contactless Capable | Insert attempted, fall back to Track 1 from swiped | Allowed on American Express, ChaseNet, International Maestro, JCB, MasterCard and Visa transactions | |
38 | Chip and Contactless Capable | Insert attempted, fall back to Track 2 from swiped | Allowed on American Express, Canadian Debit, ChaseNet, Discover, International Maestro, JCB, MasterCard, *US Debit and Visa transactions | |
39 | Chip and Contactless Capable | Insert attempted, swipe attempted, fall back to keyed/ manually entered | Allowed on American Express, ChaseNet, Discover, International Maestro, JCB, MasterCard and Visa transactions | |
40 | Chip and Contactless Capable | Track 1 read from proximity w/chip | Allowed on American Express, ChaseNet, MasterCard and Visa transactions | |
41 | Chip and Contactless Capable | Track 2 read from proximity w/chip | Allowed on American Express, Canadian Debit, ChaseNet, Discover, MasterCard, *US Debit and Visa transactions | |
42 | Chip and Contactless Capable | Track 1 read from proximity w/mag stripe | Allowed on American Express, ChaseNet, Discover, MasterCard and Visa transactions | |
43 | Chip and Contactless Capable | Track 2 read from proximity w/mag stripe | Allowed on American Express, Canadian Debit, ChaseNet, Discover, MasterCard, *US Debit and Visa transactions | |
44 | Chip and Contactless Capable | Track 1 read from swiped | Allowed on all card types except US Debit, Canadian Debit, EBT, and stored value | |
45 | Chip and Contactless Capable | Track 2 read from swiped | Allowed on all card types | |
46 | Chip and Contactless Capable | Keyed / Manually Entered | Allowed on all card types except US Debit and Canadian Debit (note that this code is permitted on Debit Reversal Advices however) | |
48 | Chip (but not Contactless) Capable | Track 2 read from inserted | Allowed on American Express, Canadian Debit, ChaseNet, Discover, International Maestro, JCB, MasterCard, *US Debit and Visa transactions | |
49 | Chip (but not Contactless) Capable | Insert attempted, fall back to Track 1 from Swiped | Allowed on American Express, ChaseNet, International Maestro, JCB, MasterCard and Visa transactions | |
50 | Chip (but not Contactless) Capable | Insert attempted, fall back to Track 2 from Swiped | Allowed on American Express, Canadian Debit, ChaseNet, Discover, International Maestro, JCB, MasterCard, *US Debit and Visa transactions | |
51 | Chip (but not Contactless) Capable | Insert attempted, swipe attempted, fall back to manually entered | Allowed on American Express, ChaseNet, Discover, International Maestro, JCB, MasterCard and Visa transactions | |
52 | Chip (but not Contactless) Capable | Track 1 from swiped | Allowed on all card types except US Debit, Canadian Debit, EBT, and stored value. | |
53 | Chip (but not Contactless) Capable | Track 2 from swiped | Allowed on all card types | |
54 | Chip (but not Contactless) Capable | Keyed / Manually Entered | Allowed on all card types except US Debit and Canadian Debit. | |
55 | Contactless Capable | Barcode read | Allowed on American Express only. | |
56 | Chip and Contactless Capable | Barcode read | Allowed on American Express only. | |
57 | Chip (but not Contactless) Capable | Barcode read | Allowed on American Express only. |
0 | Host Capture (default) |
1 | Terminal Capture |
Note that for PTechReversal, 1 (Terminal Capture) will be the default value. If Host Capture is being used, a value of 0 will need to be set.
Host-Capture means that you authorize your transactions using the AuthOnly or Sale methods, and you process refunds and capture outstanding authorizations with the Credit and Capture methods. Paymentech handles all batch management. All you need to do is use the PTechHostSettle class to release the batch for settlement (you may even set your account up for Host Auto-Close, which will automatically release the batch for settlement at the end of the business day).
Terminal-Capture means that you handle all of the batch management yourself. This is necessary for the Hotel/Lodging and Restaurant IndustryTypes, because the final settlement amount may be more than (or less than) the amount that was originally authorized. For instance, a restaurant authorization may have a GratuityAmount added to the original charge before the transaction is settled. Likewise, a customer may stay longer or shorter than originally planned, or incur additional charges (mini bar, telephone call, room service, etc), and the settlement amount must be adjusted accordingly.
All industry types supported by PTechCharge may be processed in smTerminalCapture mode. However, Restaurant and Hotel transactions MUST be authorized and settled in smTerminalCapture mode. Attempting to authorize a Restaurant or Hotel/Lodging transaction with the SettlementMode; set to 0 (Host Capture) will cause the class fails with an error.
When processing transactions in smTerminalCapture mode, credits and captures are processed off-line using the PTechDetailRecord and PTechManualSettle classs. Attempting to call the VoidTransaction or Capture methods the class fails with an error.
The class will construct the System Information data based on the following specifications:
- Application Name - 7 characters
- Release Date - 6 characters (MMDDYY)
- EPROM / Version Number - 10 characters
HTTP Config Settings
When True, the class adds an Accept-Encoding header to the outgoing request. The value for this header can be controlled by the AcceptEncoding configuration setting. The default value for this header is "gzip, deflate".
The default value is True.
If set to True (default), the class will automatically use HTTP/1.1 if the server does not support HTTP/2. If set to False, the class fails with an error if the server does not support HTTP/2.
The default value is True.
This property is provided so that the HTTP class can be extended with other security schemes in addition to the authorization schemes already implemented by the class.
The AuthScheme property defines the authentication scheme used. In the case of HTTP Basic Authentication (default), every time User and Password are set, they are Base64 encoded, and the result is put in the Authorization property in the form "Basic [encoded-user-password]".
The default value is False.
If this property is set to 2 (Same Scheme), the new URL is retrieved automatically only if the URL Scheme is the same; otherwise, the class fails with an error.
Note: Following the HTTP specification, unless this option is set to 1 (Always), automatic redirects will be performed only for GET or HEAD requests. Other methods potentially could change the conditions of the initial request and create security vulnerabilities.
Furthermore, if either the new URL server or port are different from the existing one, User and Password are also reset to empty, unless this property is set to 1 (Always), in which case the same credentials are used to connect to the new server.
A Redirect event is fired for every URL the product is redirected to. In the case of automatic redirections, the Redirect event is a good place to set properties related to the new connection (e.g., new authentication parameters).
The default value is 0 (Never). In this case, redirects are never followed, and the class fails with an error instead.
Following are the valid options:
- 0 - Never
- 1 - Always
- 2 - Same Scheme
- "1.0"
- "1.1" (default)
- "2.0"
- "3.0"
When using HTTP/2 ("2.0"), additional restrictions apply. Please see the following notes for details.
HTTP/2 Notes
When using HTTP/2, a secure Secure Sockets Layer/Transport Layer Security (TLS/SSL) connection is required. Attempting to use a plaintext URL with HTTP/2 will result in an error.
If the server does not support HTTP/2, the class will automatically use HTTP/1.1 instead. This is done to provide compatibility without the need for any additional settings. To see which version was used, check NegotiatedHTTPVersion after calling a method. The AllowHTTPFallback setting controls whether this behavior is allowed (default) or disallowed.
HTTP/3 Notes
HTTP/3 is supported only in .NET and Java.
When using HTTP/3, a secure (TLS/SSL) connection is required. Attempting to use a plaintext URL with HTTP/3 will result in an error.
The format of the date value for IfModifiedSince is detailed in the HTTP specs. For example:
Sat, 29 Oct 2017 19:43:31 GMT.
The default value for KeepAlive is false.
0 (None) | No events are logged. |
1 (Info - default) | Informational events are logged. |
2 (Verbose) | Detailed data are logged. |
3 (Debug) | Debug data are logged. |
The value 1 (Info) logs basic information, including the URL, HTTP version, and status details.
The value 2 (Verbose) logs additional information about the request and response.
The value 3 (Debug) logs the headers and body for both the request and response, as well as additional debug information (if any).
The headers must follow the format "header: value" as described in the HTTP specifications. Header lines should be separated by CRLF ("\r\n") .
Use this configuration setting with caution. If this configuration setting contains invalid headers, HTTP requests may fail.
This configuration setting is useful for extending the functionality of the class beyond what is provided.
.NET
Http http = new Http();
http.Config("TransferredRequest=on");
http.PostData = "body";
http.Post("http://someserver.com");
Console.WriteLine(http.Config("TransferredRequest"));
C++
HTTP http;
http.Config("TransferredRequest=on");
http.SetPostData("body", 5);
http.Post("http://someserver.com");
printf("%s\r\n", http.Config("TransferredRequest"));
Note: Some servers (such as the ASP.NET Development Server) may not support chunked encoding.
The default value is False and the hostname will always be used exactly as specified. Note: The CodePage setting must be set to a value capable of interpreting the specified host name. For instance, to specify UTF-8, set CodePage to 65001. In the C++ Edition for Windows, the *W version of the class must be used. For instance, DNSW or HTTPW.
Note: This setting is applicable only to Mac/iOS editions.
When True (default), the class will check for the existence of a Proxy auto-config URL, and if found, will determine the appropriate proxy to use.
Override the default with the name and version of your software.
TCPClient Config Settings
If the FirewallHost setting is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, the FirewallHost setting is set to the corresponding address. If the search is not successful, an error is returned.
Note: This setting is provided for use by classs that do not directly expose Firewall properties.
Note: This setting is provided for use by classs that do not directly expose Firewall properties.
Note: This configuration setting is provided for use by classs that do not directly expose Firewall properties.
0 | No firewall (default setting). |
1 | Connect through a tunneling proxy. FirewallPort is set to 80. |
2 | Connect through a SOCKS4 Proxy. FirewallPort is set to 1080. |
3 | Connect through a SOCKS5 Proxy. FirewallPort is set to 1080. |
10 | Connect through a SOCKS4A Proxy. FirewallPort is set to 1080. |
Note: This setting is provided for use by classs that do not directly expose Firewall properties.
Note: This setting is provided for use by classs that do not directly expose Firewall properties.
Note: This value is not applicable in macOS.
In the case that Linger is True (default), two scenarios determine how long the connection will linger. In the first, if LingerTime is 0 (default), the system will attempt to send pending data for a connection until the default IP timeout expires.
In the second scenario, if LingerTime is a positive value, the system will attempt to send pending data until the specified LingerTime is reached. If this attempt fails, then the system will reset the connection.
The default behavior (which is also the default mode for stream sockets) might result in a long delay in closing the connection. Although the class returns control immediately, the system could hold system resources until all pending data are sent (even after your application closes).
Setting this property to False forces an immediate disconnection. If you know that the other side has received all the data you sent (e.g., by a client acknowledgment), setting this property to False might be the appropriate course of action.
In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the class initiate connections (or accept in the case of server classs) only through that interface.
If the class is connected, the LocalHost setting shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multi-homed hosts (machines with more than one IP interface).
Setting this to 0 (default) enables the system to choose a port at random. The chosen port will be shown by LocalPort after the connection is established.
LocalPort cannot be changed once a connection is made. Any attempt to set this when a connection is active will generate an error.
This; setting is useful when trying to connect to services that require a trusted port in the client side. An example is the remote shell (rsh) service in UNIX systems.
If an EOL string is found in the input stream before MaxLineLength bytes are received, the DataIn event is fired with the EOL parameter set to True, and the buffer is reset.
If no EOL is found, and MaxLineLength bytes are accumulated in the buffer, the DataIn event is fired with the EOL parameter set to False, and the buffer is reset.
The minimum value for MaxLineLength is 256 bytes. The default value is 2048 bytes.
www.google.com;www.nsoftware.com
Note: This value is not applicable in Java.
By default, this config is set to false.
0 | IPv4 Only |
1 | IPv6 Only |
2 | IPv6 with IPv4 fallback |
SSL Config Settings
When enabled, SSL packet logs are output using the SSLStatus event, which will fire each time an SSL packet is sent or received.
Enabling this setting has no effect if SSLProvider is set to Platform.
The path set by this property should point to a directory containing CA certificates in PEM format. The files each contain one CA certificate. The files are looked up by the CA subject name hash value, which must hence be available. If more than one CA certificate with the same name hash value exist, the extension must be different (e.g. 9d66eef0.0, 9d66eef0.1 etc). OpenSSL recommends to use the c_rehash utility to create the necessary links. Please refer to the OpenSSL man page SSL_CTX_load_verify_locations(3) for details.
The file set by this property should contain a list of CA certificates in PEM format. The file can contain several CA certificates identified by
-----BEGIN CERTIFICATE-----
... (CA certificate in base64 encoding) ...
-----END CERTIFICATE-----
sequences. Before, between, and after the certificates text is allowed which can be used e.g. for descriptions of the certificates. Please refer to the OpenSSL man page SSL_CTX_load_verify_locations(3) for details.
The format of this string is described in the OpenSSL man page ciphers(1) section "CIPHER LIST FORMAT". Please refer to it for details. The default string "DEFAULT" is determined at compile time and is normally equivalent to "ALL:!ADH:RC4+RSA:+SSLv2:@STRENGTH".
By default OpenSSL uses the device file "/dev/urandom" to seed the PRNG and setting OpenSSLPrngSeedData is not required. If set, the string specified is used to seed the PRNG.
If set to true, the class will reuse the context if and only if the following criteria are met:
- The target host name is the same.
- The system cache entry has not expired (default timeout is 10 hours).
- The application process that calls the function is the same.
- The logon session is the same.
- The instance of the class is the same.
The value is formatted as a list of paths separated by semicolons. The class will check for the existence of each file in the order specified. When a file is found the CA certificates within the file will be loaded and used to determine the validity of server or client certificates.
The default value is:
/etc/ssl/ca-bundle.pem;/etc/pki/tls/certs/ca-bundle.crt;/etc/ssl/certs/ca-certificates.crt;/etc/pki/tls/cacert.pem
-----BEGIN CERTIFICATE----- MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw ... eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w F0I1XhM+pKj7FjDr+XNj -----END CERTIFICATE----- \r \n -----BEGIN CERTIFICATE----- MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp .. d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA -----END CERTIFICATE-----
When set to 0 (default) the CRL check will not be performed by the class. When set to 1, it will attempt to perform the CRL check, but will continue without an error if the server's certificate does not support CRL. When set to 2, it will perform the CRL check and will throw an error if CRL is not supported.
This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems.
When set to 0 (default) the class will not perform an OCSP check. When set to 1, it will attempt to perform the OCSP check, but will continue without an error if the server's certificate does not support OCSP. When set to 2, it will perform the OCSP check and will throw an error if OCSP is not supported.
This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems.
Please note that this setting contains the minimum cipher strength requested from the security library. The actual cipher strength used for the connection is shown by the SSLStatus event.
Use this setting with caution. Requesting a lower cipher strength than necessary could potentially cause serious security vulnerabilities in your application.
When the provider is OpenSSL, SSLCipherStrength is currently not supported. This functionality is instead made available through the OpenSSLCipherList config setting.
By default, the enabled cipher suites will include all available ciphers ("*").
The special value "*" means that the class will pick all of the supported cipher suites. If SSLEnabledCipherSuites is set to any other value, only the specified cipher suites will be considered.
Multiple cipher suites are separated by semicolons.
Example values when SSLProvider is set to Platform:
obj.config("SSLEnabledCipherSuites=*");
obj.config("SSLEnabledCipherSuites=CALG_AES_256");
obj.config("SSLEnabledCipherSuites=CALG_AES_256;CALG_3DES");
Possible values when SSLProvider is set to Platform include:
- CALG_3DES
- CALG_3DES_112
- CALG_AES
- CALG_AES_128
- CALG_AES_192
- CALG_AES_256
- CALG_AGREEDKEY_ANY
- CALG_CYLINK_MEK
- CALG_DES
- CALG_DESX
- CALG_DH_EPHEM
- CALG_DH_SF
- CALG_DSS_SIGN
- CALG_ECDH
- CALG_ECDH_EPHEM
- CALG_ECDSA
- CALG_ECMQV
- CALG_HASH_REPLACE_OWF
- CALG_HUGHES_MD5
- CALG_HMAC
- CALG_KEA_KEYX
- CALG_MAC
- CALG_MD2
- CALG_MD4
- CALG_MD5
- CALG_NO_SIGN
- CALG_OID_INFO_CNG_ONLY
- CALG_OID_INFO_PARAMETERS
- CALG_PCT1_MASTER
- CALG_RC2
- CALG_RC4
- CALG_RC5
- CALG_RSA_KEYX
- CALG_RSA_SIGN
- CALG_SCHANNEL_ENC_KEY
- CALG_SCHANNEL_MAC_KEY
- CALG_SCHANNEL_MASTER_HASH
- CALG_SEAL
- CALG_SHA
- CALG_SHA1
- CALG_SHA_256
- CALG_SHA_384
- CALG_SHA_512
- CALG_SKIPJACK
- CALG_SSL2_MASTER
- CALG_SSL3_MASTER
- CALG_SSL3_SHAMD5
- CALG_TEK
- CALG_TLS1_MASTER
- CALG_TLS1PRF
obj.config("SSLEnabledCipherSuites=*");
obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA");
obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA;TLS_DH_ANON_WITH_AES_128_CBC_SHA");
Possible values when SSLProvider is set to Internal include:
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_RSA_WITH_AES_256_GCM_SHA384
- TLS_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_DSS_WITH_AES_256_GCM_SHA384
- TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_DSS_WITH_AES_128_GCM_SHA256
- TLS_DH_RSA_WITH_AES_128_GCM_SHA256 (Not Recommended)
- TLS_DH_RSA_WITH_AES_256_GCM_SHA384 (Not Recommended)
- TLS_DH_DSS_WITH_AES_128_GCM_SHA256 (Not Recommended)
- TLS_DH_DSS_WITH_AES_256_GCM_SHA384 (Not Recommended)
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
- TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
- TLS_RSA_WITH_AES_256_CBC_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
- TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
- TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
- TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- TLS_RSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
- TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
- TLS_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
- TLS_DHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
- TLS_DHE_DSS_WITH_AES_256_CBC_SHA
- TLS_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
- TLS_DHE_RSA_WITH_AES_128_CBC_SHA
- TLS_DHE_DSS_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_DES_CBC_SHA
- TLS_DHE_RSA_WITH_DES_CBC_SHA
- TLS_DHE_DSS_WITH_DES_CBC_SHA
- TLS_RSA_WITH_RC4_128_MD5
- TLS_RSA_WITH_RC4_128_SHA
When TLS 1.3 is negotiated (see SSLEnabledProtocols) only the following cipher suites are supported:
- TLS_AES_256_GCM_SHA384
- TLS_CHACHA20_POLY1305_SHA256
- TLS_AES_128_GCM_SHA256
SSLEnabledCipherSuites is used together with SSLCipherStrength.
Not all supported protocols are enabled by default (the value of this setting is 4032). If you want more granular control over the enabled protocols, you can set this property to the binary 'OR' of one or more of the following values:
TLS1.3 | 12288 (Hex 3000) |
TLS1.2 | 3072 (Hex C00) (Default) |
TLS1.1 | 768 (Hex 300) (Default) |
TLS1 | 192 (Hex C0) (Default) |
SSL3 | 48 (Hex 30) [Platform Only] |
SSL2 | 12 (Hex 0C) [Platform Only] |
SSLEnabledProtocols - TLS 1.3 Notes
By default when TLS 1.3 is enabled the class will use the internal TLS implementation when the SSLProvider is set to Automatic for all editions.
In editions which are designed to run on Windows SSLProvider can be set to Platform to use the platform implementation instead of the internal implementation. When configured in this manner, please note that the platform provider is only supported on Windows 11 / Windows Server 2022 and up. The default internal provider is available on all platforms and is not restricted to any specific OS version.
If set to 1 (Platform provider) please be aware of the following notes:
- The platform provider is only available on Windows 11 / Windows Server 2022 and up.
- SSLEnabledCipherSuites and other similar SSL configuration settings are not supported.
- If SSLEnabledProtocols includes both TLS 1.3 and TLS 1.2 the above restrictions are still applicable even if TLS 1.2 is negotiated. Enabling TLS 1.3 with the platform provider changes the implementation used for all TLS versions.
SSLEnabledProtocols: SSL2 and SSL3 Notes:
SSL 2.0 and 3.0 are not supported by the class when the SSLProvider is set to internal. To use SSL 2.0 or SSL 3.0, the platform security API must have the protocols enabled and SSLProvider needs to be set to platform.
This setting is only applicable when SSLProvider is set to Internal.
If set to True all certificates returned by the server will be present in the Encoded parameter of the SSLServerAuthentication event. This includes the leaf certificate, any intermediate certificate, and the root certificate.
When set, the class will save the session secrets in the same format as the SSLKEYLOGFILE environment variable functionality used by most major browsers and tools such as Chrome, Firefox, and cURL. This file can then be used in tools such as Wireshark to decrypt TLS traffice for debugging purposes. When writing to this file the class will only append, it will not overwrite previous values.
Note: This setting is only applicable when SSLProvider is set to Internal.
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipher[connId]");
Note: For server components (e.g.TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipherStrength[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipherSuite[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedKeyExchange[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedKeyExchangeStrength[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedVersion[connId]");
0x00000001 | Ignore time validity status of certificate. |
0x00000002 | Ignore time validity status of CTL. |
0x00000004 | Ignore non-nested certificate times. |
0x00000010 | Allow unknown Certificate Authority. |
0x00000020 | Ignore wrong certificate usage. |
0x00000100 | Ignore unknown certificate revocation status. |
0x00000200 | Ignore unknown CTL signer revocation status. |
0x00000400 | Ignore unknown Certificate Authority revocation status. |
0x00000800 | Ignore unknown Root revocation status. |
0x00008000 | Allow test Root certificate. |
0x00004000 | Trust test Root certificate. |
0x80000000 | Ignore non-matching CN (certificate CN not-matching server name). |
This functionality is currently not available when the provider is OpenSSL.
The value of this setting is a newline (CrLf) separated list of certificates. For instance:
-----BEGIN CERTIFICATE----- MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw ... eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w F0I1XhM+pKj7FjDr+XNj -----END CERTIFICATE----- \r \n -----BEGIN CERTIFICATE----- MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp .. d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA -----END CERTIFICATE-----
When specified the class will verify that the server certificate signature algorithm is among the values specified in this setting. If the server certificate signature algorithm is unsupported the class fails with an error.
The format of this value is a comma separated list of hash-signature combinations. For instance:
component.SSLProvider = TCPClientSSLProviders.sslpInternal;
component.Config("SSLEnabledProtocols=3072"); //TLS 1.2
component.Config("TLS12SignatureAlgorithms=sha256-rsa,sha256-dsa,sha1-rsa,sha1-dsa");
The default value for this setting is sha512-ecdsa,sha512-rsa,sha512-dsa,sha384-ecdsa,sha384-rsa,sha384-dsa,sha256-ecdsa,sha256-rsa,sha256-dsa,sha224-ecdsa,sha224-rsa,sha224-dsa,sha1-ecdsa,sha1-rsa,sha1-dsa.
In order to not restrict the server's certificate signature algorithm, specify an empty string as the value for this setting, which will cause the signature_algorithms TLS 1.2 extension to not be sent.
The default value is ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1.
When using TLS 1.2 and SSLProvider is set to Internal, the values refer to the supported groups for ECC. The following values are supported:
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1" (default)
The default value is set to balance common supported groups and the computational resources required to generate key shares. As a result only some groups are included by default in this setting.
Note: All supported groups can always be used during the handshake even if not listed here, but if a group is used which is not present in this list it will incur an additional round trip and time to generate the key share for that group.
In most cases this setting does not need to be modified. This should only be modified if there is a specific reason to do so.
The default value is ecdhe_x25519,ecdhe_secp256r1,ecdhe_secp384r1,ffdhe_2048,ffdhe_3072
The values are ordered from most preferred to least preferred. The following values are supported:
- "ecdhe_x25519" (default)
- "ecdhe_x448"
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1"
- "ffdhe_2048" (default)
- "ffdhe_3072" (default)
- "ffdhe_4096"
- "ffdhe_6144"
- "ffdhe_8192"
- "ed25519" (default)
- "ed448" (default)
- "ecdsa_secp256r1_sha256" (default)
- "ecdsa_secp384r1_sha384" (default)
- "ecdsa_secp521r1_sha512" (default)
- "rsa_pkcs1_sha256" (default)
- "rsa_pkcs1_sha384" (default)
- "rsa_pkcs1_sha512" (default)
- "rsa_pss_sha256" (default)
- "rsa_pss_sha384" (default)
- "rsa_pss_sha512" (default)
The default value is ecdhe_x25519,ecdhe_x448,ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1,ffdhe_2048,ffdhe_3072,ffdhe_4096,ffdhe_6144,ffdhe_8192
The values are ordered from most preferred to least preferred. The following values are supported:
- "ecdhe_x25519" (default)
- "ecdhe_x448" (default)
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1" (default)
- "ffdhe_2048" (default)
- "ffdhe_3072" (default)
- "ffdhe_4096" (default)
- "ffdhe_6144" (default)
- "ffdhe_8192" (default)
Socket Config Settings
Note: This option is not valid for UDP ports.
Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the class is activated the InBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small.
Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the class is activated the OutBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small.
Base Config Settings
The following is a list of valid code page identifiers:
Identifier | Name |
037 | IBM EBCDIC - U.S./Canada |
437 | OEM - United States |
500 | IBM EBCDIC - International |
708 | Arabic - ASMO 708 |
709 | Arabic - ASMO 449+, BCON V4 |
710 | Arabic - Transparent Arabic |
720 | Arabic - Transparent ASMO |
737 | OEM - Greek (formerly 437G) |
775 | OEM - Baltic |
850 | OEM - Multilingual Latin I |
852 | OEM - Latin II |
855 | OEM - Cyrillic (primarily Russian) |
857 | OEM - Turkish |
858 | OEM - Multilingual Latin I + Euro symbol |
860 | OEM - Portuguese |
861 | OEM - Icelandic |
862 | OEM - Hebrew |
863 | OEM - Canadian-French |
864 | OEM - Arabic |
865 | OEM - Nordic |
866 | OEM - Russian |
869 | OEM - Modern Greek |
870 | IBM EBCDIC - Multilingual/ROECE (Latin-2) |
874 | ANSI/OEM - Thai (same as 28605, ISO 8859-15) |
875 | IBM EBCDIC - Modern Greek |
932 | ANSI/OEM - Japanese, Shift-JIS |
936 | ANSI/OEM - Simplified Chinese (PRC, Singapore) |
949 | ANSI/OEM - Korean (Unified Hangul Code) |
950 | ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC) |
1026 | IBM EBCDIC - Turkish (Latin-5) |
1047 | IBM EBCDIC - Latin 1/Open System |
1140 | IBM EBCDIC - U.S./Canada (037 + Euro symbol) |
1141 | IBM EBCDIC - Germany (20273 + Euro symbol) |
1142 | IBM EBCDIC - Denmark/Norway (20277 + Euro symbol) |
1143 | IBM EBCDIC - Finland/Sweden (20278 + Euro symbol) |
1144 | IBM EBCDIC - Italy (20280 + Euro symbol) |
1145 | IBM EBCDIC - Latin America/Spain (20284 + Euro symbol) |
1146 | IBM EBCDIC - United Kingdom (20285 + Euro symbol) |
1147 | IBM EBCDIC - France (20297 + Euro symbol) |
1148 | IBM EBCDIC - International (500 + Euro symbol) |
1149 | IBM EBCDIC - Icelandic (20871 + Euro symbol) |
1200 | Unicode UCS-2 Little-Endian (BMP of ISO 10646) |
1201 | Unicode UCS-2 Big-Endian |
1250 | ANSI - Central European |
1251 | ANSI - Cyrillic |
1252 | ANSI - Latin I |
1253 | ANSI - Greek |
1254 | ANSI - Turkish |
1255 | ANSI - Hebrew |
1256 | ANSI - Arabic |
1257 | ANSI - Baltic |
1258 | ANSI/OEM - Vietnamese |
1361 | Korean (Johab) |
10000 | MAC - Roman |
10001 | MAC - Japanese |
10002 | MAC - Traditional Chinese (Big5) |
10003 | MAC - Korean |
10004 | MAC - Arabic |
10005 | MAC - Hebrew |
10006 | MAC - Greek I |
10007 | MAC - Cyrillic |
10008 | MAC - Simplified Chinese (GB 2312) |
10010 | MAC - Romania |
10017 | MAC - Ukraine |
10021 | MAC - Thai |
10029 | MAC - Latin II |
10079 | MAC - Icelandic |
10081 | MAC - Turkish |
10082 | MAC - Croatia |
12000 | Unicode UCS-4 Little-Endian |
12001 | Unicode UCS-4 Big-Endian |
20000 | CNS - Taiwan |
20001 | TCA - Taiwan |
20002 | Eten - Taiwan |
20003 | IBM5550 - Taiwan |
20004 | TeleText - Taiwan |
20005 | Wang - Taiwan |
20105 | IA5 IRV International Alphabet No. 5 (7-bit) |
20106 | IA5 German (7-bit) |
20107 | IA5 Swedish (7-bit) |
20108 | IA5 Norwegian (7-bit) |
20127 | US-ASCII (7-bit) |
20261 | T.61 |
20269 | ISO 6937 Non-Spacing Accent |
20273 | IBM EBCDIC - Germany |
20277 | IBM EBCDIC - Denmark/Norway |
20278 | IBM EBCDIC - Finland/Sweden |
20280 | IBM EBCDIC - Italy |
20284 | IBM EBCDIC - Latin America/Spain |
20285 | IBM EBCDIC - United Kingdom |
20290 | IBM EBCDIC - Japanese Katakana Extended |
20297 | IBM EBCDIC - France |
20420 | IBM EBCDIC - Arabic |
20423 | IBM EBCDIC - Greek |
20424 | IBM EBCDIC - Hebrew |
20833 | IBM EBCDIC - Korean Extended |
20838 | IBM EBCDIC - Thai |
20866 | Russian - KOI8-R |
20871 | IBM EBCDIC - Icelandic |
20880 | IBM EBCDIC - Cyrillic (Russian) |
20905 | IBM EBCDIC - Turkish |
20924 | IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol) |
20932 | JIS X 0208-1990 & 0121-1990 |
20936 | Simplified Chinese (GB2312) |
21025 | IBM EBCDIC - Cyrillic (Serbian, Bulgarian) |
21027 | Extended Alpha Lowercase |
21866 | Ukrainian (KOI8-U) |
28591 | ISO 8859-1 Latin I |
28592 | ISO 8859-2 Central Europe |
28593 | ISO 8859-3 Latin 3 |
28594 | ISO 8859-4 Baltic |
28595 | ISO 8859-5 Cyrillic |
28596 | ISO 8859-6 Arabic |
28597 | ISO 8859-7 Greek |
28598 | ISO 8859-8 Hebrew |
28599 | ISO 8859-9 Latin 5 |
28605 | ISO 8859-15 Latin 9 |
29001 | Europa 3 |
38598 | ISO 8859-8 Hebrew |
50220 | ISO 2022 Japanese with no halfwidth Katakana |
50221 | ISO 2022 Japanese with halfwidth Katakana |
50222 | ISO 2022 Japanese JIS X 0201-1989 |
50225 | ISO 2022 Korean |
50227 | ISO 2022 Simplified Chinese |
50229 | ISO 2022 Traditional Chinese |
50930 | Japanese (Katakana) Extended |
50931 | US/Canada and Japanese |
50933 | Korean Extended and Korean |
50935 | Simplified Chinese Extended and Simplified Chinese |
50936 | Simplified Chinese |
50937 | US/Canada and Traditional Chinese |
50939 | Japanese (Latin) Extended and Japanese |
51932 | EUC - Japanese |
51936 | EUC - Simplified Chinese |
51949 | EUC - Korean |
51950 | EUC - Traditional Chinese |
52936 | HZ-GB2312 Simplified Chinese |
54936 | Windows XP: GB18030 Simplified Chinese (4 Byte) |
57002 | ISCII Devanagari |
57003 | ISCII Bengali |
57004 | ISCII Tamil |
57005 | ISCII Telugu |
57006 | ISCII Assamese |
57007 | ISCII Oriya |
57008 | ISCII Kannada |
57009 | ISCII Malayalam |
57010 | ISCII Gujarati |
57011 | ISCII Punjabi |
65000 | Unicode UTF-7 |
65001 | Unicode UTF-8 |
Identifier | Name |
1 | ASCII |
2 | NEXTSTEP |
3 | JapaneseEUC |
4 | UTF8 |
5 | ISOLatin1 |
6 | Symbol |
7 | NonLossyASCII |
8 | ShiftJIS |
9 | ISOLatin2 |
10 | Unicode |
11 | WindowsCP1251 |
12 | WindowsCP1252 |
13 | WindowsCP1253 |
14 | WindowsCP1254 |
15 | WindowsCP1250 |
21 | ISO2022JP |
30 | MacOSRoman |
10 | UTF16String |
0x90000100 | UTF16BigEndian |
0x94000100 | UTF16LittleEndian |
0x8c000100 | UTF32String |
0x98000100 | UTF32BigEndian |
0x9c000100 | UTF32LittleEndian |
65536 | Proprietary |
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.
This setting only works on these classes: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
Setting this configuration setting to true tells the class to use the internal implementation instead of using the system security libraries.
On Windows, this setting is set to false by default. On Linux/macOS, this setting is set to true by default.
To use the system security libraries for Linux, OpenSSL support must be enabled. For more information on how to enable OpenSSL, please refer to the OpenSSL Notes section.
Trappable Errors (PTechCanadianDebit Class)
PTechCanadianDebit Errors
432 Invalid Index | |
501 Property length is invalid | |
504 Luhn digit check failed. | |
505 Card date invalid. | |
506 Card expired. | |
511 Property is set with invalid data. | |
517 Response length mismatch. | |
518 LRC check failed. | |
519 Corrupt response. | |
545 Error found in token data | |
546 Missing property for current method call. | |
593 Verification of post data failed: Invalid mix of properties for the current method call. |
The following is a list of error codes which may be returned by the Paymentech Server. In the case of a server-side error condition, the ResponseCode property will contain "E", the error code will be contained in the ResponseApprovalCode property, and the description in ResponseText
Paymentech Issuer Errors
ResponseApprovalCode | ResponseText | Description |
200 | Auth Declined | Cardholder's bank did not approve transaction. |
201 | Call Voice Oper | Authorizer needs more information for approval. |
202 | Hold - Call | Card issuer does not want that card used. Call for further instructions. |
203 | Call Voice Oper | Authorizer didn't respond within allotted time. |
204 | Invalid Card No | Account #/mag stripe is invalid. |
205 | Invalid Exp. Date | Expiration date is either incorrect format or prior to today. |
206 | Invalid ICA No | Invalid International Control Account number. |
207 | Invalid ABA No | Invalid American Banking Association number. |
208 | Invalid PIN No | The Personal ID Number for a debit transaction is incorrect. |
209 | Invalid Bank MID | The Bank Merchant ID is incorrect. |
210 | Invalid Term No | The merchant ID is not valid or active. |
211 | Invalid Amount | Amount is either: equal to 0, has no decimal, has decimal in wrong place, or has multiple decimals. |
213 | Invalid Tran Fmt | The transaction format isn't valid, typically invalid SIC code |
214 | Call Voice Oper | Authorization center cannot be reached. |
215 | Lost/Stolen Card | Card has been reported lost or stolen. |
216 | Invalid PIN | Personal ID code is incorrect. |
217 | Over Credit Flr | Amount requested exceeds credit limit. |
218 | Request Denied | Transaction is not valid for this authorizer. |
220 | Not Online to XX | Fatal communications error. |
221 | Auth Down-Retry | Debit authorizer temporarily unavailable. |
222 | Auth Declined | Vehicle not found in positive file. |
223 | Invalid Pin No | Driver # not found in positive file. |
224 | Auth Declined | Card is on private label negative file. |
225 | Card Not Allowed | Merchant does not accept this card. |
226 | PL Setup Reqd | Merchant not set up for Private Label. |
227 | BIN Not Allowed | Merchant cannot accept this Private Label BIN range. |
228 | Card Not Allowed | Merchant cannot accept this card. |
229 | Inv Merc Rstrct Code | Restriction code field contains invalid data. |
230 | Prod Restricted | Merchant attempted a product code not permitted by this merchant. |
231 | Prod Not On File | Merchant attempted a product code that does not exist on host. |
232 | Auth Declined | Invalid card type for Prior Auth sale. |
233 | Auth Declined | Terminal Type not supported. |
234 | Auth Declined | T&E card used for Sale when merchant only allows Auth Only. |
235 | *Request Denied* | Prior Auth selected with no Auth code provided. |
238 | Invalid Driver Number | The Driver Number entered is invalid. |
247 | PIN Not Selected | EBT recipient has not selected a PIN for this card. |
248 | Unmatch Vch Info | Voucher submitted does not match one previously issued. |
248 | CVC2/CID ERROR | CVC2 or CID entered was not valid for the card number. |
249 | Tran Not Defined | This type of transaction is not allowed for this type of card. |
257 | Block Act Not Alwd | The merchant.is not allowed to process Stored Value Block Activations |
258 | Incorrect Act Amt | The activation amount requested does not match the predenominated amount for the card. |
292 | Auth Down - Retry | Authorizer is not responding. |
293 | Auth Busy - Retry | Authorizer not available at this time. |
294 | Auth Busy - Retry | Authorizer not available at this time. |
297 | Auth Error - Retry | Authorizer not available at this time. |
298 | Err - Pls Retry | Debit authorizer experienced an error. |
299 | Err - Pls Retry | Debit authorizer experienced an error. |
Paymentech Format Errors
ResponseApprovalCode | ResponseText | Description |
300 | Invalid Term ID | The length of the merchant ID is incorrect or contains invalid data. |
301 | Invalid Function | Tran code is incorrect or wrong length. |
302 | Invalid Card | Mag stripe contains invalid data or account # is greater than 19 digits |
303 | Invalid Exp. Date | Card has expired, month was not 01-12 or year was not 00-99. |
304 | Invalid Action Code | Action code is longer than 1 digit. |
305 | Amt Entry Error | Amount less than .01 or greater than 99999.99 or contained non- numeric data. |
306 | Invalid PIN | Incorrect PIN block length. |
307 | Invalid Card | Invalid card type or account number. |
308 | Auth # Not Entered | Auth code was not entered on a Prior Auth, Incremental or Rev. |
309 | Invalid Down Pay Ind | Insurance down payment indicator is invalid. |
310 | Policy # Wrong Len | Insurance policy number is incorrect length. |
311 | Invalid Ind Code | Industry type must be RE or DM. |
312 | Invalid Function | Tran code is invalid or contains alpha data. |
313 | Entry Mode Invalid | POS Entry mode is less than 01 or greater than 04. |
314 | Invalid Industry Data | The Industry Specific field contains invalid data. |
315 | Inv Fleet Data | The Fleet Card field contains invalid data. |
316 | Invalid Sys Info | The System Information field contains invalid data. |
317 | Invalid Format | Payment Service indicator or Transaction ID is invalid. |
318 | Inv Transaction Class | Transaction class not "F" for financial transaction. |
319 | Inv PIN Capability | Pin capability code field contains invalid data. |
320 | Inv/Missing Retr Ref | Retrieval Reference # is missing or contains alpha data. |
321 | Inv MSDI | Market Specific Data field contains invalid data. |
322 | Invalid Duration | Market specific data field Duration is 00, blank or missing. |
323 | Inv Pref Cust Ind | Preferred Customer indicator contains invalid data. |
324 | Inv MO/TO Number | Mail/Telephone Order number is invalid (InvoiceNumber must have a value). |
325 | Inv Sale/Chg Des/Folio | Hotel Sale Code, Charge Descriptor or Folio contains invalid data. |
326 | Inv Mult Clr Seq No | Multiple Clearing sequence number is invalid. |
327 | Inv Purch Card Data | Purchasing card field contains invalid data. |
328 | Inv Input/Use VRU | Insurance transaction not from VRU. |
329 | Invalid EC Data 329 | Invalid Electronic Commerce Data. |
330 | INV Function or Multiple FS or Unknown TKN | Indicates system problem, notify Paymentech Network Services or Multiple field separators received without required data or A token of unknown definition was received |
331 | INV TKN Value | Invalid token value was received. |
332 | CVD Data Error | Error with the cardholder verification data received; invalid value or not allowable for this card for this transaction. |
333 | TKN Data Error | Indicates system problem, notify Paymentech Network Services. |
359 | Invalid Sequence Number | The SequenceNumber must be a number between 0 and 2400. |
Paymentech Host / Setup Errors
ResponseApprovalCode | ResponseText | Description |
400 | Invalid Term ID | Merchant ID not found in merchant file. |
401 | Invalid Term ID | Merchant ID not found in terminal file. |
402 | Term Not Active | Active flag for merchant set to "N". |
403 | Invalid Act Code | Merchant not set up for cash advance function. |
404 | Void Not Allowed | The transaction requested for voiding is not an EFT transaction. |
405 | Ref Num Not Found | Transaction requested for reversal not found. |
406 | Proc Error 7 | The host can't clear all transaction records for the requested Batch Release. |
407 | Too Many Batches | There are 999 open batches for this merchant. |
408 | Release Batch | Current batch has 999 records. Release batch before continuing. |
409 | Invalid Function | Debit transaction requested but debit flag is set to "N". |
410 | Invalid Term ID | The Terminal ID portion of the merchant ID is incorrect. |
411 | Invalid Term ID | The maximum retries for this merchant have been exceeded. |
412 | Proc Error 13 | Unable to read reference number file. |
413 | Proc Error 14 | 413 |
414 | Proc Error 15 | 414 |
415 | Invalid Function | 415 |
416 | Invalid Function | Merchant is Authorization Only and a debit record was sent. |
417 | Invalid Function | Private label flag is "N" but a private label account number was sent. |
418 | Please Try Again | Incorrect debit working key. |
419 | Invalid Function | Manually entered transactions are not allowed for this terminal ID. |
420 | Amount Too Large | Maximum sale amount exceeded. |
421 | Amount Too Large | Maximum return amount exceeded. |
422 | Invalid Term ID | Host couldn't read terminal file within specified time. |
423 | Proc Error 24 | Host couldn't read reference number file within specified time. |
424 | Invalid Term ID | Transaction open flag has been set to "Y" within prior 3 minutes. |
425 | Invalid Function | Cash management not allowed for this merchant ID. |
426 | Rev Not Allowed | Host found no batch number matching the one sent. |
427 | Rev Not Allowed | Host found no transactions meeting the specifications sent. |
428 | Dscv Not Allowed | Merchant not set up for Discover transactions. |
429 | Rev Not Allowed | The batch containing the transaction to void has been released. |
430 | Dscv Not Allowed | Merchant not set up for Discover. |
431 | DC Not Allowed | Merchant not set up for Diners Club. |
432 | CB Not Allowed | Merchant not set up for Carte Blanche. |
433 | Invalid Key | No AMEX subscriber number, process control ID or product code set up |
434 | Invalid Key | Future use. |
435 | Failed-Plz Call | Debit transaction being sent to an authorizer not set up on host file. |
436 | Failed-Plz Call | Debit security key does not exist on the security management file. |
437 | Failed-Plz Call | Failure occurred during encryption/decryption of PIN. |
438 | Failed-Plz Call | Error occurred while generating a debit working key. |
439 | Failed-Plz Call | The DB (debit) sponsor institution on the merchant file is not set up on sponsor file. |
440 | Failed-Plz Call | The network set up on the sponsoring bank file for this institution is not set up on the host's network file. |
441 | Failed-Plz Call | The host is unable to communicate with decryption device. |
442 | JCB Not Allowed | JCB CD flag on merchant record not set up for JCB transactions. |
443 | JCB Not Allowed | JCB subscriber number not set up for JCB transactions. |
444 | Bank Not On File | Debit BIN not set up for this merchant in routing table. |
445 | No Sponsor Inst | No valid sponsorship was found on Merchant record. |
446 | Failed Plz Call | Future use. |
447 | WX Not Allowed | Merchant not set up to accept WEX. |
448 | Amount Too Large | Amount exceeds maximum limit. |
449 | Reenter Odometer | Odometer was 000000 or contained non-numeric data. |
450 | Duplicate Tran | No ACK reversal was followed by a duplicate request |
451 | Tran Not Allowed | Requested transaction type is not allowed for this card/merchant. |
452 | Bat Already Rels | Batch has already been released. |
453 | Invalid Rtng Ind | Invalid Routing Indicator field. |
454 | AX Not Allowed | AMEX not allowed. |
999 | Invalid Merchant | Merchant number not on file. |
Paymentech Debit / EBT Specific Errors
ResponseApprovalCode | ResponseText | Description |
602 | Call Voice Op | Auth center cannot be reached. |
692 | Auth Down-Retry | Debit authorizer temporarily unavailable. |
693 | Auth Busy-Retry | Queue for debit authorizer too long. |
694 | Auth Busy-Retry | Debit authorizer not responding in time. |
Paymentech Batch Management Errors (use the ErrorCode configuration setting to retrieve this information from the PTechHostSettle class.
ErrorCode | ResponseText | Description |
105 | Invalid Term ID | Merchant ID on a Batch Inquiry or Release is incorrect. |
106 | Term Not Active | Active flag for the merchant ID is set to N. |
107 | No Transactions | A Batch Inquiry or Release was requested but no open batch exists. |
108 | Bat Already Rels | A second batch release was attempted. |
109 | Batch Not Found | Requested batch does not exist. |
The class may also return one of the following error codes, which are inherited from other classes.
HTTP Errors
118 Firewall Error. Error description contains detailed message. | |
143 Busy executing current method. | |
151 HTTP protocol error. The error message has the server response. | |
152 No server specified in URL | |
153 Specified URLScheme is invalid. | |
155 Range operation is not supported by server. | |
156 Invalid cookie index (out of range). | |
301 Interrupted. | |
302 Can't open AttachedFile. |
The class may also return one of the following error codes, which are inherited from other classes.
TCPClient Errors
100 You cannot change the RemotePort at this time. A connection is in progress. | |
101 You cannot change the RemoteHost (Server) at this time. A connection is in progress. | |
102 The RemoteHost address is invalid (0.0.0.0). | |
104 Already connected. If you want to reconnect, close the current connection first. | |
106 You cannot change the LocalPort at this time. A connection is in progress. | |
107 You cannot change the LocalHost at this time. A connection is in progress. | |
112 You cannot change MaxLineLength at this time. A connection is in progress. | |
116 RemotePort cannot be zero. Please specify a valid service port number. | |
117 You cannot change the UseConnection option while the class is active. | |
135 Operation would block. | |
201 Timeout. | |
211 Action impossible in control's present state. | |
212 Action impossible while not connected. | |
213 Action impossible while listening. | |
301 Timeout. | |
302 Could not open file. | |
434 Unable to convert string to selected CodePage. | |
1105 Already connecting. If you want to reconnect, close the current connection first. | |
1117 You need to connect first. | |
1119 You cannot change the LocalHost at this time. A connection is in progress. | |
1120 Connection dropped by remote host. |
SSL Errors
270 Cannot load specified security library. | |
271 Cannot open certificate store. | |
272 Cannot find specified certificate. | |
273 Cannot acquire security credentials. | |
274 Cannot find certificate chain. | |
275 Cannot verify certificate chain. | |
276 Error during handshake. | |
280 Error verifying certificate. | |
281 Could not find client certificate. | |
282 Could not find server certificate. | |
283 Error encrypting data. | |
284 Error decrypting data. |
TCP/IP Errors
10004 [10004] Interrupted system call. | |
10009 [10009] Bad file number. | |
10013 [10013] Access denied. | |
10014 [10014] Bad address. | |
10022 [10022] Invalid argument. | |
10024 [10024] Too many open files. | |
10035 [10035] Operation would block. | |
10036 [10036] Operation now in progress. | |
10037 [10037] Operation already in progress. | |
10038 [10038] Socket operation on non-socket. | |
10039 [10039] Destination address required. | |
10040 [10040] Message too long. | |
10041 [10041] Protocol wrong type for socket. | |
10042 [10042] Bad protocol option. | |
10043 [10043] Protocol not supported. | |
10044 [10044] Socket type not supported. | |
10045 [10045] Operation not supported on socket. | |
10046 [10046] Protocol family not supported. | |
10047 [10047] Address family not supported by protocol family. | |
10048 [10048] Address already in use. | |
10049 [10049] Can't assign requested address. | |
10050 [10050] Network is down. | |
10051 [10051] Network is unreachable. | |
10052 [10052] Net dropped connection or reset. | |
10053 [10053] Software caused connection abort. | |
10054 [10054] Connection reset by peer. | |
10055 [10055] No buffer space available. | |
10056 [10056] Socket is already connected. | |
10057 [10057] Socket is not connected. | |
10058 [10058] Can't send after socket shutdown. | |
10059 [10059] Too many references, can't splice. | |
10060 [10060] Connection timed out. | |
10061 [10061] Connection refused. | |
10062 [10062] Too many levels of symbolic links. | |
10063 [10063] File name too long. | |
10064 [10064] Host is down. | |
10065 [10065] No route to host. | |
10066 [10066] Directory not empty | |
10067 [10067] Too many processes. | |
10068 [10068] Too many users. | |
10069 [10069] Disc Quota Exceeded. | |
10070 [10070] Stale NFS file handle. | |
10071 [10071] Too many levels of remote in path. | |
10091 [10091] Network subsystem is unavailable. | |
10092 [10092] WINSOCK DLL Version out of range. | |
10093 [10093] Winsock not loaded yet. | |
11001 [11001] Host not found. | |
11002 [11002] Non-authoritative 'Host not found' (try again or check DNS setup). | |
11003 [11003] Non-recoverable errors: FORMERR, REFUSED, NOTIMP. | |
11004 [11004] Valid name, no data record (check DNS setup). |