Decline Codes and Reasons

If a card issuer declines a payment, they may provide a reason by using a decline code.

Below is a list of some possible decline codes that can be returned, along with suggestions for the next steps to take to try and complete the payment.

DCDial Decline Codes

Understand what decline codes mean and how you can resolve them when a charge is declined. 

  • authentication_required:

The card was declined as the transaction requires authentication.

The customer should try again and authenticate their card when prompted during the transaction. If the card issuer returns this decline code on an authenticated transaction, the customer needs to contact their card issuer for more information.

  • approve_with_id:

The payment cannot be authorized.

The payment should be attempted again. If it still cannot be processed, the customer needs to contact their card issuer.

  • call_issuer:

The card has been declined for an unknown reason.

The customer needs to contact their card issuer for more information.

  • card_not_supported:

The card does not support this type of purchase.

The customer needs to contact their card issuer to make sure their card can be used to make this type of purchase.

  • card_velocity_exceeded:

The customer has exceeded the balance or credit limit available on their card.

The customer has exceeded the balance or credit limit available on their card.

  • currency_not_supported:

The card does not support the specified currency.

The customer needs to check with the issuer whether the card can be used for the type of currency specified.

  • do_not_honor:

The card has been declined for an unknown reason.

The customer needs to contact their card issuer for more information.

  • do_not_try_again:

The card has been declined for an unknown reason.

The customer should contact their card issuer for more information.

  • duplicate_transaction:

A transaction with an identical amount and credit card information was submitted very recently.

Check to see if a recent payment already exists.

  • expired_card:

The card has expired.

The customer should use another card.

  • fraudulent:

The payment has been declined as Stripe suspects it is fraudulent.

Do not report more detailed information to your customer. Instead, present as you would the generic_decline described below.

  • generic_deadline:

The card has been declined for an unknown reason.

The customer needs to contact their card issuer for more information.

  • incorrect_number:

The card number is incorrect.

The customer should try again using the correct card number.

  • incorrect_cvc:

The CVC number is incorrect.

The customer should try again using the correct CVC

  • incorrect_pin:

The PIN entered is incorrect. This decline code only applies to payments made with a card reader.

The customer should try again using the correct PIN.

  • incorrect_zip:

The ZIP/postal code is incorrect.

The customer should try again using the correct billing ZIP/postal code.

insufficient_funds:

The card has insufficient funds to complete the purchase.

The customer should use an alternative payment method.

  • invalid_account:

The card, or account the card is connected to, is invalid.

The customer needs to contact their card issuer to check that the card is working correctly.

  • invalid_amount:

The payment amount is invalid or exceeds the amount that is allowed.

If the amount appears to be correct, the customer needs to check with their card issuer that they can make purchases of that amount.

  • invalid_cvc:

The CVC number is incorrect.

The customer should try again using the correct CVC.

  • invalid_expiry_month:

The expiration month is invalid.

The customer should try again using the correct expiration date.

  • invalid_expiry_year:

The expiration year is invalid.

The customer should try again using the correct expiration date.

  • invalid_number:

The card number is incorrect.

The customer should try again using the correct card number.

  • invalid_pin:

The PIN entered is incorrect. This decline code only applies to payments made with a card reader.

The customer should try again using the correct PIN.

  • issuer_not_available:

The card issuer could not be reached, so the payment could not be authorized.

The payment should be attempted again. If it still cannot be processed, the customer needs to contact their card issuer.

  • lost_card:

The payment has been declined because the card is reported lost.

The specific reason for the decline should not be reported to the customer. Instead, it needs to be presented as a generic decline.

  • merchant_blacklist:

The payment has been declined because it matches a value on the Stripe user’s block list.

Do not report more detailed information to your customer. Instead, present as you would the generic_decline described above.

  • new_account_information_available:

The card, or account the card is connected to, is invalid.

The customer needs to contact their card issuer for more information.

  • no_action_taken:

The card has been declined for an unknown reason.

The customer should contact their card issuer for more information.

  • not_permitted:

Payment is not permitted.

The customer needs to contact their card issuer for more information.

  • offline_pin_required:

The card has been declined as it requires a PIN.

The customer should try again by inserting their card and entering a PIN.

  • online_or_offline_pin_required:

The card has been declined as it requires a PIN.

If the card reader supports an Online PIN, the customer should be prompted for a PIN without a new transaction being created. If the card reader does not support an Online PIN, the customer should try again by inserting their card and entering a PIN.

  • pickup_card:

