Logo | |
Info | Omnipay: EMS payment solutions, Global Payments, Paysquare, Payvision |
Type |
Introduction
For more information about acquirers and connection, integration with Computop Paygate and Implementation of 3-D Secure (2.x), see chapter Card processing - common introduction.
Specific parameters for Omnipay: EMS payment solutions, Global Payments, Paysquare, Payvision
Besides the general parameters described above for the credit card connection, Omnipay (Bancontact) requires the following additional parameters. An authorisation with 3-D Secure is possible.
Computop Paygate is the preferred PSP with EMS payment solutions. Paygate has now been opened for the transfer of “3D” parameters. For this the respective merchant first needs to configure to “External MPI” on Computop. Paygate then accepts the parameters and uses them in communication with downstream systems.
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.
The following table describes the additional encrypted payment request parameters described below for "interface via form" and "interface via Server-to-Server" :
Key | Format | CND | Description | |
RefNr | ns..15 | O | Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data. Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...). | |
OrderDesc | ans..768 | O | Description of purchased goods, unit prices etc. | |
RTF | a1 | O | for repeat payments (subscriptions): I = Initial payment of a new subscription R = Routine payment (Recurring) | |
ChDesc | an..30 | O | Text printed on the customer’s credit card bill alongside the payee | |
AccVerify | a3 | O | If AccVerify=Yes the card will be checked at the acquirer according to the acquirer’s interface description. The merchant has to submit only this parameter, the parameter "Amount" is optional. If "Amount" is used we replace the amount according to acquirer’s interface description. At payment always Amount=0 is stored. Allowed value: yes | |
FirstName | as..25 | OC | In combination with LastName: First name of the customer for OCT (CFT) transactions | |
LastName | as..25 | OC | In combination with FirstName: Last name of the customer for OCT (CFT) transactions | |
Cryptocurrency | a..3 | C | Used to flag a cryptocurrency purchase. Possible value "Yes". Notice: Possible only for credit card brands VISA, MasterCard, Maestro. | |
Key | Format | CND | Contact data/Address verification (AVS) | |
AddrStreet | a..50 | O | Street name (for AVS) | |
AddrStreetNr | ans..15 | O | Street number for verification by American Express (for AVS) | |
AddrZip | n..10 | O | Postcode (for AVS) | |
AddrCity | a..40 | O | Town/city (for AVS) | |
AddrState | a2 | O | Code of the customer’s Federal State (for AVS) | |
AddrStreet2 | a..32 | O | Second street name (for AVS) | |
AddrStreetNr2 | ans..5 | O | Second street number (for AVS) | |
AddrZip2 | n..5 | O | Second postcode (for AVS) | |
AddrCity2 | a..32 | O | Second town/city (for AVS) | |
AddrChoice | n1 | O | If you transmit 2 street numbers and postcodes, the AddrChoice parameter will determine which address is checked. AddrChoice=1 checks the first address, AddrChoice=2 the second address. (for AVS) | |
Key | Format | CND | Parameters for extension External MPI via EMS (only configured on request) | |
Authresult | a1 | M | Status from VERes or rather PARes Y = Fully Authenticated A = Attempt N = Not enrolled | |
CAVV | ans..32 | C | BASE64 coded Cardholder Authentication Verification Value Permitted special characters are + / = | |
ACSIDHEX | hex40 | C | VISA transactions with Authresult Y / A Bancontact transactions with Authresult Y CAUTION! Bancontact transactions are accepted only with Authresult Y! | |
XID3DHEX | hex40 | C | Hexadecimal XID VISA transactions with Authresult Y / A | |
ECI3D | n2 | M | 01 = Attempt MasterCard / Maestro 02 = Fully Authenticated MasterCard / Maestro / Bancontact 05 = Fully Authenticated VISA 06 = Attempt VISA | |
Key | Format | CND | Additional PayFac parameters for acquirer Payvision | |
SubMID | ans..15 | O | SubMerchantID assigned from the Payment Facilitator and provided in the request to identify its sub-merchants during transaction flow | |
SubMIDName | ans..22 | O | Name of the SubMerchantID | |
SubMIDAddrStreet | ans..38 | O | Street of the SubMerchantID | |
SubMIDAddrCity | ans..13 | O | Town/city of the SubMerchantID | |
SubMIDAddrZip | ans..10 | O | Postcode of the SubMerchantID | |
SubMIDAddrState | ans3 | O | Federal State of the SubMerchantID | |
SubMIDAddrCountryCode | a2 | O | Country code of the SubMerchantID according to ISO-3166-1, alphanumeric 2 chars | |
Additional parameters for credit card payments
The following table describes the result parameters with which the Computop Paygate responds to your system.
these result parameters are additional to the standard parameters for "interface via form" and "interface via Server-to-Server" described below
pls. be prepared to receive additional parameters at any time and do not check the order of parameters
the key (e.g. MerchantId, RefNr) should not be checked case-sentive
Key | Format | CND | Description |
RefNr | ns..15 | O | Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data. Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...). |
Match | a1 | O | Total result of an address check (Global Payments): For possible values see A3 AVS match parameters |
IBAN | ans..34 | MC | IBAN of account holder: Mandatory for card brand Bancontact via Omnipay, otherwise not used |
BIC | ans..11 | MC | BIC of account holder: Mandatory for card brand Bancontact via Omnipay, otherwise not used |
AppCodeTel | n6 | C | for 3-D Secure: Telephone authorisation code |
CAVV | ans..40 | C | for 3-D Secure Authentication Hosting: ACSVerificationID/ ACSVerificationIDHex |
ACSXID | ans..28 | C | for 3-D Secure Authentication Hosting: HexXID |
Additional response parameters for credit card payments
Card processing - Credit Card Form
For more information about credit card processing via forms, please see chapter Credit Card Form (paySSL).
Card processing - Server-2-Server integration
For more information about credit card processing via server-to-server communication, please see chapter Server-2-Server Integration.
Capture / Credit / Reversal
For more information about capture, credit, reversal and credit card payment via POS terminals, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.
PayNow
For more information about PayNow, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.
Batch processing via the interface
For more information about batch processing, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.