Here we help you understand what information decline codes hold and how you can resolve situations when a payment is declined.
| Code | Description | Description | Recommendations for Merchants |
0.01 | General decline | The general group of declines. The card issuing bank did not complete the transaction successfully. | Kindly ask the user to try to pay a couple more times. The Chances are high that the next attempt will be successful. |
0.02 | Order expired | The user could not finalize the payment during the given timeframe, which resulted in order expiration. | Kindly suggest to the user to try again with the same card. In the case of a PayPal order, decline code 0.02 means that there were no attempts to pay via PayPal, so the initialized PayPal button has expired. |
0.03 | Violation of law | In some cases, the card issuer can block a transaction for law violation reasons. It can be due to a cardholder or due to a sanctioned country. | Kindly suggest to the user to use another card. |
1.01 | Authentication failed | Cardholder authentification was not successful. | Kindly ask the user to try to pay a couple more times. The Chances are high that the next attempt will be successful. |
2.01 | Invalid Data / Order not found | The problem here lies with the data format and accuracy, validation error on the acquiring side. |
|
| 2.02 | Invalid Amount | There is a limit on the amount of the order on the acquiring side. | Kindly review the order amount against acquiring bank limits. Adjust or split as needed. For further queries or assistance, contact SolidGate Support. |
2.03 | Invalid Currency | The currency here is not supported. | Kindly contact SolidGate Support. More likely, we will be able to suggest a solution for you. |
2.05 | Order not Found | Integration error, request invalid data. | Kindly contact SolidGate Support. More likely, we will be able to suggest a solution for you. |
2.06 | Invalid CVV2 code | Invalid CVV2 code The CVV code is the three-digit code on the back of a MasterCard or Visa, or the four-digit code on the front of an American Express. | If it is the first occasion - kindly ask the user to try one more time. If CVV code error is recurring for the same user - potential card fraud. Act accordingly to your policies. |
2.08 | Invalid Card Number | The user entered an incorrect card number. | Kindly ask the user to enter a valid card number. |
2.09 | Invalid Expiration Date | Card is expired |
|
2.10 | Invalid 3DS flow on the merchant side | 3DS URL was not displayed to the cardholder during 3-D Secure authentification attempts | Kindly ask a user to recall the step-by-step payment flow and forward information received to SolidGate Support. |
2.11 | Invalid 3DS flow on the bank's side | The user went through a payment flow, but the bank did not initiate 3DS authorization. | Kindly ask the user to try one more time or suggest to the user to use another card. |
2.12 | Invalid 3DS flow | User hesitated with 3D Secure authentication. | Kindly ask the user to try one more time or suggest to the user to use another card. |
2.14 | Subscription error | The user_id is subscribed to the product_id. | Our systems check user_id for active subscriptions, and if product_id of active subscription matches the one you are sending in an order for subscription activation, Solid will decline the payment in question. |
2.15 | SCA require 3D authentication | The order was tried to be processed without 3D verification, in cases of the EU transactions, which require 3D authentication |
|
3.01 | Card is blocked | The card issuer bank blocked the card for payments. | Card issuer banks have various logics to block risky transactions: - Limit on online payments; - Daily limit on payments amount; - Daily limit on the number of payments; - Limits for payments with 3DS authorization; etc. It is necessary to explain to the user that the issuing bank is blocking the transaction. Most likely, one of the card limits is triggered. The customer can contact the bank's support service and ask to remove the limit in question to make the payment. You can also recommend the user try to pay again. For many banks, the rules are not static but triggered based on a scoring system, and repeated attempts to conduct a transaction increase the likelihood of a transaction going through. |
3.02 | Insufficient funds | The user's card balance has insufficient funds. | Kindly suggest to the user another card or top-up the current one. |
3.03 | Payment amount limit excess | Card payment/credit limit was reached | Card issuer banks have various logics to block risky transactions: - Limit on online payments; - Daily limit on payments amount; - Daily limit on the number of payments; - Limits for payments with 3DS authorization; etc. It is necessary to explain to the user that the issuing bank is blocking the transaction. Most likely, one of the card limits is triggered. The customer can contact the bank's support service and ask to remove the limit in question to make the payment. You can also recommend the user try to pay again. For many banks, the rules are not static but triggered based on a scoring system, and repeated attempts to conduct a transaction increase the likelihood of a transaction going through. |
3.04 | The transaction is declined by the issuer | Contact the card issuer to determine the reason. | Card issuer banks have various logics to block risky transactions: - Limit on online payments; - Daily limit on payments amount; - Daily limit on the number of payments; - Limits for payments with 3DS authorization; etc. It is necessary to explain to the user that the issuing bank is blocking the transaction. Most likely, one of the card limits is triggered. The customer can contact the bank's support service and ask to remove the limit in question to make the payment. You can also recommend the user try to pay again. For many banks, the rules are not static but triggered based on a scoring system, and repeated attempts to conduct a transaction increase the likelihood of a transaction going through. |
3.05 | Call your bank | Contact card issuer for clarifications. | Card issuer banks have various logics to block risky transactions: - Limit on online payments; - Daily limit on payments amount; - Daily limit on the number of payments; - Limits for payments with 3DS authorization; etc. It is necessary to explain to the user that the issuing bank is blocking the transaction. Most likely, one of the card limits is triggered. The customer can contact the bank's support service and ask to remove the limit in question to make the payment. You can also recommend the user try to pay again. For many banks, the rules are not static but triggered based on a scoring system and repeated attempts to conduct a transaction increase the likelihood of a transaction going through. |
3.06 | Debit card not supported | The card has been declined for an unknown reason. | Kindly suggest using another card. |
3.07 | Card brand is not supported | The card has been declined for an unknown reason. | Kindly ask the user to use another card, the one specified in your payment form. |
3.08 | Do not honor | The card has been declined for an unknown reason. | The customer should contact their card issuer for more information. More likely the next attempt will be successful. |
| Suspected Fraud | The issuing bank blocked the transaction due to possible fraud. The card wasn't in use for a long time, unusual activity, etc. | The customer should contact their card issuer for more information. More likely the next attempt will be successful. |
| 3.11 | Recurring Payment Cancelled | The transaction will not be approved by the issuer, regardless of the circumstances. | The customer should contact their card issuer for more information. Although, please do not retry such transactions. |
| 3.12 | Closed User Account | The customer has blocked transactions via this card for reasons that require clarification. | Kindly ask the user why they have blocked transactions. If the customer did not initiate this action, please ask the customer to contact their card issuer for more information. |
4.01 | Card is in blacklist | The card is on the blacklist. | Show general decline to the customer. It is best to check the customer for fraudulent activity. |
4.02 | Stolen card | The card in use is stolen, all transactions are restricted. | Show general decline to the customer. It is best to check the customer for fraudulent activity and block if necessary. |
4.03 | Restricted Card | The card cannot be used to make this payment (it is possible it has been reported lost or stolen). | Kindly suggest using another card. |
4.04 | Lost Card | The card in use is lost, all transactions are restricted. | Show general decline to the customer. It is best to check the customer for fraudulent activity and block if necessary. |
4.05 | PSP Antifraud | The acquiring bank blocked the transaction due to possible fraud. The card wasn't in use for a long time, unusual activity, etc. | Show general decline to the customer. It is best to check the customer for fraudulent activity and block if necessary. |
4.06 | Blocked by Country/IP | Blocked by IP mismatch or dye to a high-risk country IP. | Show general decline to the customer. It is best to check the customer for fraudulent activity and block if necessary. Otherwise, kindly suggest to the customer to try one more time. |
4.07 | Trusted Anti Fraud system | An antifraud rule was triggered. | Show general decline to the customer. It is best to check the customer for fraudulent activity and block if necessary. Otherwise, kindly suggest to the customer to try one more time. |
4.09 | Solid antifraud engine | An antifraud rule was triggered | Show general decline to the customer. It is best to check the customer for fraudulent activity and block/unblock if necessary. Otherwise, kindly suggest to the customer to try one more time. |
5.01 | 3D Secure verification failed | 3D Secure verification failed | Show general decline to the customer. It is best to check the customer for fraudulent activity and block if necessary. Otherwise, kindly suggest to the customer to try one more time. |
5.02 | Invalid Card Token | We received an invalid/nonexistent card token. | Kindly ask the customer to try one more time or to use another card. Please contact SolidGate Support to let us know. |
5.03 | Application Error | Processing error. | Kindly ask the customer to try one more time or to use another card. Please contact SolidGate Support to let us know. |
5.04 | Merchant is not configured yet | Processing error. | Please contact SolidGate Support. |
5.05 | Merchant is not activated yet | Processing error. | Please contact SolidGate Support. |
5.08 | Invalid Transaction | Processing error. | Kindly ask the customer to try one more time or to use another card. If another card is not an option - kindly suggest contacting the bank. |
6.01 | Unknown Decline Code | Unknown Decline Code yet to be mapped. | Kindly ask the customer to try one more time or to use another card. If another card is not an option - kindly suggest contacting the bank. |
6.02 | Connection Error | A connection is poor or interrupted. | Kindly ask the customer to try one more time or to use another card. |
7.01 | Card Token not found | An error occurred and the token was not found. | More likely card is expired. Kindly check exp. date, available in order details - logs, via Solidgate hub. Otherwise, please contact SolidGate Support. |
7.02 | Google payment error | The payment has been declined via Google Pay. | Please contact SolidGate Support. |
7.03 | Smart cascade decline | The payment was declined due to the token error on the cascade. | Please contact SolidGate Support. |
7.04 | 3DS cascade to 2D | Processing error. | Please contact SolidGate Support. |
7.05 | Apple online payment error | The payment has been declined via Apple Pay. | Please contact SolidGate Support. |
7.06 | Token generation error | Token generation was not successful. | Please contact SolidGate Support. |