Explore top Card payment errors, identify causes and actionable next steps.
Below are the top card payment error codes, along with their reasons, detailed descriptions, and recommended resolution steps.
| ppc_ParentTxnResponseCode | ppc_ParentTxnResponseMessage | Error Description | Next Steps | Error Step | Error Source |
|---|---|---|---|---|---|
| 1030 | CONTACT CARD ISSUER | The issuing bank prevented the transaction. | The customer to complete the transaction with another card or reach out to Issuer Bank to get more details. | Authorization | Issuer |
| -272 | BANK RESPONSE :INVALID MERCHANTID | Used when the issuer or cardholder has restricted (temporary or permanent) the card or product definition to not allow usage at Merchant Category Code (MCC). | The Merchant can reach out to the account manager or customer care. | Authorization | Issuer |
| 1037 OR -178 | STOLEN CARD, PICK UP OR CARD BLOCKED.CONTACT CUSTOMER SERVICE | Used for scenarios where the account has been closed, typically for non-fraud reasons. | The customer to complete the transaction with another card or reach out to Issuer Bank to get more details. | Authorization | Issuer |
| -2 | DO NOT HONOR | The issuing bank is declining the transaction for unspecified reasons. | Advise the customer to use a different card or contact their bank for more information. | Authorization | Issuer |
| -4 OR -278 | INVALID TRANSACTION OR INVALID TRANSACTION TYPE | The transaction type is not supported or the request contains invalid data. | Verify your card details and try again. If the problem continues, please contact your card issuer. | Authorization | Issuer |
| -980 | INVALID AMT OR CURRENCY CONVERSION FIELD OVERFLOW | The transaction amount is either invalid or exceeds the permissible limit for currency conversion. | Verify and re-enter the correct amount, or contact Pinelabs for assistance. | Authorization | Issuer |
| -981 | INVALID ACCOUNT NUMBER | The card number provided is incorrect or does not match any existing account. | Ask the customer to re-enter the card details or use a different card. | Authorization | Issuer |
| -982 | RE-ENTER TRANSACTION | The transaction was not processed correctly and needs to be reattempted. | Retry the transaction or advise the customer to use another card. | Authorization | Issuer |
| -374 OR 1035 | LOST CARD / STOLEN CARD | The card has been reported lost, and the transaction has been declined due to suspected fraud. | Advise the customer to contact their bank immediately and use another card. | Authorization | Issuer |
| -1024 | CLOSED ACCOUNT | The account linked to the card has been closed. | Advise the customer to use a different card or contact their bank for clarification. | Authorization | Issuer |
| -6 | INSUFFICIENT FUND | The customer’s account has insufficient funds to complete the transaction. | Advise the customer to either use another card or add funds to their account. | Authorization | Issuer |
| 1009 | INCORRECT PERSONAL IDENTIFICATION NUMBER/INCORRECT PIN | The customer has entered an incorrect PIN or has not entered a PIN where required. | Advise the customer to re-enter the correct PIN or contact their bank for PIN reset. | Authorization | Issuer |
| -5 | EXPIRED CARD | The card has expired and is no longer valid for transactions. | Advise the customer to use a different card or renew their card. | Authorization | Issuer |
| -376 OR 1040 OR -70 | TRANSACTION NOT PERMITTED TO CARDHOLDER OR DUPLICATE RESPONSE RECEIVED FROM BANK | The card issuer has restricted the cardholder from making this type of transaction. | Advise the customer to contact their bank or use a different card. | Authorization | Issuer |
| -1026 | TRANSACTION NOT ALLOWED AT TERMINAL | The transaction type is not permitted on this terminal or payment method. | Advise the customer to use a different card. | Authorization | Issuer |
| 1033 | SUSPECTED FRAUD | The transaction has been flagged by the issuer or fraud prevention system as potentially fraudulent. | Advise the customer to contact their bank or use a different card. | Authorization | Issuer |
| -176 | EXCEEDS LIMIT AMOUNT | The transaction amount exceeds the limit set by the card issuer. | Advise the customer to check the account balance/credit limit or contact their bank for further details. | Authorization | Issuer |
| -368 | RESTRICTED CARD OR TRANSACTION IS GOING ON WITH SAME TRANSACTION ID OR TRANSACTION ALREADY PROCESSED | The card is restricted for use in this region or country. | Advise the customer to contact their bank or use a different card. | Authorization | Issuer |
| -3 | SECURITY VIOLATION | The transaction failed due to a security issue, possibly related to encryption. | Advise the customer to contact their bank or use a different card. | Authorization | Issuer |
| -380 | Declined by acquirer | The customer has opted some restrictions, like opting out of gambling or e-commerce, may be the result of cardholder settings and can be addressed by the cardholder. | Advise the customer to contact their bank or use a different card. | Authorization | Issuer |
| -377 | EXCEEDS WITHDRAWAL FREQUENCY LIMIT/NUMBER OF TIMES USED | The customer has exceeded the number of withdrawals allowed within a specified period. | Advise the customer to check the withdrawal limit allowed within a specific period or contact their bank for further details. | Authorization | Issuer |
| -373 | PIN TRIES EXCEEDED/ALLOWABLE PIN TRIES | The customer has exceeded the maximum number of PIN entry attempts. | Advise the customer to contact their bank for assistance. | Authorization | Issuer |
| -992 | CRYPTOGRAPHIC ERROR FOUND IN PIN | There was an issue with the cryptographic validation of the PIN. | Advise the customer to re-enter the PIN or contact their bank. | Authorization | Issuer |
| -993 OR 1031 | NEGATIVE CAM, DCVV, ICVV, OR CVV RESULTS OR RESERVED FOR PRIVATE USE | The card’s security code (CVV) or cryptographic validation failed. | Advise the customer to re-enter their card details or use a different card. | Authorization | Issuer |
| -81 | INVALID TRACK ID DATA | The entered CVV is invalid. | Advise the customer to enter the correct CVV or try another card. | Authorization | Issuer |
| -318 | NO ISSUER FOUND | The issuing bank’s system is temporarily down or experiencing issues. | Advise the customer to try again later or use a different card. | Authorization | Issuer |
| 1018 | SUSPECTED MALFUNCTION | A technical error occurred during the transaction process, likely at the issuer’s end. | Advise the customer to retry or contact their bank for more details or use a different payment method. | Authorization | Issuer |
| -370 | DECLINED DUE TO ISSUER COMPLIANCE BY SCHEME | The issuer’s response did not comply with network's regulations or protocols. | Advise the customer to contact their bank for more details or use a different payment method. | Authorization | Issuer |
| -1029 | DECLINED BY ISSUER - DUE TO ISSUER UNABLE TO AUTHORISE | The issuer could not authorize the transaction due to technical or other issues. | Retry the transaction or advise the customer to contact their bank. | Authorization | Issuer |
| -92 OR -372 | INVALID EXPIRATION DATE | The transaction was declined because the card's expiration date provided during the payment process is invalid or incorrect. | Ask the customer to verify and re-enter the correct expiration date. If the issue persists, suggest they contact their card issuer for assistance or try another card. | Authorization | Issuer |
| -1027 | DECLINED BY PROCESSOR | The Payment ID used for this transaction has expired. | Advise the customer to initiate a new transaction or contact their bank or use a different card. | Enrollment/Authentication | Processor |
| -54 | AUTHENTICATION NOT AVAILABLE | The issuer is unable to authenticate the customer for 3D secure transaction OR OTP page is not rendered. | The customer can reach out to the Issuer Bank to get more details. | Authentication | Processor |
| -430 | Authentication Pending From Customer | The customer reached to authentication page but didn't take any actions | Advise the customer to attempt the transaction. | Authentication | Issuer |
| -21 | AUTHENTICATION FAILED | The customer attempted authentication but the issuer is unable to authenticate the customer for 3D Secure transaction. | Advise the customer to contact their issuer bank for more details or attempt the transaction with another card. | Authentication | Processor |
| -86 | INVALID BRAND | The card network could not be identified by the processor. | Suggest the customer initiate a new transaction using a different card or network. | Authentication | Processor |
| -9 OR -1006 | CARD VERIFICATION FAILURE | The Card Verification Digit (CVV) is required but was either not provided or invalid. | Ask the customer to re-enter the correct CVV or use another card. | Authorization | Issuer |
| -428 | NO ACTION TAKEN BY CUSTOMER | The issuer couldn't authenticate the customer, the payment failed as 3D Secure/OTP was not attempted. | Advise the customer to reattempt the transaction. | Authentication | Processor |
| -1030 | DECLINED BY INTERNAL PROCESSOR - CONFIGURATION ERROR | The card processor could not process the transaction due to a configuration issue. | Advise the customer to use a different card or contact support for further assistance. | Authentication | Processor |
| -13 | CARD SECURITY CODE VERIFICATION FAILED | The CVV provided is incorrect. | Ask the customer to re-enter the correct CVV or use a different card. | Authentication | Processor |
| -303 | INVALID_CARD_HOLDER_NAME | The cardholder name is missing or invalid for the transaction. | Ask the customer to enter the correct name as it appears on the card. | Authentication | Processor |
| 2083 | CUSTOMER CANCELED THE TRANSACTION | The customer canceled the transaction while being redirected to their bank's authentication page. | Suggest the customer attempt the payment again or use a different card. Alternatively, contact their bank. | Before Authentication | Processor |
| 2084 | ISSUER AUTHENTICATION SERVER FAILURE | The issuer's authentication server failed during a Rupay card transaction, causing the authentication to fail. | Advise the customer to retry the transaction or use another card. If the issue persists, contact the issuing bank. | Authentication | Issuer |
| 2085 | OTP PAGE REFRESHED | The customer refreshed the OTP page during the authentication process, leading to a failed transaction. | Ask the customer to retry the transaction without refreshing the page. Suggest using another card if needed. | Authentication | Issuer |
| 2086 | TRANSACTION DECLINED DUE TO CARD NOT FOUND | The transaction was declined as the issuer could not find the card while generating the OTP. | Ask the customer to verify card details and retry. If the issue persists, contact the issuing bank. | Authentication | Issuer |
| 2087 | BIN NOT PRESENT IN 3DS2.X | The BIN used was not present in 3DS2.X, and since 3DS 1.0 was sunset, the transaction was declined. | Suggest using a different card. | Authentication | Processor |
| 2089 | ISSUER DECLINED TRANSACTION DUE TO SYSTEM ERROR | The issuer declined the transaction due to a system error during authentication for Rupay cards. | Request the customer to try again or use a different card. If the issue remains, contact the issuing bank. | Authentication | Issuer |
| 2088 | Process time limit exceeded | The transaction was declined because the process time exceeded the allowed limit, leading to the expiration of the Payment ID. | Ask the customer to retry the transaction. Ensure that the payment is completed within the required time frame to avoid expiration. | Authentication | Issuer |
| 2090 | E-commerce flag not enabled | The customer's Rupay card does not have the e-commerce flag enabled, which is required for online transactions. | Ask the customer to enable the e-commerce flag via their issuing bank or use a different card. | Authentication | Issuer |
| 2091 | Customer exhausted OTP resend attempts | The customer exceeded the maximum number of OTP resends allowed during the authentication process. | Advise the customer to wait and retry the transaction later or use a different card. | Authentication | Issuer |
| 2092 | OTP expired during authentication | The OTP entered by the customer expired before it was used to authenticate the transaction. | Ask the customer to retry the transaction and use the OTP within the provided time limit. | Authentication | Issuer |
| 2093 | BIN not live at NPCI | The transaction was declined because the BIN (Bank Identification Number) is not live at the BEPG (Bill Exchange Payment Gateway) end, resulting in no response to the checkBin API request from NPCI. | Ask the customer to use a different card or contacting their bank for further assistance. | Enrollment | Network |
| 2094 | Authorization declined by the card issuer | This is an authorization decline from the card issuing bank, and as a payment gateway, we do not have full visibility into the specific reason for the decline. | Advise the customer to contact their card-issuing bank for the exact reason for the decline. Alternatively, the customer may retry the transaction or use a different card. | Authorization | Issuer |
| 2095 | Customer exhausted OTP verification attempts | The customer has exceeded the allowed number of OTP verification attempts, causing the transaction to fail. | Suggest the customer retry the transaction later or use a different card. They may also contact their bank for further assistance. | Authentication | Issuer |
| 2097 | E-commerce not enabled for the card | The transaction was declined because the customer’s card does not have e-commerce functionality enabled, preventing online transactions. | Ask the customer to enable e-commerce transactions by contacting their issuing bank or use a different card that supports online payments. | Authentication | Issuer |
| 2098 | Invalid OTP entered | The transaction was declined because an invalid OTP was entered during authentication. | Ask the customer to retry the transaction and ensure the correct OTP is entered. If the issue persists, advise them to contact their issuing bank for further assistance. | Authentication | Issuer |
| 2096 | Transaction denied by the card network | The transaction was denied by the card network. | Advise the customer to retry the transaction or use a different card. If the issue persists, suggest they contact their card issuer for more details. | Enrollment | Network |
| 2099 | Tokenization failed | This occurred because the provided authorization reference number was invalid during token provisioning for Rupay transaction. | Request the customer to retry the transaction with another card network or advise the customer to check with their issuing bank for further details. | Tokenisation | Network |
| -1 OR 2002 OR -69 | Failure OR TECHNICAL ERROR, PLEASE RETRY LATER. OR INVALID RESPONSE RECEIVED FROM BANK | This is due to internal (PL) technical error. | - | - | Internal |
| -69 | INVALID RESPONSE RECEIVED FROM BANK | This is due to internal technical error | - | - | Internal |
| -382 | Authentication not allowed | The transaction was declined because frictionless authentication is not permitted according to RBI guidelines, which require an additional layer of authentication for such transactions. | Advise the customer to retry the transaction with the required authentication steps or consult their bank for further details on RBI compliance for such transactions. | Authentication | Issuer |
| 2100 | TRANSACTION CANCELLED DUE TO INACTIVITY FROM CUSTOMER/NETWORK | The transaction could not proceed due to customer inactivity and was ultimately marked as failed. | The customer will need to retry the transaction, ensuring stable network connectivity and actively completing all required steps. | Before Authentication | Processor |
| -381 | Account doesnt exist with issuer | The transaction was declined because the account/card number provided is invalid or incorrect, preventing the payment from being processed. | Ask the customer to verify and re-enter the correct account number. If the issue persists, they should contact their card issuer for further assistance. | Authorization | Issuer |
| -307 | INVALID_CARD_DATA | The transaction failed due to invalid card details. Scenarios are, Validate the card using Luhn's Formula. The CVV must be an integer, the expiration month should be between 1 and 12, the year must be a valid integer greater than 0, and the expiry date must be later than the current month. | Ask the customer to double-check and re-enter the correct CVV, month, and year. If the issue persists, suggest they try a different card or contact their card issuer for further assistance. | - | PG |
| -60 | TXN COUNT LIMIT IS EXHAUSTED | The transaction was declined because the card has reached the maximum allowed transaction count set by the processor. This limit prevents any further transactions from being processed on the card. | Advise the customer to try using a different card or payment method to complete the transaction. | - | Processor |
Note:
In the above table , ppc_ParentTxnResponseCode and ppc_ParentTxnResponseMessage apply to Inquiry responses.
Similarly, the same response codes and messages are presented as txn_response_code and txn_response_msg in Webhook and Redirect responses.