Processor specific error-codes
In this list, you will find the error-codes, that are returned by a specific processor, their explanation and, if possible, a recommended behavior in how to deal with them.
Do not parse these codes, or use them for any decision making.
While we strife to keep them up-to-date, especially 3rd party processors may change these responses and their meaning without further notice. Therefore, relying on these exact codes may cause issues in your application, should they change. Please always refer to the respective documentation of the processor, if possible.
Only log these responses on your end, so you have them as additional information.
This list is only for you to understand these responses and, if necessary, manually make decisions, after you have reviewed the responses, not to make automatic decisions in your code.
In order to code automatic behavior, please refer to the explanations in the Error Handling chapter.
Abbreviations
In order to keep the following lists sleek and clean, we'll use certain abbreviations, such as:
A
Acquirer/Processor
I
Issuer (The card holders bank etc.)
CIT
Customer-initiated transaction
MIT
Merchant-initiated transaction
3DS
3D Secure authentication process
VIS
MCC
Merchant Category Code. A code, that defines the merchants business (Airline, Hospitality etc.) and applies a set of rules, connected to that code.
*
Relevant for all payment schemes
EEA
European economic area
MAC
Merchant Advice Code (MC). Special code to indicate, that a certain action is needed.
ABU
Automatic Billing Updater (MC)
MSP
Multi-service platform
A2A
Account-to-account Payments (Bank transfer by Worldline)
Credit cards
These are the processor result codes, commonly used by credit card processors.
Error
Description
Scheme
Declined by
Additional Information
Merchant action
Payer hint
(1A) Soft decline, SCA required
Additional payer authentication required
*
A/I
The acquirer or issuer expects an additional 3DS authentication step to verify the payer's identity before a transaction can be completed. This is important to prevent fraud and confirm the payer as the legitimate cardholder. This additional step may include a one-time password (OTP) sent to the phone, a security question, or logging into a banking app.
Retry using 3DS authentication by creating a new alias or forcing challenge in a new CIT. Authentication may improve likelihood of an approval.
Retry with 3DS authentication
(03) Invalid merchant number
Merchant identification failed
*
A
This error indicates that either your merchant facility is non-functional or the merchant details are incorrect. This can happen if the merchant configuration on the acquirer side is in progress (not yet completed) or has been changed for some reason.
For DCC, this means that DCC is not possible for this terminal or merchant
Retry transaction later or use another means of payment
(04) Retain card
Card invalid
*
I
The card has been reported lost, stolen or involved in a fraud. This reason is used in an ecommerce environment, although it originates from an in-store business where it makes sense for the Issuer to request card retention
Do not retry. Block the card.
Call the bank or try using another means of payment
(05) Authorization declined
Do not honor. Authorization cannot be processed
*
A/PS/I
Indicates a general decline from the Issuing bank, Acquirer or payment scheme meaning the transaction was blocked due to an unspecified reason such as suspected fraud or other Acquirer-, Scheme- or Issuer-specific rules. Acquirer may send this code, if a declined transaction was repeated more than 4 times a day. In most cases, the bank rejects the payment due to the card being invalid or for security reasons.
Check the transaction, fix possible issues and retry. Check especially CIT and MIT flagging, and flows and don't mix them. Contact the cardholder if the issue persists.
Call the bank or try using another means of payment
(10) Partial approval
The transaction is approved for a lower amount than requested
I
The Issuer can approve a payment card transaction for a lower amount than requested, typically because the card's available credit is insufficient for the full purchase. Partial approval capability can be activated via API. Not all payment method support partial approval
Retry with a smaller amount or use another means of payment, if partial authorization is not accepted by the merchant
(12) Invalid transaction
Transaction content is not correct
*
A/PS/I
A transaction is declined because it is not allowed for the cardholder's account, the card details are incorrect, or there is a problem with the transaction data. For example, if the refund amount is too high. This can also happen if the Acquirer, Scheme or Issuer does not support the specific payment method, or if the system or terminal is not configured correctly. Acquirer can decline with this code, if the payment method (card brand) is not configured (correctly) for the Acquirer contract.
Do not retry with the same data. Verify card and transaction details, fix issues and retry. If all transactions of a payment method are declined with this code, contact your account manager and ask to check the Acquirer contract configuration
If the issue persists, after the merchant action has been performed:
Call the bank or try using another means of payment
(13) Invalid amount
Transaction amount is incorrect
*
A/I
The amount does not adhere to the restrictions for this action. E.g. it might be exceeding the allowed capture amount, pre-set limits, or it's too high or too low for the card or merchant.
Check the amount, adjust and retry. Especially for refunds, check the refund amount restrictions in the API.
Call the bank or try using another means of payment
(14) Invalid card
Authorization cannot be processed with this card
*
A/I
The payment card number entered for a transaction is incorrect, does not exist, or is otherwise not recognized by the Acquirer or the Issuing bank. This usually happens due to a typo, a wrong card being used, or an outdated or unissued card number.
For DCC, this means that DCC is not possible for this card, for example, if card currency is not supported for DCC.
Do not retry. Contact the payer to double-check the card details
Re-enter the card details, retry using another means of payment or contact the bank
(30) Format error
Transaction details invalid
*
A/PS/I
Indicates that the Acquirer, Scheme or card Issuer received transaction details that were not in the correct (expected) format. This could be missing required data, incorrectly structured information, transaction details that do not match, or other problems.
Do not retry with the same configuration. Check provided information, fix possible issues and try again. See examples of typical problems:
A CIT transaction in EEA (in PSD2 scope) was performed without 3D secure authentication
Transaction Initiator is set to "PAYER" in JSON API for an MIT transaction, falsely flagging it as CIT.
An MIT transaction is flagged as Recurring "Initial".
An MIT transaction is sent without a reference to the initial 3DS fully-authenticated transaction or alias.
Use another means of payment
(33) Card expired
Card expired
*
I
The transaction was declined because the payment card's expiration date has passed, or it was entered incorrectly.
Do not retry with the same expiry date. Contact the payer to double-check the card details. Update alias if it's tokenized.
Contact Saferpay to enable scheme tokenization if it was deactivated on merchant request in the past. Token expiry date will be updated automatically.
Check if new card has been received and retry using updated or another means of payment. Contact the Issuer for any question
(34) Suspicion of manipulation
Suspicious fraudulent card
*
I
The transaction is declined due to suspected card fraud.
Do not retry. Block the card.
Call the bank and block the card if necessary, try using another means of payment.
(40) Function not supported
Requested function not supported
*
A/I
The Acquirer or card Issuer can decline an authorization because the card or the account does not support that specific type of transaction, or the merchant is not configured to handle it. For example, a merchant attempting to process an unsupported transaction on the MCC level or the card not being allowed for mail-phone- or e-commerce internet orders
Do not retry. Check the merchant and terminal configuration. Contact payer to check the card.
Retry using another means of payment or check the card configuration with the bank or in the app.
(43) Stolen card
Card reported as stolen
*
I
The payment card used in a transaction has been reported as stolen to the Issuing bank, and the bank has flagged the card for fraud.
Do not retry. Block the card.
Call the bank or try using another means of payment.
(51) Insufficient funds
Not enough funds
*
I
The cardholder's account does not cover the transaction amount or the card limit for a certain period (day, month) has been reached.
Try again after 3–7 days. Do not retry more than 4 times a day. Contact the cardholder to verify payment details.
Call the bank to increase card limits, transfer funds from another account or use a different payment method.
(57) Transaction not permitted to cardholder
Requested function is not allowed for product or card type
*
I
The card issuer declines the transaction because the card has certain restrictions, such as certain merchants (MCCs), countries, or transaction types such as mail-phone order (MOTO) or e-commerce.
Do not retry with the same data. Contact the payer to double-check the card details.
Check card configuration, contact the bank to verify card restrictions.
(58) Transaction not permitted for the terminal
The terminal is unknown or cannot process the transaction type
*
A
The payment terminal is not authorized or configured to process the type of transaction being attempted, or the merchant account has restrictions that prevent it. This may be because the terminal does not support a particular card scheme, the payment provider is incorrectly configured, or there are merchant account restrictions for certain transaction types such as international sales or specific industries (MCCs).
Do not retry with the same data. Contact Acquirer or payment service provider to analyze the problem.
Use another means of payment.
(59) Suspected fraud
Transaction appears to be potentially fraudulent
*
A/I
The Acquirer or Issuer bank's fraud detection applications identify the transaction as suspicious and decline to protect against potential financial loss.
Do not retry. Contact Acquirer or payment service provider to analyze the problem.
Call the bank or try using another means of payment.
(61) Exceeds approval amount limit
Transaction amount exceeds the maximum amount set by the Issuer
*
I
Merchant or cardholder tries to make a purchase that is higher than the configured limit for a single transaction. This limit is usually set for security reasons and to control spending.
Do not retry on the same day and with the same data. Wait at least 1 day before reattempting. Do not retry more than 4 times a day. Contact the payer to double-check the card details. In agreement with the cardholder, the payment could be split.
Check card configuration, split payment or contact the bank to verify and increase payment limits.
(62) Restricted card
Card cannot be used for the transaction type
*
I
The card can only be used for certain transaction types, locations (geographic restrictions) or merchant MCCs
Do not retry with the same data. Contact the payer.
Call the bank to remove restrictions or try using another means of payment.
(64) The transaction amount of the referencing transaction is higher than the transaction amount of the original transaction
The transaction amount of the referencing transaction is higher than the transaction amount of the original transaction
*
A/I
This is usually an error with a return or refund amount, indicating that an incorrect or invalid amount is being processed for the transaction.
Check the amount and try again. Do not retry more than 4 times a day. Check if another refund authorization already references a purchase and cancel or capture it.
Call the bank to check the card settings and the rules for amount verification.
(66) Blocked, first use or special condition
The card is blocked, new account, first use or special condition
*
I
Indicates that the payment was declined due to a special condition set by the card Issuer, such as security concerns, an account restriction, or a transaction from a new cardholder who did not properly unlock the card.
Retry on the next day. Do not retry more than 4 times a day. Contact the payer to check card status.
Call the bank to check the card or try using another means of payment.
(67) Amount exceeds Issuer limit
Request exceeds Issuer limit
*
I
Means that the requested transaction amount exceeded the limits set by the card Issuer for the particular account. This can be a total purchase amount or the frequency of transactions that exceed a threshold.
Do not retry on the same day and with the same data. Wait at least 1 day before reattempting. Do not retry more than 4 times a day. Contact the payer or use the smaller amount.
Call the bank to increase card limits, transfer funds from another account or use a different payment method.
(68) Verification data failed
Card verification data is invalid
*
I
The card Issuer declined the transaction due to a problem with the card's verification data or security details, such as an incorrect CVV/CVC.
Do not retry, contact the cardholder.
Check the data, call the bank or try using another means of payment.
(78) Stop payment order
The cardholder requests that recurring payments be stopped
VIS
I
The transaction was declined because the cardholder requested that payment of a specific recurring or installment transaction be stopped.
Do not retry, contact the cardholder.
Inform the merchant.
(79) Revocation of the authorization order
The cardholder requests that all future recurring payments be stopped.
VIS
I
The transaction was declined because the cardholder requested that all recurring or installment transactions be suspended for a specific merchant account.
Do not retry, contact the cardholder.
Inform the merchant
(80) Amount no longer available
Amount or account number is incorrect
*
I
The transaction was declined because something is wrong. It is not necessarily insufficient funds, expired card or fraud. Essentially, the system flags a data entry error at the source of the transaction that must be corrected before the transaction can be successfully processed
Check the transaction data and retry. Do not retry more than 4 times a day.
Check the transaction data and retry.
(81) Message flow error
Issuer requested stand-in
*
A/I
Issuer is unavailable and requested stand-in. This may result in temporary approval from the Issuer, but a decline from the Acquirer because the risk of Issuer decline later is high.
Try again later
Try again later
(82) Policy - MAC 01
New account information is available. Update card data before re-attempting
MC
I
Updated information found to be available in MC ABU database - The payer has been issued a new card. Maybe the the card has been completely renewed and the current usage causes a policy violation.
Obtain new account information from the payer, before reattempting.
Check if new card has been received and retry using updated details or another means of payment. Contact the Issuer for any question.
(82) Policy - MAC 02
Issuer cannot approve at this time, try again later
MC
I
Issuer is currently not able to process this transaction.
Try again later. Do not retry more than 10-15 times a month with the same card and amount.
Try again later.
(82) Policy - MAC 03
Do not retry. Obtain another type of payment from the cardholder
MC
I
The payers account-data is no longer valid, but updated credentials were not found to be available in MC ABU database (Also see code 82 - MAC 01).
Do not retry. The Issuer will never approve. Penalty fees for reattempts will be charged.
Call the bank or try using another means of payment.
(83) Security - MAC 01
New account information is available. Update card data before re-attempting
MC
I
Account or card data was changed. Additional information is needed.
Retry using 3DS authentication by creating a new alias or forcing challenge in a new CIT. Authentication may improve likelihood of an approval
Retry with 3DS authentication, enter new card details correctly or call the bank.
(83) Security - MAC 02
Issuer cannot approve at this time, try again later
MC
I
Retry transaction later. Issuer cannot approve at this time due to a security issue.
Try again later. Do not retry more than 10-15 times a month with the same card and amount.
Try again later.
(83) Security - MAC 03
Do not retry. Obtain another type of payment from the cardholder
MC
I
The transaction was declined due to a fraud or security reason. The card Issuer flagged the transaction as suspicious, perhaps due to a security violation or if the card was reported lost or stolen. The specific underlying cause is determined by the card Issuer, but it generally indicates a security-related reason for the refusal.
Do not retry. Suspected Fraud. The Issuer will never approve. Penalty fees for reattempts will be charged.
Call the bank or try using another means of payment.
(84) Life cycle - MAC 01
New account information is available. Update card data before re-attempting
MC
I
Updated information found to be available in MC ABU database - The payer has been issued a new card. Maybe the the card has been completely renewed and the current usage causes a policy violation.
Obtain new account information from the payer, before reattempting.
Check if new card has been received and retry using updated or another means of payment. Contact the Issuer for any question
(84) Life cycle - MAC 02
Issuer cannot approve at this time, try again later
MC
I
Issuer is currently not able to process this transaction.
Try again later. Do not retry more than 10-15 times a month with the same card and amount.
Try again later.
(84) Life cycle - MAC 03
Do not retry. Obtain another type of payment from the cardholder
MC
I
The payers account-data is no longer valid, but updated credentials were not found to be available in MC ABU database (Also see code 84 - MAC 01).
Do not retry. The Issuer will never approve. Penalty fees for reattempts will be charged.
Call the bank or try using another means of payment.
(86) Exceeds frequency
The maximum allowed number of transactions has been exceeded.
*
I
The maximum allowed number of transactions within a certain period has been exceeded. A transaction is declined because the customer has made too many transactions in a certain period. It can also indicate that the credit limit has been exceeded.
Do not retry on the same day and with the same data. Wait at least 1 day before reattempting. Do not retry more than 4 times a day. Contact the payer to obtain another means of payment, if necessary.
Call the bank to increase card limits or use a different payment method.
(91) Card Issuer temporarily not reachable
Card Issuer couldn't be contacted in time to approve the transaction
*
A
Temporary issue, usually due to a timeout or application error on the Issuer or Acquirer side. The transaction can be retried after a few minutes.
Wait a few minutes and try again. Contact the Acquirer or payment service provider if the issue persists.
Wait a few minutes and try again. Contact the bank if the issue persists.
(92) The card type is not processed by the authorization center
Unable to route transaction
*
A/PS
Indicates a problem with the payment network or payment gateway that prevents the transaction from being sent to the correct card Issuer for approval. This can happen if the routing information from the card BIN is incorrect or if there is a system or network issue preventing the transaction from being forwarded.
Retry on the next day. Contact the Acquirer or payment service provider if the issue persists. Contact the payer to obtain another means of payment.
Try again later or another means of payment
BLIK
These are the response codes, that are returned by BLIK.
Decline reason
Description
Merchant action
Payer hint
(ER_WRONG_TICKET) Wrong BLIK code
Incorrect BLIK code was entered. The BLIK code did not match any code generated within the last 180 seconds. The transaction can be retried.
Ask the shopper to try again and to check that they are using a valid code.
Try again with a new, correct code.
(ER_TIC_EXPIRED) Expired BLIK code
The BLIK code has expired.
Ask the shopper to try again using a new, valid code.
Try again with a new, correct code.
(ER_TIC_STS) Cancelled BLIK code
The BLIK code was cancelled.
Ask the shopper to try again using a new, valid code.
Try again with a new, correct code.
(ER_TIC_USED) Used BLIK code
The BLIK code was already used within the last 180 seconds.
Ask the shopper to try again using a new, valid code.
Try again with a new, correct code.
(INSUFFICIENT_FUNDS) Insufficient funds
Insufficient funds in the shopper’s bank account. The mobile app should display the reason and instruct the buyer to change the limit.
Ask the shopper to retry using another bank account or a different payment method.
Check the reason in the banking application and try again.
(LIMIT_EXCEEDED) Exceeding the transaction limit
The shopper’s transaction limit is exceeded. The banking mobile app should display the reason and instruct the buyer to change the limit.
Ask the shopper to retry using another bank account or a different payment method.
Check the reason in the banking application and try again.
(ER_BAD_PIN) Rejection due to incorrect PIN
The PIN entered in the banking app is not correct. The banking mobile app should display the reason.
Ask the shopper to retry the transaction.
Check the reason in the banking application and try again.
(USER_DECLINED) Rejection by the user
The shopper declined the transaction in the mobile app.
Ask the shopper to retry the transaction.
Payment rejected in a banking application. Try again.
(USER_TIMEOUT) User timeout
The shopper did not confirm the transaction in the mobile banking app within the time limit.
Ask the shopper to retry the transaction.
Payment not confirmed on time in the banking application. Try again.
(TIMEOUT) System timeout
Timeout in communication with the mobile banking app or the Issuer’s system.
Ask the shopper to retry the transaction later.
Payment not confirmed on time in the banking application. Try again.
(AM_TIMEOUT) Mobile app timeout
Timeout in communication with the mobile app.
Ask the shopper to retry the transaction later.
Payment not confirmed on time in the banking application. Try again.
Boncard
These are the response codes, that are returned by Boncard.
(Generic error)
General decline. The transaction was blocked due to an unspecified reason.
Ask the shopper to retry the transaction later.
Retry later or using another means of payment.
(Card unknown)
Invalid card number or CVC.
Ask the shopper to double-check the card details.
Re-enter the card details, retry using another means of payment or contact Boncard.
(No funds)
Insufficient funds. The cardholder's account does not cover the transaction amount or the card limit has been reached
Ask the shopper to load the card or to use another means of payment.
Check the card or use a different payment method.
(Authentication error)
UserId and / or password are wrong
Ask the shopper to retry with correct login data or to use another means of payment.
Retry with correct UserId and password, contact Boncard if login is still not possible.
(Invalid transaction)
A transaction is declined because it is not allowed for the cardholder's account, the card details are incorrect, or there is a problem with the transaction data. For example, refund amount is too high or if the system or terminal is not configured correctly.
Contact Boncard and payment service provider.
Verify card data and retry or use another means of payment.
(Amount invalid)
The amount does not adhere to the restrictions for this action. E.g. it might be exceeding the allowed amount, pre-set limits, or it's too high or too low for the card.
Ask the shopper to retry later.
Verify card data and retry or use another means of payment.
(Card locked)
The card has been reported lost, stolen or involved in a fraud. For example, if CVC was entered incorrectly several times.
Ask the shopper to contact Boncard or to use another means of payment.
Contact Boncard to check the card status or retry using another means of payment.
(Wrong card number)
The card number entered for a transaction is incorrect, does not exist, or is otherwise not recognized by Boncard. This usually happens due to a typo, a wrong card being used, or an outdated or unissued card number.
Contact the payer to double-check the card details.
Re-enter the card details, retry using another means of payment or contact Boncard.
(Card expired)
The transaction was declined because the card is expired by Boncard.
Ask the shopper to contact Boncard or to use another means of payment.
Contact Boncard to check the card status or retry using another means of payment.
Klarna
These are the response codes, that are returned by Klarna.
(BAD_VALUE) Invalid parameter
The transaction was declined because one of the values in the payment request is invalid. For example:
The data sent in the JSON API OrderId does not follow Klarna's requirements.
The address contains invalid characters. Make sure that you only submit UTF-8 encoded values when creating a Klarna payment.
The phone number is not formatted correctly. Refer to our Klarna documentation to see how to format the telephone number.
The postal code in the billing or the delivery address is not formatted correctly.
The locale in the payment request is not compatible.
The currency not formatted correctly or doesn't apply for a certain locale.
Error message on the validation criteria for the tax calculation. Refer to the Klarna documentation for more information about the tax calculation.
Check the additional decline information
Refer to Klarna's documentation to see how to format:
The merchant data (JSON API OrderId)
Phone number
Locale and currency
Postal code
Check address fields for invalid characters
Verify your tax amount calculation
Use another means of payment
(REFUND_NOT_ALLOWED) Over refund is not allowed
The refund was refused because the amount is higher than the original payment.
Correct the refund amount and retry or contact the payer, use refund on another means of payment.
Accept another means of payment for refund.
(NOT_FOUND)
The shopper has tried to make a payment for an offer that has expired
Ask the shopper to retry the transaction.
Try again or use another means of payment.
(REFUSED)
Klarna's internal risk engine refused the payment. A possible reason is that the shopper has an unpaid balance towards Klarna
Contact the shopper and check the status.
Try again or use another means of payment.
(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.
Contact the shopper and check the status.
Try again or use another means of payment.
PayPal
These are the response codes, that are returned by PayPal.
(AGREEMENT_ALREADY_CANCELLED)
The agreement that the payment was based on, has been cancelled.
Contact PayPal.
Use another means of payment.
(AUTHORIZATION_ALREADY_CAPTURED)
The payment has already been captured. Do not retry the same request.
Do nothing.
Do not retry.
(AUTHORIZATION_EXPIRED)
The payment cannot be captured because the authorization validity period has expired.
Retry the transaction, contact the payer.
Retry the transaction.
(AUTHORIZATION_VOIDED)
The payment cannot be captured or re-authorized because the authorization has been cancelled.
Retry the transaction, contact the payer.
Retry the transaction.
(BILLING_AGREEMENT_NOT_FOUND)
The billing agreement token for this transaction was not found.
Contact PayPal.
Use another means of payment.
(CANNOT_BE_ZERO_OR_NEGATIVE)
The amount must be greater than zero. If the currency supports decimals, only two decimal place precision is supported.
Contact the payment service provider.
Use another means of payment.
(CAPTURE_FULLY_REFUNDED)
It is not possible to issue a refund because the payment has already been fully refunded.
Do nothing.
Do nothing.
(COMPLIANCE_VIOLATION)
The transaction is declined because it is not compliant with regulations.
Contact the shopper to obtain another means of payment, contact PayPal.
Use another means of payment.
(DUPLICATE_INVOICE_ID)
Duplicate invoice ID detected. This error can occur, if your account has been set to use the reference (Order ID) from your payment request as the transaction ID. PayPal will check the submitted reference (Order ID) and refuse payment with duplicates.
Make sure, that each payment has a unique reference (Order ID).
Use another means of payment.
(DUPLICATE_TRANSACTION)
Duplicate invoice ID detected. This error can occur if your account has been set to use the reference from your payment request as the transaction ID.
Make sure, that each payment has a unique reference (Order ID).
Use another means of payment
(INSTRUMENT_DECLINED)
The payment instrument was declined by the processor or bank, or cannot be used for this payment. In case of insufficient funds, you can retry and ask the customer to use a different payment method.
Retry the transaction, or contact the payer.
Retry later or use another means of payment.
(INTERNAL_SERVER_ERROR)
Something unexpected has gone wrong on the PayPal server. You can retry the transaction.
Retry later, contact PayPal or the payment service provider if the problem persists.
Retry later or use another means of payment.
(INVALID_RESOURCE_ID)
The specified resource ID does not exist. Check the resource ID and try again.
Contact PayPal.
Use another means of payment.
(MAX_NUMBER_OF_PAYMENT_ATTEMPTS_EXCEEDED)
You have retried the payment more times than is allowed.
Do not retry on the same day. Contact the shopper to obtain another means of payment.
Retry on another day or use another means of payment.
(MAX_NUMBER_OF_REFUNDS_EXCEEDED)
You have retried a refund for this capture more times than is allowed.
Contact the payer, or use another means of payment to refund the payer.
N/A
(NOT_AUTHORIZED)
Authorization failed due to insufficient permissions.
Contact the shopper to obtain another means of payment, contact PayPal.
Use another means of payment
(PAYEE_ACCOUNT_RESTRICTED)
The transaction failed because PayPal has put restrictions on the seller's PayPal account.
Contact PayPal and check the account settings.
Use another means of payment.
(PAYER_ACCOUNT_LOCKED_OR_CLOSED)
The shopper's account cannot be used for this transaction because the account is locked or closed. Do not retry this transaction with the same account details.
Contact the shopper to obtain another means of payment.
Use another means of payment.
(PAYER_ACCOUNT_RESTRICTED)
The transaction failed because PayPal has put restrictions on the shopper's PayPal account.
Contact the shopper to obtain another means of payment.
Contact PayPal or use another means of payment.
(PAYER_CANNOT_PAY)
The shopper cannot pay for this transaction using PayPal. Ask the shopper to try another payment method.
Contact the shopper to obtain another means of payment.
Contact PayPal or use another means of payment.
(PERMISSION_DENIED)
No permission to access or perform this operation.
Contact the shopper to obtain another means of payment.
Use another means of payment.
(REDIRECT_PAYER_FOR_ALTERNATE_FUNDING)
The transaction failed. Ask the shopper to try another payment method.
Contact the shopper to obtain another means of payment.
Use another means of payment.
(REFUND_FAILED_INSUFFICIENT_FUNDS)
The refund failed because the seller's PayPal account has insufficient funds, or because the bank account linked to the seller's PayPal account has not been verified or has insufficient funds
Contact PayPal and check the account settings, check with the bank, inform the payer
N/A
(REFUND_NOT_PERMITTED_DUE_TO_CHARGEBACK)
It is not possible to issue a refund because the payment is disputed. If you are a marketplace, contact the seller to resolve the chargeback.
Do nothing.
Wait for chargeback.
(REFUND_TIME_LIMIT_EXCEEDED)
It is not possible to refund this payment because the time period that PayPal allows for issuing a refund has passed.
Contact the payer, or use another means of payment to refund the payer.
N/A
(REFUSED_MARK_REF_TXN_NOT_ENABLED)
Your PayPal merchant account is not set up or approved to initiate recurring payments on behalf of your customers.
Contact PayPal and check the account settings. Contact the shopper to obtain another means of payment.
N/A
(TRANSACTION_DISPUTED)
Partial refunds are not possible because the transaction is disputed.
N/A
Wait for chargeback.
(TRANSACTION_REFUSED)
There are many possible reasons for a refused transaction, including, an issue with the amount or currency of a partial refund, already fully refunded, card account closed or never existed, suspected fraud.
Contact the shopper to obtain another means of payment.
Use another means of payment.
(UNPROCESSABLE_ENTITY)
The requested action cannot be performed, is semantically incorrect, or failed.
Contact the shopper to obtain another means of payment.
Use another means of payment.
Account-to-Account (A2A) payments
These are the response codes, that are returned by A2A.
(Error) General decline
Authorization is declined by the bank on an unspecified reason.
N/A
Use another means of payment.
(BAD_REQUEST) MSP scheme error
The transaction was declined because a mandatary parameter is missing in the payment request. For example, the Refund requires the consumer name but it is empty.
Check the request, or contact the payer to obtain another means of payment for refund.
Use another means of payment.
(CancelledAtTPP) Canceled by the payer
The payer canceled the payment explicitly by clicking on the cancel button during the payment flow.
N/A
Use another means of payment.
(TimeoutAtTpp) Timeout die to payer inactivity
The payer stopped doing anything during the payment process and the payment has expired.
N/A
Use another means of payment.
(Cancelled) Cancelled by the MSP
MSP hasn't receive any information or transaction status notification during the expiration period and cancelled the payment. If MSP doesn't cancel explicitly, the transaction appears in the Failed Journal with the reason "Authorization expired".
N/A
Use another means of payment.
(SCHEME_UNAVAILABLE) Internal technical error
The transaction is declined due to internal technical error.
If the problem persists, contact the Acquirer or payment service provider.
Use another means of payment.
(INTERNAL_SERVER_ERROR) Internal technical error
The transaction is declined due to internal technical error.
If the problem persists, contact the Acquirer or payment service provider.
Use another means of payment.
Alipay+
These are the response codes, that are returned by Alipay+.
(ACCESS_DENIED) Access is denied
There is a technical issue with the configuration
Contact the Alipay+ support team
Use another means of payment
(BUSINESS_NOT_SUPPORT) The payment business is not supported
There is a configuration issue with the contract or terminal
Check whether the parameter values in the request message is conform to the contract. If yes, it is recommended to the Alipay+ support team and the payment service provider
Use another means of payment
(CURRENCY_NOT_SUPPORT) The currency is not supported
The currency is not supported
The the Alipay+ contract details and contact support team to activate more currencies
Use another means of payment
(INVALID_CLIENT) The client is invalid
There is a technical issue with the configuration
Contact the Alipay+ support team
Use another means of payment
(INVALID_CONTRACT) The contract is invalid
This error indicates that either your merchant facility is non-functional or the merchant details are incorrect. This can happen if the merchant configuration on the acquirer side or by Alipay is in progress (not yet completed) or has been changed for some reason
Retry transaction later or contact the account manager to check the merchant configuration on the acquirer side including terminal configuration. Contact the Alipay+ support team if the problem persists
Retry transaction later or use another means of payment
(INVALID_SIGNATURE) The signature is invalid
There is a technical issue with the configuration
Contact the payment service provide to check whether the public key, signed message, and signature algorithm are as expected
Use another means of payment
(KEY_NOT_FOUND) The key is not found
There is a technical issue with the configuration
Contact the Alipay+ support team to fix this issue
Use another means of payment
(MEDIA_TYPE_NOT_ACCEPTABLE) MIME type is not acceptable
The server does not implement the media (MIME) type that is acceptable to the client. Web browsers and other applications use media types to determine how to process the data
Ask the payer to use another browser configuration or a different payment method
Use a media type that is accepted by Alipay+ or another means of payment
(MERCHANT_NOT_REGISTERED) The merchant is not registered
The merchant is not registered
It is recommended to contact the Alipay+ support team to troubleshoot the issue.
Use another means of payment
(METHOD_NOT_SUPPORTED) The server does not implement the requested HTTPS method
The transaction is declined due to internal technical error
If the problem persists, contact the payment service provider
Use another means of payment
(NO_INTERFACE_DEF) API is not defined
The transaction is declined due to internal technical error
If the problem persists, contact the payment service provider
Use another means of payment
(ORDER_IS_CLOSED) The order is closed
The payer opened the payment page with Alipay+, but did not pay with Alipay+ Wallet. After 10 minutes, the Alipay+ Payment Page automatically expires and the payment order is flagged as closed
Ask the payer to use another means of payment
Install the latest version of Alipay+ app and configure it properly or use another means of payment
(PARAM_ILLEGAL) Illegal parameters
The transaction was declined due to illegal input parameter(s). For example, non-numeric input, invalid date.
Check Alipay+ requirements or contact you payment service provider
Use another means of payment
(PAYMENT_AMOUNT_EXCEED_LIMIT) The amount exceeds the limit
The payment amount exceeds the limit that is specified by Alipay+
It is recommended to inform the user of the error regarding amount limits. Ask the payer to split the order or to use another means of payment
Split the order or use another means of payment
(PAYMENT_AMOUNT_INVALID) Payment amount is invalid
The amount does not adhere to the restrictions for this action. E.g. it might be exceeding the allowed capture amount, pre-set limits, or it's too high or too low for the merchant configuration. For refunds, the total refund amount exceeds the transaction amount
Check that the amount is correct and retry. Contact the Alipay+ support team or the payment service provider to troubleshoot the issue with the merchant configuration
Use another means of payment
(PAYMENT_COUNT_EXCEED_LIMIT) The number of payments exceeds the limit
The transaction is declined due to internal technical error. The Alipay server is blocked due too many requests
If the problem persists, contact the Alipay+ support team or the payment service provider
Retry later or use another means of payment
(PROCESS_FAIL) The process failed
The transaction is declined due to a general business failure occurred
Do not retry. Contact the Alipay+ support team or the payment service provider to troubleshoot the issue
Use another means of payment
(REPEAT_REQ_INCONSISTENT) Repeated requests are inconsistent
The transaction is declined due to internal technical error. The values of the parameters in the repeated requests are not the same
Contact the payment service provider to troubleshoot the issue
Try again or use another means of payment
(RISK_REJECT) Risk check failed
The request is rejected because of the risk control
It is recommended to inform the user of the error. Ask the payer to use another means of payment
Use another means of payment
(UNAVAILABLE_PAYMENT_METHOD) Payment method unavailable
The transaction is declined due to a general failure on the payer side
It is recommended to inform the user of the error. Ask the payer to use another means of payment
Use another means of payment
(USER_AMOUNT_EXCEED_LIMIT) The amount exceeds the limit
The payment amount exceeds the payment limit that is specified by the user's digital wallet
It is recommended to inform the user of the error. Ask the payer to split the order or to use another means of payment
Contact Alipay+ to change the configuration, increase limit or use another means of payment
(USER_BALANCE_NOT_ENOUGH) The user balance is not enough
The user's account does not cover the transaction amount
It is recommended to inform the user of the error. Ask the payer to use another means of payment
Check the account or use another means of payment
(USER_NOT_EXIST) The user does not exist
The transaction is declined due to a general (technical, business or configuration) failure
It is recommended to inform the user of the error. Ask the payer to use another means of payment
Use another means of payment
(USER_PAYMENT_VERIFICATION_FAILED) Payment verification failed
User fails to pass the payment verification in the methods like OTP, PIN and so on
It is recommended to inform the user of the error. Ask the payer to retry using correct verification data or another means of payment
Retry or use another means of payment
(USER_STATUS_ABNORMAL) The user status is abnormal
The transaction is declined due to a general (technical, business or configuration) failure
It is recommended to inform the user of the error. Ask the payer to check wallet configuration and to retry or to use another means of payment
Check wallet configuration to verify the status. Retry or use another means of payment
(PAYMENT_IN_PROCESS) The payment is being processed
The payer must be redirected to the Alipay+ checkout page to confirm the payment
Contact the payment service provider if the issue persists, ask payer to use another means of payment
Retry or use another means of payment
(REQUEST_TRAFFIC_EXCEED_LIMIT) The request traffic exceeds the limit
The transaction is declined due to internal technical error (frequency of API calls)
If the problem persists, contact the payment service provider
Use another means of payment
(UNKNOWN_EXCEPTION) An API call failed, which is caused by unknown reasons
The transaction is declined due to internal technical error
If the problem persists, contact the payment service provider
Use another means of payment
Last updated
Was this helpful?