Response codes
This section describes why transactions sometimes fail.
Find the result code for a transaction using the Dashboard:
- In the left navigation menu, click Transactions.
- Use the search bar or filters to find the transaction that failed, then select it.
- The transaction's status, result code, and result description appear at the top of the details panel that appears.
Failed transaction with result code and description.
The content below does not provide an exhaustive list of transaction failure reasons.
800.100.152: Transaction declined by authorization system
Description: The risk system of the issuing bank (customer's bank) declined the transactions for account-related reasons, for example:
- Account closed - customer must contact their bank.
- Do not honor - customer must contact their bank.
- Identification required - FICA required; customer must contact their bank.
- No card record - customer must contact their bank or recheck the card number.
- No credit account - customer must contact their bank or recheck the card number.
- No savings account - customer must contact their bank or recheck the card number.
- Retry the transaction.
- Refer to card issuer - customer must contact their bank.
- Suspected malfunction - customer must contact their bank.
- Violation of law - prohibited.
What to tell your customer?
Your transaction was declined for one of the following account-related reasons:
- Your bank card or virtual card might not be enabled for online transactions.
- Another reason which only your bank can communicate with you. Contact your bank as more information on the failed transaction can only be communicated to you by your bank. This information is privy only to the customer and their bank.
100.380.401: User Authentication Failed
Description: Wrong OTP. This result code signifies that the bank's system was unable to authenticate the user.
What to tell your customer?
Your transaction failed because:
- You entered the OTP incorrectly.
- There was a field or system error with the OTP.
100.396.101: Cancelled by user
Description: The user started a transaction and then cancelled it or Checkout.
What to tell your customer?
See the description above.
100.396.103: Previously pending transaction timed out
Description: The registration transaction (RG) was not authenticated and timed out. The debit transaction references the registration token and hence this might also fail.
What to tell your customer?
See the explanation for 800.100.152.
100.380.501: Risk management transaction timeout
Description: The customer probably did not enter their OTP or they might not have been shown the 3-D Secure page because their browser or an extension might have blocked it, or because of an issue with the bank's 3-D Secure server. If the card is 3-D Secure enabled, the customer should receive an OTP during the authentication phase of the payment. The customer's bank handles OTP generation and sending. Peach Payments is not aware of and does not control the 3-D Secure authentication process. The customer's bank also authenticates the payment if the correct OTP is provided and when completed, sends Peach Payments a successful payment response. Note that Peach Payments does not know upfront whether a card is enabled for 3-D Secure.
What to tell your customer?
You might not have entered the OTP in time, your bank card is not enabled for online transactions, or there could be an issue with the bank's 3-D Secure server or transaction approval server. Try again if you know your bank card is activated for online transactions or contact your bank.
100.390.112: Technical Error in 3D system
Description: There is an error with the 3-D Secure process at the bank. It could be that their 3-D Secure system is down.
What to tell your customer?
There might be an issue with your bank's 3-D Secure server, check in with your bank.
100.100.101: invalid creditcard, bank account number or bank name
Description: The transaction failed because:
- Credit card number, bank account number, or bank name entered incorrectly.
- Credit card not activated for online transactions.
What to tell your customer?
See the description above.
100.100.700: invalid cc number/brand combination
Description: Your customer might be entering all the digits found on the reverse side of their card, instead of only the last three digits for Visa and Mastercard or the last four digits for Amex and Diners. Remember that by default, Amex is not activated unless you have specifically requested it. If you receive this error frequently, Peach Payments recommends showing an image of what a CVV is and clearly specifying to customers during the checkout the amount of digits they need to enter.
What to tell your customer?
Your transaction failed because:
- Credit card number, CVV, or CVC entered incorrectly.
- The credit card is not activated for online transactions.
- The credit card type is not accepted.
800.100.153: transaction declined (invalid CVV)
Description: Card might not be enabled for online transactions or the customer is using the wrong CVV or CVC numbers.
What to tell your customer?
Your transaction has been declined because either an invalid CVV or CVC number was entered or one wasn't entered. If you entered your CVV or CVC correctly and still had your transaction declined, contact your bank and inform them that you are unable to complete e-commerce transactions.
800.100.169: transaction declined (card type is not processed by the authorization center)
Description: Transaction failed because:
- The bank card is not enabled for online transactions.
- The bank card type is foreign registered and not Visa or Mastercard.
- There could be an issue with the bank's 3-D Secure server or transaction approval server.
What to tell your customer?
See the description above.
800.100.155: transaction declined (amount exceeds credit)
Description: The risk system of the issuing bank (customer's bank) declined the transactions for account-related reasons, for example:
- The customer has likely exceeded their available credit limit (not enough funds available).
- Most banks allow their customers to set their own limits in their banking app. When these limits are set, if the transaction exceeds the limit, the transaction fails.
What to tell your customer?
The transaction failed because of insufficient funds on your card. It is likely that you have exceeded your available funds or the limits set on your banking app.
100.150.203: registration is not valid, probably initially rejected
Description: When the customer tried to register their card for the payment, incorrect or no data was provided which results in the registration being rejected by the issuing bank.
What to tell your customer?
The initial registration phase of the transaction failed, meaning:
- The registering of the card contained no account holder data.
- The issuing bank was offline for the initial period of the transaction.
- Did not pass 3-D Secure resulting in the token not being valid.
800.100.170: transaction declined (transaction not permitted)
Description: This is a failure with the issuing bank and the cardholder must find out from their bank what caused the transaction to fail.
What to tell your customer?
The transaction was declined by your issuing bank. This means that the issuing bank could not process the transaction because of some rules applied to their system. Contact your bank, as further detail on the failed transaction can only be communicated to you by your bank. This information is privy only to the customer and their bank.
800.100.162: transaction declined (limit exceeded)
Description: The limit set by the customer's bank has been exceeded. The customer must check their daily limit on their banking app and confirm that their transaction will not take them over the limit.
What to tell your customer?
This transaction failed because you exceeded your limit. This error means that the transaction will bring your bank balance below the limit set by your bank or you have exceeded your transaction limit for that day. Check your daily limit and ensure that you have enough funds in your account to continue with the transaction.
100.390.107: Transaction rejected because cardholder authentication unavailable
Description: The transaction failed as it was rejected by the issuing bank:
- The card holder or issuing bank is not enrolled for 3-D Secure.
- 3-D Secure card authentication was unsuccessful, for example, if the card holder is not enrolled for 3-D Secure.
- Card or issuing bank is not 3-D Secure ready.
What to tell your customer?
See the description above.
800.100.203: Insufficient Funds
Description: The customer's card has insufficient funds for the transaction. They must check if they have enough funds in their account before trying again.
What to tell your customer?
Check if you have enough funds for the transaction.
800.100.100: transaction declined for unknown reason
Description: The customer tried to do a transaction but no data or incorrect data was provided for registration, resulting in the transaction being rejected by the issuing bank.
What to tell your customer?
The transaction was declined for an unknown reason (800.100.100 - an error message from your bank). Contact your bank for more information on this failure.
100.100.303: card expired
Description: The card might not be enabled for online transactions or the customer is using the wrong CVV or CVC numbers.
What to tell your customer?
This transaction failed because your card is expired. Try again with a valid card.
800.140.112: maximum number of registrations of email per credit card number exceeded
Description: When the risk setting is enabled, only one email registration is allowed per card number. This error occurs when trying to register a card and email that was already registered. The customer should either use their registered email or use a new email when registering with an email.
What to tell your customer?
You might have tried to register or transact with a different email on the same card number. This is usually a setting that is enabled on the merchant's website or for their business. Use one email per card number.
800.100.165: transaction declined (card lost)
Description: Transaction declines occur when the customer's card issuer or bank does not authorise the transaction for reasons such as possible fraud, invalid account information, or a lost or stolen card. In such instances, the customer must contact their bank or card issuer immediately to take corrective measures.
What to tell your customer?
We have checked the transaction and the result code received is "transaction declined". In this case, you must contact your bank to find out why the transaction was declined.
800.100.157: transaction declined (wrong expiry date)
Description: The transaction failed because the customer entered the wrong card expiry date (printed on the customer's bank card). The customer should double-check their card details before retrying the transaction. This support article explains the different card numbers.
What to tell your customer?
Your transaction was declined because the card number, expiry date, or CVV or CVC was entered incorrectly. Double-check the numbers above and try again.
800.100.151: transaction declined (invalid card)
Description: This could occur because:
- The customer's card might have expired.
- The card is not registered for online transactions.
What to tell your customer?
See the description above.
800.100.174: transaction declined (invalid amount)
Description: The customer is trying to do online payments but is exceeding the amount they are allowed to transact with. The customer must check their daily limits for online transactions and then try again.
What to tell your customer?
The transaction failed with an invalid amount error, indicating that you exceeded your daily limit. Check your daily limit for online transactions with your bank or in your bank app before retrying.
800.100.171: transaction declined (pick up card)
Description: The transaction was rejected by the customer's bank because either:
- The card has been flagged as a pick up card. In this case, the customer must contact their card issuer (the customer's bank) to learn why the card was flagged as a pick up card.
- The bank has cancelled the card and the customer might not be aware of this as they might have flagged the card as lost or stolen.
What to tell your customer?
The transaction failed with a "Transaction declined (Pick up card)" error. This could mean one of the following:
- The card could have been lost and picked up and reported to the bank.
- Depending on the bank, these cards are normally held for a period and "locked", that is, they fail until the customer signs the card out of the bank's possession.
- The bank has cancelled the card and you might not be aware of this as they might have flagged the card as lost or stolen.
800.100.158: transaction declined (suspecting manipulation)
Description: There is a limit set by the customer's issuing bank, for example:
- The customer is attempting and failing multiple transactions by inputting bad data such as a wrong CVV, expiry date, or re-trying transactions in quick succession.
- The customer's issuing bank suspects fraudulent behaviour or transacting out of the usual transactional categories. As a protective measure, they might fail the transaction.
What to tell your customer?
See the description above.
800.110.100: duplicate transaction
Description: The issuing bank has identified that the transaction reference, unique ID, or RRN of the transaction is the same as an earlier transaction. Peach Payments must raise this with the acquiring bank of the merchant who can investigate and indicate why the transaction has been flagged as a duplicate.
What to tell your customer?
See the description above.
800.100.168: transaction declined (restricted card)
Description: The customer's card issuer declined the transaction as the credit card has some restrictions. The customer must check with their issuing bank what the issue is.
What to tell your customer?
You must contact your issuing bank to learn why this transaction was declined.
See the error code documentation for a full list of response codes.
Updated 16 days ago