Logo | |
Info | Snap: EVO Payments |
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 Snap
Besides the general parameters described below for the credit card connection, Snap requires the following additional parameters. An authorisation with 3-D Secure is possible.
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..30 | 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, ...). |
CustomerID | ans..64 | O | CustomerID given by the merchant with the transaction request |
OrderDesc | ans..768 | M | Description of purchased goods, unit prices etc. |
CreditCardHolder | ans..60 | O | Name of card holder (for AVS US domestic optional) |
Contact data/Address verification (AVS) | |||
sdFirstName | ans..25 | O | First name in the delivery address |
sdLastName | ans..25 | O | Last name in the delivery address |
sdMiddleName | ans..30 | O | Middle name in the delivery address |
sdTitle | ans..10 | O | Title in the delivery address, e.g. Dr. or Prof. |
sdSuffix | ans..15 | O | Suffix to the name |
sdStreet | ans..35 | O | Street name in the delivery address |
sdHouseNumber | ans..8 | O | Street number in the delivery address |
sdStreet2 | ans..35 | O | Address addition in the delivery address |
sdPOBox | ans..35 | O | Post office box in the delivery address |
sdZIPCode | ans..20 | O | Postcode in the delivery address |
sdCity | ans..35 | O | Town/city in the delivery address |
sdState | ans..10 | O | State/country in the delivery address |
sdCountryCode | a2/a3 | O | Country code of the delivery address according to ISO-3166-1, alphanumeric 2-digits or 3-digits (preferred) |
bdFirstName | ans..30 | O | First name in the invoicing address |
bdLastName | ans..30 | O | Last name in the invoicing address |
bdMiddleName | ans..30 | O | Middle name in the invoicing address |
bdSuffix | ans..15 | O | Suffix to the name in the invoicing address |
bdCompany | ans..100 | O | Company name in the invoicing address |
bdStreet | ans..35 | O | Street name in the invoicing address |
bdHouseNumber | ans..15 | O | Street number in the invoicing address |
bdStreet2 | ans..35 | O | Address addition in the billing address |
bdPOBox | ans..35 | O | Post office box in the invoicing address |
bdZIPCode | ans..20 | O | Postcode in the invoicing address |
bdCity | ans..35 | O | Town/city in the invoicing address |
bdState | ans..30 | O | State/country in the invoicing address |
bdCountryCode | a3 | O | Country code of invoicing address according to ISO-3166-1, alphanumeric 3 chars |
EmployeeID | ans..25 | OC | ID of the employee/cashier. Required for the branches retail, restaurant and for MOTO. |
ShipDate | an8 | OC | Shipment date in the format "YYYYMMDD": mandatory for MOTO |
AddrStreet | ans..100 | OC | Street name: it must be distinguished between AVS-US-Domestic and AVS-International. (for AVS) US-Domestic: Street and street number together; optional International: Street name (without street number); mandatory for AVS |
AddrStreetNr | ans..15 | OC | Street number of the customer: mandatory for AVS International |
AddrPOBox | ans..35 | O | Post office box (for AVS International) |
AddrZip | ans..10 | OC | Postcode, mandatory for AVS (US domestic as well as International) |
AddrCity | ans..50 | OC | Town/city, mandatory for AVS International |
AddrState | a2 | O | Code of the customer’s Federal State (for AVS) |
AddrCountryCode | a2/a3 | M | Country code according to ISO-3166-1, alphanumeric 2 or 3 chars (preferred) (for AVS) |
ans..128 | O | Email address of the customer (for AVS US domestic) | |
Phone | ans..20 | O | Telephone number of the customer (for AVS US domestic) |
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..30 | 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, ...). |
ErrorText | ans..128 | O | Error text from Snap, if agreed with Computop Helpdesk. Is returned only if ResponseExtended=Yes is configured for that merchant. |
CodeExt | n..10 | O | Error code from Snap, if agreed with Computop Helpdesk. Is returned only if ResponseExtended=Yes is configured for that merchant. |
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.