The card cannot be used to make this payment (it may have been reported lost or stolen).

The customer needs to contact their card issuer for more information.

  • pin_try_exceeded:

The allowable number of PIN tries has been exceeded.

The customer must use another card or method of payment.

  • processing_error:

An error occurred while processing the card.

The payment should be attempted again. If it still cannot be processed, try again later.

  • reenter_transaction:

The payment could not be processed by the issuer for an unknown reason.

The payment should be attempted again. If it still cannot be processed, the customer needs to contact their card issuer.

  • restricted_card:

The card cannot be used to make this payment (it may have been reported lost or stolen).

The customer needs to contact their card issuer for more information.

  • revocation_of_authorization:

The card has been declined for an unknown reason.

The customer should contact their card issuer for more information.

  • security_violation:

The card has been declined for an unknown reason.

The customer needs to contact their card issuer for more information.

  • stolen_card:

The payment has been declined because the card is reported stolen.

The specific reason for the decline should not be reported to the customer. Instead, it needs to be presented as a generic decline.

  • stop_payment_order:
The card has been declined for an unknown reason.

The customer should contact their card issuer for more information.

  • testmode_decline:

A Stripe test card number was used.

A genuine card must be used to make a payment.

  • transaction_not_allowed:

The card has been declined for an unknown reason.

The customer needs to contact their card issuer for more information.

  • try_again_later:

The card has been declined for an unknown reason.

Ask the customer to attempt the payment again. If subsequent payments are declined, the customer should contact their card issuer for more information.

  • withdrawal_count_limit_exceeded:

The customer has exceeded the balance or credit limit available on their card.

The customer should use an alternative payment method.


ACHQ Return Codes


Below are ACHQ return codes, reasons, and details. For more information, please refer to https://achq.com/ach-return-codes/.


  • Insufficient Funds:

The available and/or cash reserve balance is not sufficient to cover the dollar value of the debit entry.

You can try the transaction again up to two times within 30 days of the original authorization date.

  • Account Closed:

A previously active account has been closed by the action of the customer or the RDFI.

Contact your customer for a different bank account or another form of payment. If you have not yet shipped the goods or provided the services covered by the payment, you may want to wait to do so until you have confirmation of a settled payment.

  • No Account/Unable to Locate Account:
The account number structure is valid, and it passes the check digit validation, but the account number does not correspond to the individual identified in the entry, or the account number designated is not an open account.

Contact your customer and confirm the Routing Number, Bank Account Number, and the exact name on the bank account. (You can request a copy of a voided check so that you can verify.) If this information does not exactly match what you initially entered, make changes and submit a NEW payment.

  • Invalid Account Number:

The account number structure is not valid. The entry may fail the check digit validation or may contain an incorrect number of digits.

Obtain the correct bank account number. (You can request a copy of a voided check so that you can verify.) Submit a NEW payment using the corrected bank account number.

  • Unauthorized Debit Entry*:

Account number structure not valid: entry may fail check digit validation or may contain an incorrect number of digits.


* You cannot re-submit this transaction. Any additional transactions you attempt to process against this account will also be returned unless your customer specifically instructs his bank to accept them.

Contact your customer and resolve any issues that caused the transaction to be disputed.


You can ask the customer for a different form of payment, or ask to debit a different bank account.


If you need to debit the same bank account, instruct your customer to call the bank and remove the block on transactions.


Unfortunately, there is no dispute resolution available to you within the ACH Network. If your customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect.


If this action is taken, please contact ACHQ.

  • Returned per ODFI’s Request:

The ODFI has requested that the RDFI return the ACH entry. If the RDFI agrees to return the entry, the ODFI must indemnify the RDFI according to Article Five (Return, Adjustment, Correction, and Acknowledgment of Entries and Entry Information) of these Rules.

Please contact ACHQ.

  • Authorization Revoked by Customer (adjustment entries):

Authorization Revoked by Customer – The consumer, who previously authorized ACH payment, has revoked authorization from Originator (must be returned no later than 60 days from the settlement date and the customer must sign an affidavit).

Immediately suspend any recurring payment schedules entered for this bank account. This will prevent additional transactions from being returned while you address the issue with your customer. Then contact your customer and resolve any issues that caused the transaction to be disputed or the schedule to be canceled.


