Point of Sale
For an in-person payments integration, see the most common raw responses that Terminal API returns.
When a card scheme or issuer declines a transaction, they send us a raw response to explain why. This is also known as the "raw acquirer response".
The many raw responses are slightly different between schemes and are subject to change. For that reason, we map raw responses for failed transactions to a combination of a resultCode field with a value of Refused or Cancelled, and a refusalReason field explaining why the transaction did not succeed.
If you want to receive the raw response in your API responses as well, you can enable that in your Customer Area.
On this page, we describe the most common raw responses related to refused or canceled transactions. In the tables, Journal type refers to payment details in your Customer Area.
Requirements
| Requirement | Description |
|---|---|
| Integration type | An online payments integration. |
| Setup steps | Before you begin, in your Customer Area enable receiving raw responses. |
Recommendations
Take the following recommendations into account with regard to handling raw responses.
-
The raw response provides additional information about why the transaction failed. Be aware that card schemes and issuers sometimes change the text without notice.
-
To prevent the malicious use of data, you must not expose the details of raw responses to shoppers.
Receive raw responses
If you want to receive the raw response for declined transactions:
- Log in to your Customer Area and switch to your merchant account.
- Go to Developers > Additional data.
- Select the Raw acquirer result checkbox.
- Select Save configuration.
When a payment request is declined, the additionalData of the response now includes:
refusalReasonRaw: the full raw response. For example: 51 : Insufficient funds/over credit limit.refusalCodeRaw(only available for Visa and Mastercard transactions through our own acquiring platform): the numeric part of the raw response. For example: 51. This represents the underlying scenario that caused the transaction to fail.
Note that we would map the raw response from this example to refusalReason Not enough balance and resultCode Refused.
Visa and Mastercard raw responses
These are the most common raw responses from Visa and Mastercard for refused or canceled transactions.
If you use your own retry logic, you can use the raw response to help avoid Visa excessive retry fees. See Mapping to Visa system integrity fee categories.
| Journal type | refusalReasonRaw | Description |
|---|---|---|
| Cancelled | 00: Approved or completed successfully | The transaction was canceled after being initially approved by the issuer. This can be due to various reasons, for example, if the shopper returns goods after purchase. |
| Refused | 01: Refer to card issuer | The transaction was refused by the card issuer. The shopper should contact their bank for clarification. The shopper can try again after resolving the issue with their bank, or use another payment method. |
| Refused | 03: Invalid merchant | The transaction was refused by the card issuer. The shopper should contact their bank for clarification. The shopper can try again after resolving the issue with their bank, or use another payment method. |
| Refused | 04: Pickup card | The card issuer requests to retain the card. This can be due to a suspected counterfeit or stolen card. This reason is used in an ecommerce environment although it originates from an in-person payments environment. |
| Refused | 05: Do not honor | This is a generic refusal that has several possible causes. The shopper should contact their issuing bank for clarification. |
| Error | 06: Error | Payment could not be authorised and resulted in an error. The shopper can try again or use another payment method. |
| Refused | 07: Pickup card, special conditions | The card issuer requests to retain the card. This can be due to a suspected counterfeit or stolen card. |
| Cancelled | 10: Partial approval | The transaction was canceled. Some card issuers support partial-approval authorization. This approves a part of the requested transaction, leaving the remainder to be paid with another form of tender. |
| Refused | 12: Invalid transaction | The card issuer does not allow this type of transaction on this card/account. For example, the card is a fleet card for which this type of transaction is not permitted. |
| Refused | 13: Invalid amount | The card issuer has declined the transaction because of an invalid format or field. This response usually occurs with Cirrus or Maestro Debit and Prepaid Cards or cards that are not allowed to do online purchases. The shopper should try again or use another payment method. |
| Refused | 14: Invalid Account Number (No such Number) | The card issuer is unable to validate the card/account number. |
| Refused | 15: No such issuer | The card number is not within a card number range supported by the scheme. |
| Refused | 19: Re-enter transaction | Applies for Visa. The transaction cannot be processed temporarily. |
| Error | 30: Format error | The card issuer does not recognize the transaction details being entered. This is due to a format error. The shopper should check the transaction information and try again. |
| Refused | 41: Pickup card (lost card) | The card was reported as lost. Validate the shopper's authenticity and refer them to their bank. |
| Refused | 43: Pickup card (stolen card) | The card was reported as stolen. Validate the shopper's authenticity and refer them to their bank. |
| Refused | 46: Closed Account | Applies for Visa. The account is closed. Re-validate the account number for accuracy and do not reattempt with the same PAN or token. |
| Refused | 51: Insufficient funds/over credit limit / Not sufficient funds | Insufficient funds in the cardholder's account. The shopper can try again after adding funds to their bank account, or use another payment method. |
| Refused | 54: Expired card | The card expiration date is in the past. The shopper should correct the date or use another payment method. |
| Refused | 55: Invalid PIN | The shopper has entered an incorrect PIN. The shopper should re-enter their PIN or use another payment method. |
| Refused | 57: Transaction not permitted to cardholder | The card issuer does not permit the transaction on this card/account. The shopper can use another payment method. For activation or loading of prepaid cards, the Merchant, acquirer BIN, and issuer BIN are not all domestic. An issuer's processing center is not certified to receive transaction-specific data in TLV format (field 104 in request message). |
| Refused | 58: Transaction not permitted to acquirer/terminal | Card issuer does not permit the transaction on this card/account. Shopper can use another payment method or contact their bank. |
| Refused | 59: Suspected fraud | The transaction is refused because the card issuer suspects this payment to be fraudulent. |
| Refused | 61: Exceeds withdrawal amount limit(s) / Withdrawal amount limit exceeded | The shopper has exceeded their card limit. The shopper can try again after resolving the issue with their bank, or use another payment method. |
| Refused | 62: Restricted card | The card issuer has restricted where the card can be used. For example, because of embargoes. |
| Refused | 63: Security violation | The card issuer indicated a security issue with this card. The shopper can use another payment method. Alternatively, the shopper can try again after they resolved the issue with their bank. |
| Refused | 65: Exceeds withdrawal count limit / Withdrawal count limit exceeded | The shopper has exceeded their card usage frequency limit. The shopper can use another payment method or try again with the same card after the shopper took care of the card limit issue. |
| Refused | 6P: Customer ID verification failed | Applies for Visa. Incorrect account verification (for example driving license number) related to Visa Direct. Not to be confused for cardholder verification method refusals such as CVV, for example. |
| Refused | 65: Authentication required | Applies for Mastercard. Authentication is required for the transaction. If the transaction is in scope of PSD2 and did not go through 3D Secure, try again with 3D Secure. This is also referred to as a "Soft Decline". |
| Refused | 70: Contact Card Issuer | Applies for Mastercard. The card issuer indicated an issue with this card and requests contact from the shopper. The shopper can use another payment method. Alternatively the shopper can try again after they resolved the issue with their bank. |
| Refused | 70: PIN data required | Applies for Visa. The card issuer requests to use Secure Customer Authentication. Reattempt transaction with PIN. (European Region Only) |
| Refused | 75: Allowable number of PIN tries exceeded | The shopper has entered an incorrect PIN more times than is allowed by the issuing bank. The shopper should try again or use another payment method. |
| Refused | 78: Invalid/nonexistent account specified (general) | The transaction is from a new cardholder, and the card has not been properly unblocked. |
| Refused | 79: Life Cycle | Applies for Mastercard. The transaction is refused due to invalid card data. View the Merchant Advice Code for follow-up action. |
| Refused | 80: Credit issuer unavailable | The issuing bank cannot be contacted. The shopper should try again or use another payment method. |
| Refused | 82: Policy | Applies for Mastercard. The transaction is refused due to a policy reason. View the Merchant Advice Code for follow-up action. |
| Refused | 82: Negative online CAM, dCVV, iCVV, CVV, or CAVV results or Offline PIN authentication interrupted | Applies for Visa. The cardholder verification method failed for CAM, dCVV, iCVV, CVV or a service code for card present transactions. |
| Refused | 83: Fraud / Security | Applies for Mastercard. The transaction is refused because the card issuer suspects this payment to be fraudulent. View the Merchant Advice Code for follow-up action. |
| Authorised | 85: No reason to decline a request for account number verification, address verification, CVV2 verification, or a credit voucher or merchandise return | Zero-value auth request authorised. |
| Authorised | 85: Not declined (Valid for all zero amount transactions) | Zero-value auth request authorised. |
| Refused | 86: Cannot verify PIN | Applies for Visa. The PIN cannot be validated. If applicable, the transaction can be reattempted as a non-PIN transaction. |
| Refused | 91: Authorization Platform or issuer system inoperative / Issuer not available | The issuing bank cannot be contacted. The shopper should try again or use another payment method. |
| Error | 91: Issuer unavailable or switch inoperative | The issuer or issuer processor cannot authorize, for example because of downtime. |
| Refused | 92: Destination cannot be found for routing / Unable to route transaction | The shopper is using a test card number on live. The shopper should use another payment method. |
| Refused | 93: Transaction cannot be completed; violation of law | The issuing bank will not allow this transaction. The shopper should use another payment method. |
| Refused | 96: System malfunction | The issuing bank cannot be contacted. The shopper should try again or use another payment method. |
| Refused | 1A: Authentication Required | Applies for Visa. Authentication is required for the transaction. If the transaction is in scope of PSD2 and did not go through 3D Secure, try again with 3D Secure. This is also referred to as a "Soft Decline". |
| Refused | R0: Stop payment order | Applies for Visa. The cardholder requested to stop a specific, single recurring payment transaction. Contact the shopper regarding cancellation of this transaction. |
| Refused | R1: Revocation of authorization order | Applies for Visa. The cardholder requested to stop all recurring payment transactions. Contact the shopper regarding cancellation of all transactions. |
| Refused | R3: Revocation of all authorization | Applies for Visa. All recurring payments have been canceled for the card number in the request. Contact the shopper regarding cancellation of all transactions. |
| Refused | Z1: Offline-declined | Applies for Visa. Only used in non-cardholder requests such as advice. |
| Refused | Z3: Unable to go online; offline-declined | Applies for Visa. Only used in non-cardholder requests such as advice. |
| Error | N3: Cash service not available | Reserved for private use or Maximum online refund reached |
| Error | N4: Cash request exceeds issuer limit | Reserved for private use or Maximum offline refund reached |
| Declined | N7: Decline for CVV2 failure | Reserved for private use or Customer selected negative file reason |
Adyen for Platforms raw responses
Besides the issuer or card scheme, Adyen can also refuse a transaction if it fails a validation check in your balance platform.
| Journal type | refusalReasonRaw | Description |
|---|---|---|
| Refused | 010: Insufficient funds in the source balance account | The transaction was refused by Adyen because there are insufficient funds in the balance account. |
| Refused | 100 : Account holder misses required capabilities | The transaction was refused by Adyen because the account holder does not have the required capabilities. |
| Refused | 101 : Account holder is not active | The transaction was refused by Adyen because the account holder is not in active status. |
| Refused | 111 : Balance account is not active | The transaction was refused by Adyen because the balance account is not in active status. |
| Refused | 121: Balance platform is not active | The transaction was refused by Adyen because your balance platform is not in Active status. |
| Error | 999: Unknown error | The transaction was refused by Adyen for unknown reasons. |
Afterpay raw responses
| Journal type | Raw Acquirer Response | Description |
|---|---|---|
| Refused | DECLINED : Payment rejected (402) | Afterpay declined the payment. |
| Error | No response from ACM | Afterpay did not respond within 30 seconds which resulted in a timeout. |
| Error | 500: Internal Error | AfterPay had an internal error. The shopper needs to try again later. |
| Refused | INVALID_AMOUNT | The transaction amount is above or below the limit for Afterpay. |
Alipay raw responses
| Journal type | Response | Description |
|---|---|---|
| sentForSettle / SettledScheduled / settledExternally | trade_status=TRADE_FINISHED | The payment was successfully completed and you can expect to receive the funds. |
| Refused | Field 'currency' is not valid. Reason: The provided currency is not supported. | The currency sent in the request does not match the country code. For example, sending EUR for Norway; the currency should be NOK. See supported currencies at adyen.com. |
| Refused | Payment details are not supported for this combination of country/region and MCC | The acquirer's risk rules blocked this transaction. There is usually a non-compliance issue in the payment details. |
| Refused | 422: Invalid shopper interaction | The payment request includes the wrong shopperInteraction. For example, an Ecommerce merchant account sent a request with shopperInteraction: POS.Contact our Support Team. |
| Refused | trade_status=WAIT_BUYER_PAY | The shopper did not authorise the payment. The authorised funds were refunded and the offer was closed because the Adyen terminal did not receive the authorisation notification. |
| Refused | Shopper cancelled during PIN entry | The shopper did not enter their PIN. |
| Refused | Merchant cancelled | For Alipay, this refusal only occurs for POS transactions. Usually, the merchant cancels the transaction before it completes, or refunds the transaction before it is captured. |
| Refused | (NOT_SUPPORT_PAYMENT_INST) | The shopper is using a version of Alipay Wallet that is not supported. Make sure that payment_inst is set to Alipay_HK, and prompt the shopper to use the correct wallet. |
| Refused | TRADE_NOT_EXIST | For online transactions, the shopper did not open the Alipay app from the payment URL, or did not log in to the Alipay website. For POS transactions, this refusal occurs when the merchant's MA Registration Number (RegNum) is missing. Contact our Support Team. |
| Error | SYSTEM_ERROR : Alipay system is currently not available, please try again later. | The Alipay system is currently not available. Ask the shopper to try again later. |
| Error | ILLEGAL_SIGN | There is a technical issue with your configuration. Contact Alipay Support. |
| Error | ACCESS_FORBIDDEN | There is a technical issue with your configuration. Contact our Support Team. |
| RefundFailed | MERCHANT_BALANCE_NOT_ENOUGH | There is a technical issue with the refund. Try again between 21:00–23:00 SGT. |
| RefundFailed | PURCHASE_TRADE_NOT_EXIST | The transaction you’re attempting to refund does not exist, or does not include a PSP reference. Check the request parameters to ensure you’re sending a referenced refund. |
| RefundFailed | ILLEGAL_ARGUMENT | The API request includes an incorrect parameter. Check your request parameters according to Alipay's API specification. |
| RefundFailed | RETURN_AMOUNT_EXCEED | The total refund amount exceeds the transaction amount. Check that the amount is correct. |
| RefundFailed | ISSUER_OR_SWITCH_INOPERATIVE | The issuer or issuer processor temporarily cannot authorize, usually because of downtime. Try again later. |
| RefundFailed | 40 : Requested function not supported | The card issuer declined the transaction. This is sometimes caused by the issuer placing a hold on the shopper's card. |
American Express raw responses
These are the most common raw responses from American Express for refused or canceled transactions.
| Journal type | refusalReasonRaw | Description |
|---|---|---|
| Cancelled | 000: Approved | The transaction was canceled after being initially approved by the issuer. This can be due to various reasons, for example, if the shopper returns goods after purchase. |
| Cancelled | 001: Approve with ID | The transaction was canceled after the issuer requested that identification be established through telephone contact between the acquiring center's authoriser and the merchant. |
| Cancelled | 002: Prepaid Card Partial Authorization | Transaction was canceled. Some card issuers support partial-approval authorization. This approves a part of the requested transaction, leaving the remainder to be paid with another form of tender. |
| Refused | 100: Deny | This is a generic refusal that can have several possible reasons. Shopper should contact their issuing bank for clarification. |
| Refused | 101: Expired Card / Invalid Expiration Date | The card expiration date is in the past. The shopper should correct the date or use another payment method. |
| Refused | 106: PIN tries exceeded | The shopper has entered an incorrect PIN more times than is allowed by the issuing bank. The shopper should try again or use another payment method. |
| Refused | 109: Invalid merchant | The transaction was refused by the card issuer. The shopper should contact their bank for clarification. The shopper can try again after resolving the issue with their bank, or use another payment method. |
| Refused | 110: Invalid amount | The transaction amount was specified in an invalid format. For example, an invalid character such as a dollar sign or a space was used. The shopper should correct or use another payment method. |
| Refused | 111: Invalid account | The card issuer is unable to validate the card/account number, possibly because an invalid character was used. |
| Refused | 115: Requested function not supported | The card issuer does not allow this type of transaction on this card/account. |
| Refused | 117: Incorrect PIN | The shopper entered an invalid PIN. The shopper should try again or use another payment method. |
| Refused | 119: Transaction not permitted to Cardmember | The card issuer doesn't permit the transaction on this card/account. The shopper can use another payment method. |
| Refused | 122: Invalid Keyed Printed Card Security Code (PCSC) | The card issuer indicated a security issue with this card. The shopper can use another payment method. Alternatively, the shopper can try again after they resolved the issue with their bank. |
| Refused | 125: Invalid Effective Date on Card | The card expiration date provided is not a valid date format. The shopper should correct or use another payment method. |
| Refused | 130: Additional customer identification required | Authentication is required for the transaction. If the transaction is in scope of PSD2 and did not go through 3D Secure, try again with 3D Secure. This is also referred to as a "Soft Decline". |
| Refused | 181: Format error | The card issuer does not recognize the transaction details being entered. This is due to a format error. The shopper should check the transaction information and try again. |
| Refused | 183: Invalid Currency Code | The currency code provided doesn't comply with standards. |
| Refused | 187: Deny New Card Issued | The card issuer supplied the cardholder with a new card. The shopper should try again with the new card, or use another payment method |
| Refused | 189: Deny Canceled or Closed Card Acceptor | The merchant has stopped operations or is no longer accepting cards from this card scheme. |
| Refused | 200: Deny pick up Card | The card issuer requests to retain the card. This can be due to a suspected counterfeit or stolen card. |
| Refused | 900: Advice accepted | The ExpressPay issuer is unable to respond to an ATC Synchronization Authorization Request. |
| Refused | 911: Card Issuer timed out | The issuing bank cannot be contacted. The shopper should try again or use another payment method. |
| Refused | 912: Host unavailable | The issuing bank cannot be contacted. The shopper should try again or use another payment method. |
BLIK raw responses
| Journal type | Response | Description |
|---|---|---|
| Refused | ER_WRONG_TICKET | The BLIK code did not match any code generated within the last 180 seconds. Ask the shopper to try again and to check that they are using a valid code. |
| Refused | ER_TIC_USED | The BLIK code was already used within the last 180 seconds. |
| Refused | ER_TIC_EXPIRED | The BLIK code has expired. |
| Refused | TIMEOUT | Timeout in communication with the mobile banking app or the issuer’s system. |
| Refused | USER_TIMEOUT | The shopper did not confirm the transaction in the mobile banking app within the time limit. |
| Refused | LIMIT_EXCEEDED | The shopper’s transaction limit is exceeded. The banking mobile app should direct the shopper to change the limit. |
| Refused | USER_DECLINED | The shopper declined the transaction in the mobile app. |
| Refused | AM_TIMEOUT | Timeout in communication with the mobile app. |
| Refused | INSUFFICIENT_FUNDS | Insufficient funds in the shopper’s bank account. The mobile app should display the reason and direct the shopper to change the limit. |
| Error | NO_RESPONSE_WITHIN_TIMEOUT | Adyen did not receive a response from BLIK within the time limit. |
Grabpay raw responses
| Journal type | Response | Description |
|---|---|---|
| Canceled | consent_required : Shopper Canceled the payment before completion | The shopper’s wallet only contains SGD currency, but is trying to pay in MYR. Grabpay cancels the transaction and prompts the shopper to top up their wallet. |
| Refused | insufficient_balance : Shopper insufficient balance in wallet | The shopper did not have the funds to cover this transaction. Ask the shopper to top up their wallet or try another payment method. |
| Refused | confirm_failed : Customer Limits Exceeded/KYC check failed | The shopper has exceeded the balance limits of their wallet. Grabpay imposes lower limits on "basic users" who have not completed the KYC of their wallet. |
| Refused | server_error : GrabPay Server Error | Generic error returned by GrabPay during the redirect If you do not have a direct contract with Adyen, contact GrabPay directly. If you have a direct contract with Adyen, contact our Support Team. |
| Error | "{""devMessage"":""Bad Input."",""arg"":""Missing value for item0Price\n""}" | You did not specify the item price for the invoice line item. The value for amountIncludingTax must be greater than 0. |
| Refused | Customer has not completed KYC of wallet | The shopper's GrabPay wallet was not activated (not KYC-ed or no has balance), or the shopper attempted to bind their card or bank account to their wallet but was unsuccessful. |
| Refused | invalid_request : GrabPay Server Error | Adyen couldn’t establish a connection to GrabPay to either send the request or receive a response. Retry the payment request. If the issue continues, contact our Support Team. |
| Error | CONVERTER_RESPONSE | Adyen couldn’t interpret the acquirer’s response. Retry the payment request. If the issue continues, contact our Support Team. |
| Error | NO_RESPONSE_WITHIN_TIMEOUT | The acquirer did not return a response within the 30 seconds time limit. Retry the payment request. If the issue continues, contact our Support Team. |
| Refused | Customer has not completed initial top up of wallet | There are no funds in the shopper's wallet. Ask the shopper to top up their wallet. |
| Refused | kyc_compliance_decline : kyc_compliance_decline | The shopper hasn’t completed the KYC verification process. Ask the shopper to complete the KYC process to activate their wallet, and to try the payment again. |
| RefundFailed | merchant_insufficient_balance | Your account balance is insufficient. This can happen if your funds have just been settled from GrabPay to Adyen. Processed additional volume with GrabPay and set up a reserve with Grabpay. |
| RefundFailed | pending_approval | The Grabpay system is processing modifications on the transaction. Wait for these modifications to complete, then try again. |
Japanese issuer error codes
Error codes from Japanese issuers often provide more insight than acquirer responses. When shoppers in Japan encounter a payment error, it is common for them to call their issuer to retry the transaction. When the issuer provides an error, the additionalData object in the payment response contains the following fields:
We recommend you show the domesticShopperAdvice from the API response on your checkout page in Japan. This text is in the Shopper advice column below.
The following are the most frequent error codes from domestic issuers.
| Refusal reason | Shopper advice | Explanation |
|---|---|---|
| G12: Card cannot be used (when credit card cannot be used) | カード発行会社にご連絡し、状況をご確認ください。もしくは別カードでお取引ください。 | The shopper's credit card cannot be used. Ask them to contact their card issuer to get approval. |
| G30: Suspension (if authorization of transaction is suspended) | カード発行会社にて取引の判定を保留しています。カード発行会社にご連絡ください。 | The authorization for the transaction is suspended. Ask the shopper to inform their card issuer that they have received a G30 error. |
| G42: PIN error (incorrect PIN entered) | PINが誤っています。再度入力ください。 | The shopper entered their PIN incorrectly. Ask them to enter the correct PIN. |
| G44: Transaction Data Error | 正しいお支払い情報をご入力ください。 | Please re-enter your payment details. |
| G45: Transaction Data Error | 正しいお支払い情報をご入力ください。 | Please re-enter your payment details. |
| G54: Card used too many times (either in 1 day or when max amount is exceeded) | カード発行会社にご連絡し、状況をご確認ください。もしくは別カードでお取引ください。 | The card's usage limit has been exceeded. Ask the shopper to use a different card. |
| G55: Max amount exceeded (when single day max amount is exceeded) | クレジットカードの場合はカード発行会社にご確認ください。デビットカード・プリペイドカードの場合は残高をご確認ください。 | The card's credit limit has been exceeded. Ask the shopper to use a different card or contact their card issuer. If it is a debit card, ask them to check their account balance. |
| G56: Transaction Data Error | 正しいお支払い情報をご入力ください。 | Please re-enter your payment details. |
| G60: Transaction Data Error | 正しいお支払い情報をご入力ください。 | Please re-enter your payment details. |
| G83: Transaction Data Error | 正しいお支払い情報をご入力ください。 | Please re-enter your payment details. |
KCP raw responses
| Journal type | Response | Description |
|---|---|---|
| Refused | CC10 : Insufficient funds in the account (CC10 : Etc error) | The shopper doesn’t have enough funds to complete the transaction. Ask the shopper to top up their account and try again. |
| Refused | CC61 : The card holder has exceeded his or her credit limit (CC61 : Etc error) | The shopper has exceeded their credit limit. Ask the shopper to contact their bank if they want to increase the limit. |
| Refused | CC45 : Suspended credit card. (CC45 : Etc error) | The shopper’s card is suspended. Ask the shopper to contact their bank for further information. |
| Refused | CC63 : Password is not correct. (CC63 : Etc error) | The shopper has entered an incorrect password. |
| Refused | CC66 : Error in the social security number. (CC66 : Etc error) | The shopper entered the wrong social security number. Ask the shopper to try again with the correct number. |
| Refused | CC04 : Lost or invalid card. (CC04 : Etc error) | Ask the shopper to contact their bank. |
| Refused | CC54 : The expiry date has passed, or the date does not match. (CC54 : Etc error) | The shopper's card is expired. |
| Refused | CC55 : Error in the expiry date of the credit card. (CC55 : Etc error) | The shopper entered the wrong expiry date. Ask the shopper to try again with the correct expiry date. |
| Refused | CC69 : The transaction has been suspended since the wrong PIN is entered more than three (CC69 : Etc error) | The shopper entered the wrong PIN more than three times. Ask the shopper to contact their bank to resolve. |
| Refused | CC01 : Please contact the card issuer for further assistance. (CC01 : Etc error) | A technical issue occurred with the shopper’s card. Ask the shopper to contact their bank. |
| Error | CC03 : This error will occur when the status of the card used is invalid. (CC03 : Etc error) | The shopper's card is not active. Ask the shopper to confirm that they activated the card. |
| Refused | 8130 : The merchant does not accept credit cards issued outside of Korea. (8130 : Etc error) | KCP only processes Korean local cards. Ask the shopper to try again using a card issued in Korea. |
Klarna raw responses
These are the most common raw acquirer responses from Klarna for successful, refused, failed or cancelled transactions.
| Last journal type | Raw acquirer response | Description |
|---|---|---|
| PENDING | This is an expected response for Klarna Widget integrations. | |
| Authorised | ACCEPTED | The payment was authorised. |
| Error | Internal error | Generic API response from Klarna. Check your Customer Area for additional information. |
| Error | BAD_VALUE : locale | The locale in your payment request is not compatible. Refer to our Klarna documentation for compatible combinations. |
| Error | BAD_VALUE : order_lines[X].tax_rate | Error message on the validation criteria for the tax calculation. Refer to our Klarna documentation for more information about the tax calculation. |
| Error | BAD_VALUE : order_lines[X].total_tax_amount | There is an error in the tax amounts for order line [X]. Tax amounts should add up over all order lines. Klarna validates this on their end. Refer to our Klarna documentation to see how to send in tax amounts in your payment request. |
| Error | BAD_VALUE : order_tax_amount | There is an error in the tax amounts. Tax amounts should add up over all order lines. Klarna validates this on their end. Refer to our Klarna documentation to see how to send in tax amounts in your payment request. |
| Error | BAD_VALUE : purchase_currency | The amount.currency in your payment request not formatted correctly or doesn't apply for a certain locale. Refer to our Klarna documentation for compatible combinations. |
| Error | BAD_VALUE : billing_address.postal_code, shipping_address.postal_code or BAD_VALUE : shipping_address.postal_code, billing_address.postal_code | The postal code in the billingAddress or the deliveryAddress in your payment request is not formatted correctly. Refer to our Klarna documentation to see how to format the shopper's address. |
| Error | BAD_VALUE : attachment.attachment | The data sent in the additionalData.openinvoicedata.merchantData in your payment request does not follow Klarna's requirements. Refer to Klarna's documentation to see how to format the merchant data. |
| Error | BAD_VALUE : billing_address.phone, shipping_address.phone or BAD_VALUE : shipping_address.phone, billing_address.phone | The telephoneNumber in your payment request is not formatted correctly. Refer to our Klarna documentation to see how to format the telephone number. |
| Error | BAD_VALUE : billing_address.given_name, billing_address.family_name, or BAD_VALUE : shipping_address.given_name, shipping_address.family_name | Your request contains invalid characters. Make sure that you only submit UTF-8 encoded values when creating a Klarna payment. |
| Error | Payment method not available (contact Klarna) | The payment method defined in the payment request is not configured correctly on Klarna's end. Verify that you have enabled Klarna in your Customer Area. |
| Error | Allowed category list is empty | Edit your payment request. Your payment request does not follow the guidelines defined in our Klarna documentation. For example, make sure that the country code and billing address are for the same location. |
| Error | Missing returnUrl | Your payment request is missing the returnUrl parameter. |
| Error | No InvoiceLines provided | Your payment request did not include invoice lines. Refer to our Klarna documentation to see how to send in invoice lines in your payment request. |
| OfferCancelled | NOT_FOUND : Invalid session id | The shopper has tried to make a payment for an offer that has expired. We recommend that you ask the shopper to retry the transaction. |
| Not linked to a payment status, check logs. | ReadSessionResponse does not have valid authorisation token | Klarna sends this error when:
|
| Refused | REFUSED | Klarna's internal risk engine refused the payment. A possible reason is that the shopper has an unpaid balance towards Klarna. |
| Refused | UNAVAILABLE_PAYMENT_METHOD or PAYMENT_METHOD_FAILED : Purchase for payment method failed | Klarna's internal risk engine refused the payment. A possible reason is that the shopper has an unpaid balance towards Klarna. |
Mastercard Merchant Advice Codes
The Merchant Advice Code (MAC) can be returned by Mastercard issuers for both approved and refused payments. This code provides additional information about the type of transaction or the reason why the payment failed. If the payment failed, the MAC gives guidance on if and when the payment can be retried. You receive the MAC in the
additionalData.merchantAdviceCode
of the payment response.
| merchantAdviceCode | Description | Recommended action |
|---|---|---|
| 01 : New account information available | There has been a change in the shopper's account information, for example a new expiry date for an expired card. | Get the updated card information. You can either use our Account Updater, or reach out directly to the shopper. |
| 02 : Cannot approve at this time, try again later | This can happen because of a credit limit, or insufficient funds on the card. | Try again the payment after 72 hours. |
| 03 : Do not try again | The account is closed, or the issuer suspects fraud. | Do not retry this payment. Retries can be subject to penalty fees by Mastercard. Consider reaching out directly to the shopper. |
| 04 : Token requirements not fulfilled for this token type | There is a technical issue with the payment. | Contact our Support Team. |
| 21 : Payment Cancellation | Shopper canceled the recurring agreement. | Do not retry this payment. Retries can be subject to penalty fees by Mastercard. |
| 24 : Retry after 1 hour | Insufficient funds. | Retry the payment after 1 hour. |
| 25 : Retry after 24 hours | Insufficient funds. | Retry the payment after 24 hours. |
| 26 : Retry after 2 days | Insufficient funds. | Retry the payment after 2 days. |
| 27 : Retry after 4 days | Insufficient funds. | Retry the payment after 4 days. |
| 28 : Retry after 6 days | Insufficient funds. | Retry the payment after 6 days. |
| 29 : Retry after 8 days | Insufficient funds. | Retry the payment after 8 days. |
| 30 : Retry after 10 days | Insufficient funds. | Retry the payment after 10 days. |
| 40 : Consumer non-reloadable prepaid card | Issuer recognizes a consumer non-reloadable prepaid card was used for this transaction. | No action required. |
| 41 : Consumer single-use virtual card number | Issuer recognized a consumer single-use virtual card was used for this transaction. | No action required. |
| 42 : Score Exceeds Applicable Threshold Value | Mastercard refused this transaction due to a sanctions match. | No action required. |
| 43: Consumer multi-use virtual card number | Transaction was carried out with a consumer multi-use virtual card number. | No action required. |
| MerchantAdviceCode unknown | The issuer has returned a value that is not included in the Mastercard specifications. | No action possible. |
MB WAY raw responses
| Journal type | Response | Description |
|---|---|---|
| Refused | c5: Refused/Recusado | The payment was not completed or refused in the app. |
| Refused | ERROR - 102/203: Unknown phone number | The phone number provided by the shopper is unknown. |
| Error | No response from ACM | The connection to MB WAY timed out before Adyen received a response. |
| Refused | c2: Customer declined payment - Recusado | The shopper refused the payment in the app. |
| Refused | c4: Operation rejected | The shopper should contact their bank for further information. |
| Refused | Vp3: Limit exceeded | The shopper has exceeded the maximum daily amount. |
Mexico raw responses
These are the raw responses for refused or canceled domestics transactions in Mexico.
| Journal type | refusalReasonRaw | Description |
|---|---|---|
| Approved | 00 : APPROVED | Approved or completed successfully |
| Referral | 01 : REFERRAL | Function not available‚ Refer to card issuer |
| Referral | 02 : REFERRAL | Refer to card issuer‚ special conditions |
| Declined | 03 : DECLINED | Invalid merchant or terminal |
| Block card | 04 : BLOCK_CARD | Pick-up card |
| Declined | 05 : DECLINED | Do not honor |
| Declined | 06 : DECLINED | Decline from the issuer |
| Block card | 07 : BLOCK_CARD | Capture card, special conditions (bad debt) |
| Block card | 09 : BLOCK_CARD | Request in progress (duplicate) |
| Partially approved | 10 : PARTIALLY_APPROVED | Partial Approval |
| Approved | 11 : APPROVED | Approved (VIP) |
| Declined | 12 : DECLINED | Invalid transaction |
| Invalid amount | 13 : INVALID_AMOUNT | Invalid amount |
| Invalid card | 14 : INVALID_CARD | Invalid card number (no such number) |
| Invalid card | 15 : INVALID_CARD | Cardholder not on file (no such issuer) |
| PIN required | 1A : PIN_REQUIRED | PIN data required |
| Error | 30 : ERROR | Format error |
| Error | 31 : ERROR | Bank not supported by switch |
| Card expired | 33 : CARD_EXPIRED | Expired card, capture |
| Issuer suspected fraud | 34 : ISSUER_SUSPECTED_FRAUD | Suspected fraud, capture |
| Error | 35 : ERROR | Card acceptor contact acquirer |
| Restricted card | 36 : RESTRICTED_CARD | Restricted card |
| Error | 37 : ERROR | Card acceptor call acquirer security |
| PIN tries exceeded | 38 : PIN_TRIES_EXCEEDED | Allowable PIN tries exceeded, capture |
| Not supported | 39 : NOT_SUPPORTED | No credit account |
| Block card | 41 : BLOCK_CARD | Lost card |
| Block card | 43 : BLOCK_CARD | Stolen card, capture |
| Not enough balance | 51 : NOT_ENOUGH_BALANCE | Insufficient funds |
| Card expired | 54 : CARD_EXPIRED | Expired card |
| Invalid PIN | 55 : INVALID_PIN | Incorrect PIN |
| Invalid card | 56 : INVALID_CARD | No card record |
| Transaction not permitted | 57 : TRANSACTION_NOT_PERMITTED | Transaction not permitted to cardholder |
| Transaction not permitted | 58 : TRANSACTION_NOT_PERMITTED | Transaction not permitted to terminal |
| Withdrawal amount exceeded | 61 : WITHDRAWAL_AMOUNT_EXCEEDED | Exceeds withdrawal amount limit |
| Restricted card | 62 : RESTRICTED_CARD | Restricted card |
| Withdrawal count exceeded | 65 : WITHDRAWAL_COUNT_EXCEEDED | Exceeds withdrawal frequency limit |
| Issuer unavailable | 68 : ISSUER_UNAVAILABLE | Response not arrived or received too late |
| Error | 70 : ERROR | Decryption error Track2 |
| Error | 71 : ERROR | Must initialize keys |
| Error | 72 : ERROR | Problem initializing Keys |
| Error | 73 : ERROR | CRC error |
| PIN tries exceeded | 75 : PIN_TRIES_EXCEEDED | Allowable number of PIN tries exceeded |
| Error | 76 : ERROR | Reserved for private use or Approved country club |
| Error | 77 : ERROR | Reserved for private use or Approved pending identification (sign paper draft) |
| Error | 78 : ERROR | Reserved for private use or Approved blind |
| Error | 79 : ERROR | Reserved for private use or Approved administrative transaction |
| Error | 80 : ERROR | Reserved for private use or Approved national negative file hit OK |
| Error | 81 : ERROR | Reserved for private use or Approved commercial |
| Declined | 82 : DECLINED | Reserved for private use or No security module |
| Declined | 83 : DECLINED | Reserved for private use or No accounts |
| Error | 84 : ERROR | Reserved for private use or No PBF |
| Error | 85 : ERROR | Reserved for private use or PBF update error |
| Declined | 86 : DECLINED | Reserved for private use or Invalid authorization type |
| Declined | 87 : DECLINED | Reserved for private use or Bad Track Data |
| Error | 88 : ERROR | Reserved for private use or PTLF error |
| Error | 89 : ERROR | Reserved for private use or Invalid route service |
| Error | 90 : ERROR | Cutoff in progress |
| Issuer unavailable | 91 : ISSUER_UNAVAILABLE | Issuer or switch is inoperative |
| Issuer unavailable | 92 : ISSUER_UNAVAILABLE | Financial institution or intermediate network unknown for routing |
| Declined | 94 : DECLINED | Duplication transaction |
| Issuer unavailable | 96 : ISSUER_UNAVAILABLE | System malfunction |
| Declined | N0 : DECLINED | Reserved for private use or Unable to authorize |
| Error | N1 : ERROR | Reserved for private use or Invalid PAN length |
| Declined | N2 : DECLINED | Reserved for private use or Preauthorization full |
| Error | N5 : ERROR | Reserved for private use or Maximum credit per refund |
| Error | N6 : ERROR | Reserved for private use or Maximum refund credit reached |
| Error | N8 : ERROR | Reserved for private use or Over floor limit |
| Error | N9 : ERROR | Reserved for private use or Maximum number refund credits |
| Error | O0 : ERROR | Reserved for private use or Referral file full |
| Error | O1 : ERROR | Reserved for private use or NEG file problem |
| Error | O2 : ERROR | Reserved for private use or Advance less than minimum |
| Error | O3 : ERROR | Reserved for private use or Delinquent |
| Error | O4 : ERROR | Reserved for private use or Over limit table |
| Error | O5 : ERROR | Reserved for private use or PIN required |
| Error | O6 : ERROR | Reserved for private use or Mod 10 check |
| Error | O7 : ERROR | Reserved for private use or Force post |
| Error | O8 : ERROR | Reserved for private use or Bad PBF |
| Error | O9 : ERROR | Reserved for private use or NEG file problem |
| Error | P0 : ERROR | Reserved for private use or CAF problem |
| Declined | P1 : DECLINED | Reserved for private use or Over daily limit |
| Error | P2 : ERROR | Reserved for private use or CAPF not found |
| Error | P3 : ERROR | Reserved for private use or Advance less than minimum |
| Error | P4 : ERROR | Reserved for private use or Number of times used |
| Error | P5 : ERROR | Reserved for private use or Delinquent |
| Error | P6 : ERROR | Reserved for private use or Over limit table |
| Error | P7 : ERROR | Reserved for private use or Advance less than minimum |
| Error | P8 : ERROR | Reserved for private use or Administrative card needed |
| Error | P9 : ERROR | Reserved for private use or Enter lesser amount |
| Error | Q0 : ERROR | Reserved for private use or Invalid transaction date |
| Declined | Q1 : DECLINED | Reserved for private use or Invalid expiration date |
| Declined | Q2 : DECLINED | Reserved for private use or Invalid transaction code |
| Error | Q3 : ERROR | Reserved for private use or Advance less than minimum |
| Error | Q4 : ERROR | Reserved for private use or Number of times used |
| Error | Q5 : ERROR | Reserved for private use or Delinquent |
| Error | Q6 : ERROR | Reserved for private use or Over limit table |
| Error | Q7 : ERROR | Reserved for private use or Amount over maximum |
| Error | Q8 : ERROR | Reserved for private use or Administrative card not found |
| Error | Q9 : ERROR | Reserved for private use or Administrative card not allowed |
| Error | R0 : ERROR | Reserved for private use or Approved administrative request performed in window |
| Error | R1 : ERROR | Reserved for private use or Approved administrative request performed out of window |
| Error | R2 : ERROR | Reserved for private use or Approved administrative request performed anytime |
| Error | R3 : ERROR | Reserved for private use or Chargeback, customer file updated |
| Error | R4 : ERROR | Reserved for private use or Chargeback, customer file updated, acquirer not found |
| Error | R5 : ERROR | Reserved for private use or Chargeback, incorrect prefix number |
| Error | R6 : ERROR | Reserved for private use or Chargeback, incorrect response code or CPF configuration |
| Error | R7 : ERROR | Reserved for private use or Administrative transactions not supported |
| Error | R8 : ERROR | Reserved for private use or Card on national negative file |
| Error | S4 : ERROR | PTLF full |
| Error | S5 : ERROR | Reserved for private use or Chargeback approved, customer file not updated |
| Error | S6 : ERROR | Reserved for private use or Chargeback approved, customer file not updated, acquirer not found |
| Error | S7 : ERROR | Reserved for private use or Chargeback accepted, incorrect destination |
| Error | S8 : ERROR | Reserved for private use or ADMN file problem |
| Error | S9 : ERROR | Reserved for private use or Unable to validate PIN; security module is down |
| Error | T1 : ERROR | Reserved for private use or Invalid credit card advance amount |
| Error | T2 : ERROR | Reserved for private use or Invalid transaction date |
| Error | T3 : ERROR | Reserved for private use or Card not supported |
| Error | T4 : ERROR | Reserved for private use or Amount over maximum |
| Declined | T5 : DECLINED | Reserved for private use or CAF status = 0 or 9 |
| Error | T6 : ERROR | Reserved for private use or Bad UAF |
| Error | T7 : ERROR | Reserved for private use or Cash back exceeds daily limit |
| Error | T8 : ERROR | Reserved for private use or Invalid account |
Oney raw responses
| Journal type | Response | Description |
|---|---|---|
| Refused | La demande de paiement a été refusée | Oney declined the payment. |
| Error | ERR_03 : L'email n'est pas compatible avec la regex définie en base. - email_address | The email address failed Oney’s validation. Ask the shopper to try again with another email address. |
| Error | 504 : Gateway Timeout | The payment failed because of a timeout. Ask the shopper to try again later. |
| Error | ERR_04 : Le pays de livraison/facturation n'est pas accepté - customer.customer_address | The shipping or billing address is not accepted. Check that the address is correct and matches the country/region. |
| Error | ERR_04 : Le pays de livraison/facturation n'est pas accepté - purchase.delivery.delivery | The delivery address is not accepted. Check that the delivery address is correct. |
| Error | ERR_03 : Le format du champ est invalide | The phone number format is not valid. The expected format for France is: +336 or +337 followed by eight digits. The expected format for Spain is +346 or +347 followed by eight digits. |
| Error | ERR_03 : Invalid Business_transaction. | You don’t have permission to do this type of transaction. Contact our Support Team. |
| Error | ERR_05 : Les bornes d'une OPC sont dépassées - payment.payment_amount | The transaction amount is above/below the required limits for Oney. |
Online banking Czech Republic raw responses
| Last journal type | refusalReasonRaw | Description |
|---|---|---|
| Refused | provider_error: Something went wrong on the provider's side. | Transaction is rejected by the bank (refusal to authorize the transaction). The shopper should contact their bank to clarify the reason for the transaction's rejection. |
| Error | No response from ACM | PayU did not respond within 30 seconds which resulted in a timeout. |
For a full list of responses, refer to PayU's documentation.
Online banking Slovakia raw responses
| Last journal type | refusalReasonRaw | Description |
|---|---|---|
| Refused | provider_error: Something went wrong on the provider's side. | Transaction is rejected by the bank (refusal to authorize the transaction). To clarify the reason for the rejection of the transaction, the shopper should contact their bank. |
| Error | No response from ACM | PayU did not respond within 30 seconds which resulted in a timeout. |
For a full list of responses, refer to PayU's documentation.
PayPal raw responses
These are the most common raw acquirer responses from PayPal for refused, failed, or canceled transactions.
| Journal type | refusalReasonRaw | Description |
|---|---|---|
| CaptureFailed | 10606 - Transaction rejected, please contact the buyer | The shopper cannot pay. For more information on why the capture failed, contact PayPal. |
| CaptureFailed | 11607 - Duplicate request | This transaction could not be completed since it is duplicate. Check whether the shopper already attempted a transaction. |
| Error | 10001: Internal Error | This indicates a technical issue on PayPal's side. For more information, contact PayPal. |
| Error | 10002 : The user account is locked | Your PayPal account may be locked. For more information, contact PayPal. |
| Error | 10002: Restricted account | PayPal merchant account has been restricted. Contact your PayPal account manager to resolve the issue. |
| Error | 10212: Profile preference setting | Applies to subscription payments. The shopper's PayPal account is configured to automatically block certain payments. The shopper can adjust this in their PayPal account. |
| Error | 10409: You're not authorized to access this info | There are multiple PayPal accounts set up on the same merchant account. |
| Error | 10525: Invalid Data | The transaction cannot be processed because the amount is zero. If you want to make a zero-auth transaction to validate payment details, make sure that you are sending the required parameters to save payment details. |
| Error | 10729: Shipping Address State Empty | For transactions in the US and Canada, the deliveryAddress has to include a stateOrProvince. |
| Error | 10730: Shipping Address Postal Code Empty | The deliveryAddress has to include a postalCode. |
| Error | 11451: Billing Agreement Id or transaction Id is not valid | The transaction failed because the token used for the recurring transaction was created from a different merchant account. Make sure to use the recurring details created on the same merchant account. |
| Error | 11452: Merchant not enabled for reference transactions | You tried to either create or use a token, but do not have the recurring feature enabled on your PayPal account. Contact PayPal to resolve the issue. |
| Error | 11547: Recurring payments feature is not currently available; try again later | You tried to either create or use a token, but do not have the recurring feature enabled on your PayPal account. Contact PayPal to resolve the issue. |
| Error | 11547: Permission denied | Your PayPal account does not have the required API permissions. For instructions, see Set up PayPal or Set up PayPal for marketplaces. If the problem persists, contact PayPal. |
| Error | 11601: Request for billing address failed | The Request billing address feature is not enabled on your PayPal account. Contact PayPal to have it enabled. |
| Refused/Error | XXXXX: Transaction refused because of an invalid argument. See additional error message | No specific reason provided. For more information, refer to PayPal's API Error Codes. |
| Refused | 10201: Agreement cancelled | The billing agreement of a recurring payment has been canceled on PayPal's side. You can either retry the payment with another token, or create a new token. |
| Refused | 10204: Denied | The shopper's PayPal account is closed or restricted. The shopper should contact PayPal to resolve the issue. |
| Refused | 13122: Transaction refused | This transaction cannot be completed because it violates the PayPal User Agreement. For more information, contact PayPal. |
| Refused | 10417: Transaction cannot complete | This payment failed. PayPal recommends that you ask the shopper to retry the payment using another payment method from their PayPal wallet. |
| Refused | 10486: This transaction could not be completed | The transaction failed due to a bad funding source; for example, the payment exceeded the shopper's card limit. |
| RefundFailed | 10002: You do not have permission to make this API call | Your PayPal does not have the required API permissions. See Set up PayPal or Set up PayPal for marketplaces If the problem persists, contact PayPal. |
| RefundFailed | 10007: Permission denied - You do not have permission to refund this transaction | This issue is related to the permissions you have on PayPal's side. For more information, refer to PayPal documentation. |
| RefundFailed | 10009: You do not have a verified ACH | You can receive this response in the following scenarios:
|
TWINT raw responses
| Journal type | Response | Description |
|---|---|---|
| Refused | 103: Declined by the issuer | The transaction was declined by the issuer. Ask the shopper to contact their bank for more information. |
| Refused | 1301/1302 Shopper removed the recurring agreement | The shopper has canceled their recurring payment. |
| Refused | 103:Payment aborted by the customer | The shopper did not complete the payment. |
| Error | No response from ACM | Adyen was not able to connect with TWINT, which resulted in a timeout. |