Response Codes
During the payment process there are many response codes which either follow a common ISO standard, or are standards set by the card scheme or issuer. This page will explain what each of these codes is used for and possible examples.
Submission Component Specific Codes
Please select the submission component (inbound interface) relevant to you to see the list of specific response codes:
nexo Acquirer Protocol Response Codes
General Gateway Response Codes
Authorization Platform (Host) Specific Codes
Please select the front end processor relevant to you to see the list of specific response codes:
Base24 Argentina Response Codes
Issuer Authorisation Response
When an authorisation is performed, the issuer will respond with a code which gives some context as to whether it was successful or not, and if not then why is was declined.
See the following table for a list of example response codes and the usage:
Code | Description |
---|---|
00 | Approved or completed successfully |
01 | Refer to card issuer |
02 | Refer to card issuer's special conditions |
03 | Invalid merchant |
04 | Pick-up card |
05 | Do not honor |
06 | Error |
07 | Pick-up card, special condition |
08 | Honour with identification |
09 | Request in progress |
10 | Approved for partial amount |
11 | Approved (VIP) |
12 | Invalid transaction |
13 | Invalid amount |
14 | Invalid card number (no such number) |
15 | No such issuer |
16 | Approved, update track 3 |
17 | Customer cancellation |
18 | Customer dispute |
19 | Re-enter transaction |
20 | Invalid response |
21 | No action taken |
22 | Suspected malfunction |
23 | Unacceptable transaction fee |
24 | File update not supported by receiver |
25 | Unable to locate record on file |
26 | Duplicate file update record, old record replaced |
27 | File update field edit error |
28 | File update file locked out |
29 | File update not successful, contact acquirer |
30 | Format error |
31 | Bank not supported by switch |
32 | Completed partially |
33 | Expired card - pick up |
34 | Suspected fraud - pic up |
35 | Card acceptor contact acquirer - pick up |
36 | Restricted card - pick up |
37 | Card acceptor call acquirer security - pick up |
38 | Allowable PIN tries exceeded |
39 | No credit account |
40 | Requested function not supported |
41 | Lost card - pick up |
42 | No universal account |
43 | Stolen card - pick-up |
44 | No investment account |
45-50 | Reserved for ISO use |
51 | Insufficient funds |
52 | No checking account |
53 | No savings account |
54 | Expired card |
55 | Incorrect personal identification number |
56 | No card record |
57 | Transaction not permitted to cardholder |
58 | Transaction not permitted to terminal |
59 | Suspected fraud |
60 | Card acceptor contact acquirer |
61 | Exceeds withdrawal amount limit |
62 | Restricted card |
63 | Security violation |
64 | Original amount incorrect |
65 | Exceeds withdrawal frequency limit |
66 | Card acceptor call acquirer's security department |
67 | Hard capture (requires that card be picked up at ATM) |
68 | Response received too late |
69-74 | Reserved for ISO use |
75 | Allowable number of PIN tries exceeded |
76-89 | Reserved for private use |
90 | Cutoff is in process (switch ending a day's business and starting the next. Transaction can be sent again in a few minutes) |
91 | Issuer or switch is inoperative |
92 | Financial institution or intermediate network facility cannot be found for routing |
93 | Transaction cannot be completed. Violation of law |
94 | Duplicate transmission |
95 | Reconcile error |
96 | System malfunction |
97-99 | Reserved for national use |
Zero A-9Z | Reserved for ISO use |
A Zero-MZ | Reserved for national use |
N Zero-ZZ | Reserved for private use |
Address Verification Service (AVS)
Address verification service (commonly referred to as AVS) is a method of fraud prevention for card payments made via non-face-to-face channels like ecommerce. The service aims to ensure that the address provided matches the cardholder's address.
AVS is used primarily in the US, Canada and the UK with limited support elsewhere.
A number of response codes can be returned which depend on the card schemes used. See the detail below:
Code | Description | Applicable Schemes |
---|---|---|
A | Street address matches, ZIP does not | Visa, Mastercard, AMEX |
B | Street address matches. Postal code not verified due to incompatible formats | Visa |
C | Street address and postal code not verified due to incompatible formats | Visa |
D | Street address and postal code both match (international-only) | Visa |
E | Information invalid or not allowed for this card type | Visa |
F | Street address and postal code both match (UK-only) | Visa |
G | Not verified for international transaction, or issuer does not support verification | Visa |
I | Not verified | Visa |
M | Street address and postal code both match (international-only) | Visa |
N | Neither street address or postal code matches | Visa, Mastercard, AMEX |
O | Card member name and street address match | AMEX |
P | Postal Code matches, street address unverifiable due to incompatible formats (international-only) | Visa |
R | Retry due to system not being available | Visa, Mastercard, AMEX |
S | Not supported. If present, replaced with U (for domestic) or G (for international) | Visa, Mastercard, AMEX |
U | Address information is unavailable | Visa, Mastercard, AMEX |
W | 9-Digit ZIP matches, street address does not | Visa, Mastercard, AMEX |
Y | 9-Digit ZIP ands treet address both match | Visa, Mastercard, AMEX |
X | 5-Digit ZIP and street address both match | Visa, Mastercard, AMEX |
Z | 5-Digit ZIP matches, street address does not | Visa, Mastercard, AMEX |
0 | All the address information matched | Maestro |
1 | None of the address information matched | Maestro |
2 | Partial information match | Maestro |
3 | No information provided | Maestro |
Results of address verification in REST API
Tag | Value |
---|---|
postalCodeMatch | Y - Matched N- Not matched NO_INPUT_DATA - Postal code wasn't sent in request NOT_CHECKED - Postal code wasn't checked |
streetMatch | Y - Matched N - Not matched NO_INPUT_DATA - Street wasn't sent in request NOT_CHECKED - Street wasn't checked |
associationAvsResponse | see above table - colum 'code' |
Updated 9 months ago