Please contact Axepta helpdesk to activate this feature on your MID.
Scope
This feature is only available for cardholder from UK, USA and Canada.
Visa and Mastercards
Request
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 |
|---|---|---|---|
TransID | an..12 | M | TransactionID which should be unique for each payment |
RefNr | an..12 | 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 BNP settlement file (CTSF) we cannot add the additional payment data. |
AddrStreet | ans..30 | O | Street name of the customer (for AVS) |
AddrStreetNr | ans..30 | O | Street number of the customer (for AVS) |
AddrZip | ans..10 | O | Postcode of the customer (for AVS) |
AddrCity | ans..20 | O | Town/city of the customer (for AVS) |
AddrCountryCode | n3 | O | Customer's country code according to ISO-3166-1 numeric (3-digits) (for AVS) |
Response
Address Verification can be performed on a number of card schemes, subject to Issuer and Acquirer support. The result is returned as a code within the parameter Match. Following tables explain the meaning of the result values from different Acquirers.
Following AVS parameters are returned for via CB2A:
Code for „Match“ | Description |
|---|---|
| A | Postcode and address fully match |
| B | Postcode and address partially match |
| C | Postcode and address do not match |
| D | Control was not performed or was not performed for all data elements |
American Express
Request
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 |
|---|---|---|---|
FirstName | ans..15 | O | First name of the customer (for AVS) |
LastName | ans..30 | O | Last name of the customer (for AVS) |
AddrStreet | ans..20 | O | Street name and street number, e.g. 18850~N~56~ST~#301 (for AVS) |
AddrZip | n..9 | O | Postcode (for AVS) |
ans..60 | O | Email address of the customer (for AVS) | |
Phone | n..10 | O | Phone number of the customer: for countries which do not use this system, please send the last 10 digits (for AVS) |
sdFirstName | ans..15 | O | First name in the delivery address (for AVS) |
sdLastName | ans..30 | O | Last name in the delivery address (for AVS) |
sdStreet | ans..50 | O | Street name and street number in th delivery address, e.g. 4102~N~289~ST~#301 (for AVS) |
sdZip | n..9 | O | Postcode in the delivery address |
sdCountryCode | n3 | O | Country code of the delivery address according to ISO-3166-1 numeric (3-digits) (for AVS) |
sdPhone | ans..10 | O | Phone number in the delivery address: for countries which do not use this system, please send the last 10 digits (for AVS) |
Response
Address Verification can be performed on a number of card schemes, subject to Issuer and Acquirer support. The result is returned as a code within the parameter Match. Following tables explain the meaning of the result values from different Acquirers.
Following AVS parameters are returned for American Express via CAPN:
Code for „Match“ | Description |
|---|---|
Y | Address and ZIP matches |
N | Address and ZIP both did not match |
A | only address matches |
Z | only ZIP matches |
U | Information not available |
S | SE not allowed for AAV function |
R | Retry, system unavailable |
L | Name and ZIP match |
M | Name, address and ZIP match |
O | Name and address match |
K | Name match |
D | Name does not match and ZIP matches |
E | Name does not match, address and ZIP match |
F | Name does not match, address matches |
W | Name, address and ZIP does not match |