The eCommerce Response code indicates the status of a transaction as it is sent to the financial institution and returned to the client. The Response Code "00" (Transaction Normal) indicates that the transaction was processed normally. Any response other than "00" indicates that it was not normal.
Properties:
- Exact_Resp_code char(2)
- Exact_Message char(50)
In all cases the Exact_Resp_code is accompanied by a brief Exact_Message, which gives a description of the code.
In the case of a non "00" Exact_Resp_code, the developer has an option as to how that transaction is presented to the customer and what further steps should be taken to ensure proper transaction flow.
The table below gives some guidelines as to what each response code means and what actions should be taken when it is returned. In all cases, a fully populated Customer Transaction Record (CTR) is returned and should be displayed to the cardholder in accordance with bank requirements.
|
This response code indicates that the transaction was processed normally. Please refer to the bank and approval response information for bank approval Status. |
|
|
00 |
Transaction Normal |
|
The following response codes indicate invalid data in the transaction. In these cases, the data should be changed before attempting to resend the transaction. These response codes are generated by the remote Plug-In. They will not appear on the First Data Payeezy Gateway website. |
|
|
07 |
Terminal Restriction: Try again later |
|
22 |
Invalid Credit Card Number |
|
25 |
Invalid Expiry Date |
|
26 |
Invalid Amount |
|
27 |
Invalid Card Holder |
|
28 |
Invalid Authorization No |
|
31 |
Invalid Verification String |
|
32 |
Invalid Transaction Code |
|
57 |
Invalid Reference No |
|
58 |
Invalid AVS String, The length of the AVS String has exceeded the max. 40 characters |
|
60 |
Invalid Customer Reference Number |
|
63 |
Invalid Duplicate |
|
64 |
Invalid Refund |
|
68 |
Restricted Card Number |
|
69 |
Invalid Transaction Tag |
|
72 |
Data within the transaction is incorrect |
|
88 |
Invalid Correlation ID |
|
89 |
Invalid Transarmor Token |
|
93 |
Invalid authorization number entered on a pre-auth completion. The ETG response of "93 - Violation, Cannot Complete" can be returned if you tried to send a Pre-Authorization Completion transaction and one of the required conditions were not met. In order to complete a pre-authorized transaction successfully, please make sure the following conditions are met: · The Pre-Authorization Completion transaction is sent using the same GatewayID as the one used for the original Pre-Authorization transaction. · The amount in the Pre-Authorization Completion is less or equal to twice the pre-authorized amount. · The Pre-Authorization Completion transaction is sent no later than 15 days after the date of the initial Pre-Authorization transaction. |
|
95 |
Invalid Currency Requested · This error is received when a transaction is sent in a different currency than what is on the merchant processing account. |
|
The following response codes indicate a problem with the merchant configuration at the financial institution. Please contact First Data for further investigation. |
|
|
11 |
Invalid Sequence No |
|
12 |
Message Timed-out at Host |
|
21 |
BCE Function Error |
|
23 |
Invalid Response from First Data |
|
30 |
Invalid Date From Host |
|
The following response codes indicate a problem with the Payeezy Gateway host or an error in the merchant configuration. Please contact First Data for further investigation. |
|
|
10 |
Invalid Transaction Description |
|
14 |
Invalid Gateway ID |
|
15 |
Invalid Transaction Number |
|
16 |
Connection Inactive |
|
17 |
Unmatched Transaction |
|
18 |
Invalid Reversal Response |
|
19 |
Unable to Send Socket Transaction |
|
20 |
Unable to Write Transaction to File |
|
24 |
Unable to Void Transaction |
|
37 |
Payment Type Not Supported By Merchant |
|
40 |
Unable to Connect |
|
41 |
Unable to Send Logon |
|
42 |
Unable to Send Trans |
|
43 |
Invalid Logon |
|
52 |
Terminal not Activated |
|
53 |
Terminal/Gateway Mismatch |
|
54 |
Invalid Processing Center |
|
55 |
No Processors Available |
|
56 |
Database Unavailable |
|
61 |
Socket Error |
|
62 |
Host not Ready |
|
The following response codes indicate the final state of a transaction. In the event of one of these codes being returned, please contact First Data for further investigation. |
|
|
08 |
CVV2/CID/CVC2 Data not verified |
|
44 |
Address not Verified |
|
70 |
Transaction Placed in Queue |
|
73 |
Transaction Received from Bank |
|
76 |
Reversal Pending |
|
77 |
Reversal Complete |
|
79 |
Reversal Sent to Bank |
|
The following response codes indicate the final state of a transaction due to custom Fraud Filters created by the Merchant. |
|
|
F1 |
Address check failed - Fraud suspected |
|
F2 |
Card/Check Number check failed - Fraud suspected |
|
F3 |
Country Check Failed - Fraud Suspected |
|
F4 |
Customer Reference Check Failed - Fraud Suspected |
|
F5 |
Email Address check failed - Fraud suspected |
|
F6 |
IP Address check failed - Fraud suspected |
|
The following response codes indicate that a certain threshold is exceeded within the Velocity Controls restrictions: |
|
|
33 |
Merchant Volume Exceeded |
|
34 |
Card Volume Exceeded |
|
35 |
Maximum Sale Exceeded |
|
36 |
Below Minimum Sale |
|
38 |
IP Volume Exceeded |