You can ask the customer for a different form of payment, or ask to debit a different bank account.

If you need to debit the same bank account, instruct your customer to call the bank and remove the block on transactions.


Unfortunately, there is no dispute resolution available to you within the ACH Network. If your customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect. If this action is taken, please contact ACHQ.

  • Payment Stopped or Stop Payment on Item:


    • The Receiver of a recurring debit transaction has the right to stop payment on any specific ACH debit. The RDFI should verify the Receiver’s intent when a request to stop payment is made to ensure this is not intended to be a revocation of the authorization.


A stop payment order shall remain in effect until the earliest of the following occurs: a lapse of six months from the date of the stop payment order, payment of the debit entry has been stopped, or the Receiver withdraws the stop payment order.


    • The RDFI determines that a stop payment order has been placed on the item to which the PPD debit entry constituting notice of presentment or the PPD Accounts Receivable Truncated Check Debit Entry relates. [The RDFI determines that a stop payment order has been placed on the item to which the PPD Accounts Receivable Truncated Check Debit Entry relates.]

Contact your customer and resolve any issues that caused the transaction to be stopped.

You can re-enter the returned transaction again with proper authorization from your customer. You can also ask your customer for a different form of payment.

  • Uncollected Funds:

A sufficient book or ledger balance exists to satisfy the dollar value of the transaction, but the dollar value of transactions in the process of collection (i.e., uncollected checks) brings the available and/or cash reserve balance below the dollar value of the debit entry.

You can try the transaction again up to two times within 30 days of the original authorization date.

  • Customer Advises Not Authorized; Item Is Ineligible, Notice Not Provided, Signatures Not Genuine, or Item Altered (adjustment entries):


    • For entries to Consumer Accounts that are not PPD debit entries constituting notice of presentment or PPD Accounts Receivable Truncated Check Debit Entries in accordance with Article Two, subsection 2.1.4(2), the RDFI has been notified by its customer, the Receiver, that the Originator of a given transaction has not been authorized to debit his account.


    • For entries to Consumer Accounts that are not PPD Accounts Receivable Truncated Check Debit Entries in accordance with Article Two, subsection 2.1.4(2) (Authorization/Notification for PPD Accounts Receivable Truncated Check Debit Entries), the RDFI has been notified by its customer, the Receiver, that the Originator of a given transaction has not been authorized to debit his account.
  • The Receiver may request immediate credit from the RDFI for an unauthorized debit. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information pertaining to that debit entry.


  • Immediately suspend any recurring payment schedules entered for this bank account. This will prevent additional transactions from being returned while you address the issue with your customer. Then contact your customer and resolve any issues that caused the transaction to be disputed or the schedule to be canceled.


You can ask the customer for a different form of payment, or ask to debit a different bank account.
If you need to debit the same bank account, instruct your customer to call the bank and remove the block on transactions.


Unfortunately, there is no dispute resolution available to you within the ACH Network. If your customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect. If this action is taken, please contact ACHQ.

  • Check Truncation Entry Return:

To be used when returning a check truncation entry. This reason for return should be used only if no other return reason code is applicable. The RDFI should use the appropriate field in the addenda record to specify the reason for the return (i.e., “exceeds dollar limit,” “no match on ARP,” “stale date,” etc.)

Immediately suspend any recurring payment schedules entered for this bank account. This will prevent additional transactions from being returned while you address the issue with your customer. Then contact your customer and resolve any issues that caused the transaction to be disputed or the schedule to be canceled.


You can ask the customer for a different form of payment, or ask to debit a different bank account.

If you need to debit the same bank account, instruct your customer to call the bank and remove the block on transactions.


Unfortunately, there is no dispute resolution available to you within the ACH Network. If your customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect. If this action is taken, please contact ACHQ.

  • Branch Sold to Another DFI:

A financial institution may continue to receive entries destined for an account at a branch that has been sold to another financial institution. Because the RDFI no longer maintains the account and is unable to post the entry, it should return the entry to the ODFI.

Obtain a new Routing Number and Bank Account Number information, then enter a NEW transaction using the updated account numbers.


If the transaction was part of a recurring payment schedule, be sure to update the schedule to use the new bank account.

  • RDFI not qualified to participate:
The financial institution is not qualified to participate in ACH or the routing number is incorrect.

Double-check that you entered the Routing Number correctly, and contact your customer to confirm it if necessary. Then submit a NEW payment using the correct routing number.

  • Representative Payee Deceased or Unable to Continue in that Capacity:
