Overview
This section lists error responses returned during the payment process.
Status and Error Indicators
Errors occurring during the payment process are reported in response parameters, which provide information about the error. Each of the three stages of the payment process use different response parameters to return error responses:
-
Stage 1: The API itself.
Status/error parameters:status
,errCode
,reason
. -
Stage 2: The payment gateway and banks in the event of a credit card transaction.
Status/error parameters:transactionStatus
,gwErrorCode
,gwErrorReason
,gwExtendedErrorCode
. -
Stage 3: The APM in the event of alternative payment methods transaction.
Status/error parameters:paymentMethodErrorCode
,paymentMethodErrorReason
.
Response Code Tables
API Response Codes
ERRCODE | REASON |
---|---|
1000 | General Error |
1001 | Invalid checksum |
1004 | Missing or invalid CardData data |
1007 | Invalid name on card |
1010 | Invalid user token |
1011 | Missing or invalid UserPaymentOption data |
1013 | Invalid merchant ID |
1014 | {0}Invalid country code |
1019 | Validation Error |
1021 | Invalid timestamp |
1022 | Invalid merchant site ID |
1023 | User payment option is not enabled |
1024 | UPO limit per user exceeded |
1028 | Invalid card issuer |
1029 | Invalid expired date |
1038 | Communication error |
1040 | Invalid or missing amount |
1041 | Invalid or missing amount currency |
1055 | Single UPO validation failed |
1056 | User management is off |
1057 | Invalid order ID |
1058 | Requested operation cannot be performed on this order |
1059 | Ambiguous payment data |
1060 | Missing or invalid payment data |
1061 | Invalid card token |
1062 | Invalid CVV |
1063 | Total amount does not match items amount sum |
1064 | Invalid session token. There can be only one order per session token. |
1065 | Invalid token |
1066 | Invalid request |
1067 | Invalid or missing transaction type |
1068 | Payment method is not enabled |
1069 | Session expired |
1070 | The currency is not supported by the merchant payment option settings |
1071 | Invalid request amount. The amount of the payment3D request is unequal to the amount of the Auth3D order. |
1072 | Missing or invalid PA response |
1073 | Invalid Order Currency. The currency of the payment 3D request and the currency of the Auth3D order are different. |
1074 | The user payment option is expired. |
1075 | Invalid language code |
1076 | Unsupported payment method |
1077 | API rebilling is disabled |
1078 | Missing user payment option config |
1079 | Rebilling is only allowed with user payment option. |
1080 | Invocation of this method is forbidden |
1081 | IP Address is blocked |
1082 | Invalid value of relatedTransactionId |
1083 | ekycUserDetails: The date of birth is invalid |
1084 | UserDetails: The date of birth is invalid |
1085 | Invalid request parametter value. The value of isPartialApproval should be empty or equal to 0 or 1 |
1086 | Sending of cardData block is not allowed |
1087 | Invalid request xss content |
1088 | Invalid clientRequestId. It should be provided when api setting is set to check it for uniqueness. |
1089 | There is another transaction with this clientRequestId. |
1091 | The transaction was processed by another merchant or merchant site. |
1092 | The transaction does not support the requested operation |
1093 | Missing message text! |
1094 | Invalid message locale! |
1095 | Invalid results range |
1096 | Unknown status |
1097 | Invalid value of account info field {0} in request. |
1098 | Missing account info field {0} in request. |
1099 | Payment method already registered! |
1101 | {0}Invalid state |
1102 | No such product descriptor |
1103 | The subscription plan id is invalid |
1104 | Temporary card token is forbidden for this method. |
1105 | UserDetails: firstname, lastname, email, address, zip code and country are mandatory |
1107 | Invalid methodCode |
1108 | Invalid casino |
1109 | Invalid email |
1110 | Invalid locale code |
1111 | External Error. Error received from IMS. IMS error message: {0}. |
1112 | Registration failed |
1113 | {0}The state is not from the country |
1114 | Invalid verification status |
1115 | Invalid verification method |
1116 | Payment account details not found by IMS. |
1117 | Invalid dynamic3DMode. The allowed values are: (off, on). |
1118 | Invalid isDynamic3D. The allowed values are: (0, 1). |
1120 | ekycUserDetails: invalid identificationType |
1121 | Merchant not verified |
1122 | Merchant site disabled |
1123 | Invalid items count with open amount |
1124 | Merchant site is not configured to execute Managed3D transaction. |
1125 | UPO Payment method is not supported by this method. |
1126 | When using rebilling, isDynamic3D must be equal to 1 and dynamic3DMode must be OFF. |
1127 | When using externalMPI, isDynamic3D must be equal to 1 and dynamic3DMode must be OFF. |
1128 | Invalid type: {0} |
1129 | KYC Document Upload disabled. |
1130 | Country could not be extracted from the request. |
1131 | The originUrl = [{0}] is not valid! |
1132 | The transaction has been already automatically settled. |
9064 | 3D Authentication failure |
9065 | The currency is not supported by the payment method |
9066 | Exchange rate not available |
9067 | Wrong payment method |
9068 | Wrong DCC currency |
9069 | Wrong converted amount |
9070 | Wrong original currency |
9071 | Wrong original amount |
9072 | Payment is still in progress |
9073 | Invalid or missing country and currency |
Gateway Response Codes
This table contains the error response codes sent in response, as well as DMNs (direct merchant notifications) with their descriptions.
The first three rows consist of the mapping of the error codes (gwErrCode
, gwExtendedErrCode
) to the corresponding response status field (transactionStatus
).
ERRORCODE | EXERRCODE | DESCRIPTION |
---|---|---|
0 | 0 | APPROVED |
-1 | 0 | DECLINED (please refer to Gateway Decline Reasons below) |
0 | 0 | PENDING |
-1100 | greater than 0 | ERROR (filter error) (please refer to Gateway Filter Error Codes below) |
!=0 | ERROR (gateway/bank error) | |
-1001 | 0 | Invalid login |
-1005 | 0 | IP out of range |
-1203 | 0 | Timeout/Retry |
-1 | -1 | UNEXPECTED SYSTEM ERROR - PLEASE RETRY LATER |
Gateway Filter Error Codes
This table contains the possible filter codes (gwExtendedErrCode
) and their descriptions. ErrCode
(gwErrCode
) for all filter errors is -1100.
Contact Technical Support for more information.
EXERRCODE | DESCRIPTION |
---|---|
1001 | Invalid Expiration Date |
1002 | Expiration Date Too Old |
1101 | Invalid Card Number (Alpha Numeric) |
1102 | Invalid Card Number (Digits Count) |
1103 | Invalid Card Number (MOD 10) |
1104 | Invalid CVV2 |
1105 | Auth Code/Trans ID/Credit Card Number Mismatch |
1106 | Credit Amount Exceed Total Charges |
1107 | Cannot Credit this CC company |
1108 | Illegal interval between auth and force |
1109 | Not allowed to process this CC company |
1110 | Unrecognized credit card company |
1111 | This Transaction was charged back |
1112 | Sale/Settle was already credited |
1113 | Terminal is not ready for this credit card company |
1114 | Black listed card number |
1115 | Illegal BIN number |
1116 | <Custom Fraud Screen Filter> |
1118 | 'N’ Cannot be a Positive CVV2 Reply |
1119 | 'B’/'N’ Cannot be a Positive AVS Reply |
1120 | Invalid AVS |
1121 | CVV2 check is not allowed in Credit/Settle/Void |
1122 | AVS check is not allowed in Credit/Settle/Void |
1124 | Credits total amount exceeds restriction |
1125 | Format Error |
1126 | Credit amount exceeds ceiling |
1127 | Limit exceeding amount |
1128 | Invalid Transaction Type Code |
1129 | General Filter Error |
1130 | Bank required fields are missing or incorrect |
1131 | This transaction type is not allowed for this bank |
1132 | Amount exceeds bank limit |
1133 | GW required fields are missing |
1134 | AVS Processor Error |
1135 | Only one credit per sale is allowed |
1136 | Mandatory fields are missing |
1137 | Credit count exceeded CCC restriction |
1138 | Invalid Credit Type |
1139 | This card is not supported in the CFT Program |
1140 | Card must be processed in the GW System |
1141 | Transaction type is not allowed |
1142 | AVS required fields are missing or incorrect |
1143 | Country does not match ISO Code |
1144 | Must provide UserID in a Rebill transaction |
1145 | Your Rebill profile do not support this transaction type |
1146 | Void is not allowed due to CCC restriction |
1147 | Invalid Account Number |
1148 | Invalid Cheque Number |
1149 | Account Number/Trans ID Mismatch |
1150 | UserID/Trans Type /Trans ID Mismatch |
1151 | Transaction does not exist in the rebill system. |
1152 | Transaction was already cancelled |
1153 | Invalid Bank Code(Digits Count) |
1154 | Invalid Bank Code (Alpha Numeric) |
1155 | 3D Related transaction is missing or incorrect |
1156 | Debit card required fields are missing or incorrect |
1157 | No update parameters were supplied |
1158 | 3D PaRes value is incorrect |
1159 | State does not match ISO Code |
1160 | Invalid Bank Code (Checksum Digit) |
1161 | This Bank allows only 3 digits in CVV2 |
1162 | Age verification Failed |
1163 | Transaction must contain a Card/Token/Account |
1164 | Invalid Token |
1165 | Token Mismatch |
1166 | Invalid Email address |
1167 | Transaction already settled |
1168 | Transaction already voided |
1169 | sg_ResponseFormat field is not valid |
1170 | Version field is missing or incorrect |
1171 | Issuing Country is invalid |
1172 | Phone is missing or format error |
1173 | Check number is missing or incorrect |
1174 | Birth date format error |
1175 | Zip code format error |
1176 | Cannot void an auth transaction |
1177 | Cannot void a credit transaction |
1178 | Cannot void a void transaction |
1179 | Cannot perform this void |
1180 | Invalid start date |
1181 | Merchant Name is too long (>25) |
1182 | Transaction must be sent as 3DSecure |
1183 | Account is not 3D enabled |
1184 | Transaction 3D status is incorrect |
1185 | Related transaction must be Auth3D, APPROVED, same 3DS version and same merchant |
1186 | Related transaction must be 3D authenticated |
1187 | Country does not support the CFT program |
1188 | Invalid token ID |
1190 | Risk processor error |
1191 | RiskOnly is supported from version 4.0.0 and above |
1192 | AGV processor error |
1193 | AGVOnly is supported from version 4.0.1 and above |
1194 | Age verification mismatch |
1195 | Requested acquirer is unrecognized |
1196 | Sale transaction isn’t processed on acquirer side yet |
1197 | Input data is not sufficient |
1198 | Credit card details are not allowed for the given Payment Method |
1199 | Envoy payout transaction requires credit transaction of type 1 |
1200 | Invalid issuing bank country code |
1201 | Invalid Amount |
1202 | Invalid Currency |
1203 | IBAN does not match country code |
1204 | Payment method is not supported |
1205 | APM risk processor error |
1206 | Settle amount exceeds total charges |
1207 | Cannot perform this credit |
1208 | Converted transaction cannot be handled, please use alternative interfaces |
1209 | Client is not allowed for Partial Approval |
1210 | NameOnCard is missing |
1214 | Invalid FinalizationURL |
1220 | Expired Token |
1230 | Invalid or missing PFSubMerchantId input parameter |
1231 | Invalid or missing MerchantName input parameter |
1232 | Invalid or missing PFSubMerchantCountry input parameter |
1233 | Invalid or missing PFSubMerchantCity input parameter |
1265 | One year passed since last sale, Payout declined |
1266 | Submethod not supported |
1267 | This card is not supported in the Visa Direct OCT program. |
1268 | Token is inactive |
1269 | Cannot get cryptogram |
1270 | The client is not configured to account update |
1271 | sg_transaction must be of type InitAuth3D, Approved and the same merchant |
1272 | Card number must be equal for all transaction in a specific 3DS flow |
1273 | Card number, Currency and Amount must be equal in a specific 3DS flow |
1274 | Requested Auth3D 2.0 but card number is not supported with 3DS 2.0 |
1275 | initAuth3D represented by sg_transactionId was already used in another 3D flow |
1276 | Authentication request could not be completed – timeout, please try again later |
1277 | DS responded with an error, please verify request and try again |
1278 | Authentication is expired, new InitAuth3d is required |
1279 | 3D related transaction was already used for Sale/Auth |
1280 | Mandatory field is missing: sg_threeDSMethodNotificationURL
|
1281 | Authentication has not completed |
1282 | Authentication failed |
1283 | Required field sg_ThreeDSPlatformType is missing or invalid |
1284 | Invalid external MPI parameters format |
1285 | Exceeding refund time frame |
1500 | Client Is Not Allowed To Use This Channel |
1501 | Client Is Not Allowed To Use Suppress Auth |
1550 | Not all the auto reversal parameters were sent in the request |
1551 | Client is not permitted to use auto reversal functionality |
1552 | Input parameter data type incorrect |
1553 | Currency of auto reversal does not match the currency of the settle |
1554 | Amount of auto reversal does not match the amount of the settle and auth |
1555 | Auto Reversal Cannot be Allowed with Multiple Settle |
1556 | Settle amount plus AutoReversal Amount should be equal to Original Auth |
1557 | Original currency does not match auto reversal currency |
1558 | Incorrect Auto-Reversal Input Parameters |
1559 | Cannot void auth, transaction has already been settled |
1560 | Not Allowed to Process this Auth Type |
2001 | The requested acquirer bank is temporarily unavailable |
2002 | ApmRisk is disabled |
2025 | External MPI not supported for this acquirer |
2030 | Invalid external token provider |
3001 | Invalid Interval for sale reversal |
3002 | Invalid Interval for refund reversal |
3003 | Invalid Interval for OCT reversal |
3004 | Transaction has already been reversed |
3005 | Transaction is not approved |
3006 | Transaction type does not match reversal type |
3007 | Transaction has not been transmitted |
3008 | Transaction already has chargeback record |
3500 | Invalid POS Parameter |
3501 | Mandatory POS Parameter is missing |
3502 | KYC parameters error |
10012 | Saved payment option no longer valid |
10013 | Cannot register payment option at APM |
10014 | APM authentication error |
Gateway Decline Reasons
This table contains the possible decline reasons received in the decline reason (gwErrorReason
).
ERRCODE | EXERRCODE | DECLINE REASON | DESCRIPTION |
---|---|---|---|
-1 | 0 | Call issuer | Refers to the issuer. It is possible that such transactions could be authorized with voice AuthCode. |
-1 | 0 | Invalid merchant | General decline message. Typically, this does not indicate any general issue with the merchant or MID. This decline reason is usually the result of an issue regarding an internal standard. |
-1 | 0 | Pick up card | This is a general decline message from the issuer indicating that the consumer should retrieve the card. This message may be received when the card is reported as lost/stolen. |
-1 | 0 | Do not honor | The most common and general issuer decline code. This code is generated by the issuer when no specific decline reason/code is returned. |
-1 | 0 | External Error in Processing | This is a general error message. When receiving this error, the transaction may succeed when trying again later. |
-1 | 0 | Pick up card, special condition (fraud account) | This is a general decline message from the issuer indicating that the consumer should retrieve the card. This message may be received when the card is reported as lost/stolen. |
-1 | 0 | Invalid transaction | The most common and general issuer decline code. This code is generated by the issuer when no specific decline reason/code is returned. |
-1 | 0 | Invalid amount | This decline code is the result of an issue with the transaction amount. This code may be triggered as a result of the currency or financial reasons such as insufficient funds. |
-1 | 0 | Invalid card number | The transaction could not be processed with the provided credit card number. This may indicate that the card number does not exist. |
-1 | 0 | No such issuer | This decline code indicates that there is a problem with the credit card number, for example, the credit card BIN doesn’t match the range of any issuer in the acquirer’s list. |
-1 | 0 | Unable to locate record in file | The transaction failed due to a technical issue. When receiving this error, the transaction may succeed when trying again later. |
-1 | 0 | File temporarily not available | The transaction failed due to a technical issue. When receiving this error, the transaction may succeed when trying again later. |
-1 | 0 | Format error | For MasterCard or Maestro Card, this decline code may be the result of an invalid CVV number or a CVV number that could not be verified. This decline code may also be generated as the result of a 3D Secure-related issue, for example, the issuer requires transactions to be 3D secured and the transaction was processed through a non-3D Secure account. |
-1 | 0 | No credit account | This usually indicates that there is an issue with the account connected to the credit card, for example, the account is expired, cancelled, or does not exist. |
-1 | 0 | Lost card, pickup | This decline code is returned when the card is listed as lost on the issuer’s side. |
-1 | 0 | Stolen card, pickup | This decline code is returned when the card is listed as stolen on the issuer’s side. |
-1 | 0 | Insufficient Funds | The credit card holder lacks sufficient funds to complete the transaction. |
-1 | 0 | No checking account | This usually indicates that there is an issue with the account connected to the credit card, for example, the account is expired, cancelled, or does not exist. |
-1 | 0 | No savings account | This usually indicates that there is an issue with the account connected to the credit card, for example, the account is expired, cancelled, or does not exist. |
-1 | 0 | Expired card | The credit card is no longer valid or was cancelled. It is also possible that the expiration date does not match the card details. |
-1 | 0 | Incorrect PIN | This decline code is similar to other PIN-based declines, and may indicate that the card is being blocked due to a security issue, such as exceeding the limit of PIN entry attempts at a point of sale. |
-1 | 0 | Transaction not permitted to cardholder | The issuer did not allow this transaction against this card based on internal reasons, such as the transaction originated from a specifically restricted industry or country. |
-1 | 0 | Transaction not permitted on terminal | The issuer rejected the transaction based on its technical origin or requester. When this error reoccurs, it may indicate that the Issuer does not allow transactions from this specific merchant or industry type. |
-1 | 0 | Suspected fraud | The transaction is suspected to be fraudulent. |
-1 | 0 | Exceeds withdrawal limit | The transaction amount exceeds the permitted amount for this card or account. |
-1 | 0 | Restricted card | The card is marked as restricted on the issuer’s systems. |
-1 | 0 | Error in decryption of PIN block | The decline code is the result of a security violation and may indicate that the card has been restricted. |
-1 | 0 | Exceeds withdrawal frequency | The transaction amount or count exceeds the permitted frequency for this card or account. |
-1 | 0 | Invalid transaction; contact card issuer | A general decline message likely indicating that the transaction was rejected for financial reasons, as well as the issuer’s internal standards. |
-1 | 0 | PIN not changed | The transaction was declined as a result of the PIN code. |
-1 | 0 | PIN tries exceeded | The card was blocked on the issuer’s system due to an excessive amount of PIN entry attempts at the point of sale. This decline code may be returned during an online transaction even though the PIN is not entered for online transactions. This message may be received when a card was blocked following a card-present transaction. |
-1 | 0 | Invalid “To” account specified | This decline code is also known as ‘Unsolicited Reversal’, and might mean that the ‘to’ [debit] account does not exist, is not connected to the card, or card was restricted. |
-1 | 0 | Invalid “From” account specified | The ‘from’ [credit] account does not exist. |
-1 | 0 | Invalid account specified | This indicates that there is an issue with the account associated to the credit card number, for example, the number does not exist or is invalid. |
-1 | 0 | System not available | This indicates that there was a technical issue preventing the completion of this transaction. |
-1 | 0 | Cryptographic error found in PIN | This decline code is similar to other PIN-based declines, and may indicate that that the card is being blocked due to a security issue, such as exceeding the limit of PIN entry attempts at a point of sale. |
-1 | 0 | Cannot verify PIN | The transaction was declined as a result of the PIN code. |
-1 | 0 | PIN unacceptable. Retry. | The transaction was declined as a result of an unacceptable PIN code. |
-1 | 0 | Issuer or switch inoperative | The acquirer was unable to complete the transaction on the issuer’s side, for example, as a result of a timeout. |
-1 | 0 | Routing error | This indicates that the transaction request could not reach the authorising destination (scheme/issuer). This may indicate that the credit card type is not processed by the acquirer. |
-1 | 0 | Transaction cannot be completed | The issuer could not complete the authorisation of this transaction. If this occurs again, the cardholder should try contacting the issuer. |
-1 | 0 | Duplicate transaction | Indicates that a transaction was sent twice. |
-1 | 0 | Timeout/Retry | A timeout occurred between the acquirer and the issuer. |
-1 | 0 | Invalid CVV2 | The transaction was rejected as a result of the CVV2 and usually indicates that CVV2 provided does not match the credit card number. This code is relevant for Visa only. |
-1 | 0 | Revocation of Authorization Order | This decline code may indicate that the cardholder requested to discontinue recurring transactions. |
-1 | 0 | Revocation of All Authorizations Order | This decline code may indicate that the cardholder requested to discontinue recurring transactions. |
-1 | 0 | Soft Decline – Authentication is Advised | The issuer has declined the transaction for authentication reasons. Running the transaction again with 3DS 2.0 / 1.0 might help to get the transaction approved. |