A representative payee is a person or institution authorized to accept entries on behalf of one or more other persons, such as legally incapacitated adults or minor children. The representative payee is either deceased or unable to continue in that capacity. The beneficiary is not deceased.


  • Beneficiary or Account Holder (Other Than a Representative Payee) Deceased:


    • The beneficiary is the person entitled to the benefits and is deceased. The beneficiary may or may not be the account holder.
    • The account holder (acting in a non-representative payee capacity) is the owner of the account and is deceased.
  • Account Frozen:
The funds in the account are unavailable due to specific actions taken by the RDFI or by legal action.

Obtain a different form of payment. You will not be able to process transactions using this bank account until it is unfrozen.

  • File Record Edit Criteria (Specify):
Some fields that are not edited by the ACH Operator are edited by the RDFI. If the entry cannot be processed by the RDFI, the field(s) causing the processing error must be identified in the addenda record information field of the return.


  • Non-Transaction Account:
The ACH entry is destined for a non-transaction account. This would include either an account against which transactions are prohibited or limited.

Contact your customer to obtain authorization to charge a different bank account.

Ask for a different form of payment.

  • Invalid Company Identification:
The identification number used in the Company Identification Field is not valid. This Return Reason Code will normally be used on CIE transactions.


  • Invalid Individual ID Number:
In CIE and MTE entries, the Individual ID Number is used by the Receiver to identify the account. The Receiver has indicated to the RDFI that the number with which the Originator was identified is not correct.


  • Credit Entry Refused by Receiver:
The Receiver may return a credit entry because one of the following conditions exists: (1) a minimum amount required by the Receiver has not been remitted; (2) the exact amount required has not been remitted; (3) the account is subject to litigation and the Receiver will not accept the transaction; (4) acceptance of the transaction results in an overpayment; (5) the Originator is not known by the Receiver; or (6) the Receiver has not authorized this credit entry to this account.

Contact your customer to work out the problem, or ask them to work the problem out with their bank. Have your customer confirm that the refund will be accepted, then attempt to refund the transaction again.

Alternatively, you can send your customer a paper check for the refund amount.

  • Duplicate Entry:

The RDFI has received what appears to be a duplicate entry; i.e., the trace number, date, dollar amount, and/or other data matches another transaction. This code should be used with extreme care. The RDFI should be aware that if a file has been duplicated, the Originator may have already generated a reversal transaction to handle the situation.

Contact ACHQ.

  • Corporate Customer Advises Not Authorized:

The RDFI has been notified by the Receiver (non-consumer) that the Originator of a given transaction has not been authorized to debit the Receiver’s account.

Immediately suspend any recurring payment schedules entered for this bank account. This will prevent additional transactions from being returned while you address the issue with your customer. Then contact your customer and resolve any issues that caused the transaction to be disputed or the schedule to be canceled.


You can ask the customer for a different form of payment, or ask to debit a different bank account.

If you need to debit the same bank account, instruct your customer to call the bank and remove the block on transactions.


Unfortunately, there is no dispute resolution available to you within the ACH Network. If your customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect. If this action is taken, please contact ACHQ.

  • Permissible Return Entry (CCD and CTX only):

The RDFI has been notified by the ODFI that the ODFI agrees to accept a CCD or CTX return entry in accordance with Article Seven, section 7.3 (ODFIAgrees to Accept CCD or CTXReturn).

  • In some cases, a business bank account holder, or the bank itself, may request a return after that 2-day window has closed. If the ODFI (your bank, or your ACH Processor) agrees to accept a late return, it is processed using the R31 return code.


  • You can ask for a different form of payment, or ask to debit a different bank account.

  • Return of XCK Entry:

The RDFI determines at its sole discretion to return an XCK entry. This return reason code may only be used to return XCK entries. An XCK entry may be returned up to sixty days after its Settlement Date.


USAePay Error Codes

For more information on the USAePay error codes and messages, please refer to https://help.usaepay.info/developer/downloads/errorcodelist.pdf.


PayPal Decline Codes

For more information on the PayPal decline codes, please refer to https://developer.paypal.com/braintree/articles/control-panel/transactions/declines.


Authorize.net Error Codes

For more information on the Authorize.net error codes, please refer to https://developer.authorize.net/api/reference/features/errorandresponsecodes.html. 

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us