/
Braintree Decline Codes

Braintree Decline Codes

Braintree Decline Codes

 

Purpose:

The purpose of this walkthrough is to show you the different error codes that you could receive while using the Braintree gateway. This will help you identify and correct the error that you may be receiving. 

 

Pre Requisites:

  • Active gateway account

  • Error code you are receiving

 

NOTE

Declines are not the same as gateway rejections. Declined transactions are blocked by the customer's bank, while gateway rejections are blocked by your Braintree gateway settings.

 

Authorization decline codes

Code

 

Text

 

Implications

 

Type

 

Code

 

Text

 

Implications

 

Type

 

2000

Do Not Honor

The customer's bank is unwilling to accept the transaction. The customer will need to contact their bank for more details regarding this generic decline.

Soft

2001

Insufficient Funds

The account did not have sufficient funds to cover the transaction amount at the time of the transaction – subsequent attempts at a later date may be successful.

Soft

2002

Limit Exceeded

The attempted transaction exceeds the withdrawal limit of the account. The customer will need to contact their bank to change the account limits or use a different payment method.

Soft

2003

Cardholder's Activity Limit Exceeded

The attempted transaction exceeds the activity limit of the account. The customer will need to contact their bank to change the account limits or use a different payment method.

Soft

2004

Expired Card

Card is expired. The customer will need to use a different payment method.

Hard

2005

Invalid Credit Card Number

The customer entered an invalid payment method or made a typo in their credit card information. Have the customer correct their payment information and attempt the transaction again – if the decline persists, they will need to contact their bank.

Hard

2006

Invalid Expiration Date

The customer entered an invalid payment method or made a typo in their card expiration date. Have the customer correct their payment information and attempt the transaction again – if the decline persists, they will need to contact their bank.

Hard

2007

No Account

The submitted card number is not on file with the card-issuing bank. The customer will need to contact their bank.

Hard

2008

Card Account Length Error

The submitted card number does not include the proper number of digits. Have the customer attempt the transaction again – if the decline persists, the customer will need to contact their bank.

Hard

2009

No Such Issuer

This decline code could indicate that the submitted card number does not correlate to an existing card-issuing bank or that there is a connectivity error with the issuer. The customer will need to contact their bank for more information.

Hard

2010

Card Issuer Declined CVV

The customer entered in an invalid security code or made a typo in their card information. Have the customer attempt the transaction again – if the decline persists, the customer will need to contact their bank.

Hard

2011

Voice Authorization Required

The customer’s bank is requesting that the merchant (you) call to obtain a special authorization code in order to complete this transaction. This can result in a lengthy process – we recommend obtaining a new payment method instead. Contact us for more details.

Hard

2012

Processor Declined – Possible Lost Card

The card used has likely been reported as lost. The customer will need to contact their bank for more information.

Hard

2013

Processor Declined – Possible Stolen Card

The card used has likely been reported as stolen. The customer will need to contact their bank for more information.

Hard

2014

Processor Declined – Fraud Suspected

The customer’s bank suspects fraud – they will need to contact their bank for more information.

Hard

2015

Transaction Not Allowed

The customer's bank is declining the transaction for unspecified reasons, possibly due to an issue with the card itself. They will need to contact their bank or use a different payment method.

Hard

2016

Duplicate Transaction

The submitted transaction appears to be a duplicate of a previously submitted transaction and was declined to prevent charging the same card twice for the same service.

Soft

2017

Cardholder Stopped Billing

The customer requested a cancellation of a single transaction – reach out to them for more information.

Hard

2018

Cardholder Stopped All Billing

The customer requested the cancellation of a recurring transaction or subscription – reach out to them for more information.

Hard

2019

Invalid Transaction

The customer’s bank declined the transaction, typically because the card in question does not support this type of transaction – for example, the customer used an FSA debit card for a non-healthcare related purchase. They will need to contact their bank for more information.

Hard

2020

Violation

The customer will need to contact their bank for more information.

Hard

2021

Security Violation

The customer's bank is declining the transaction, possibly due to a fraud concern. They will need to contact their bank or use a different payment method.

Hard

2022

Declined – Updated Cardholder Available

The submitted card has expired or been reported lost and a new card has been issued. Reach out to your customer to obtain updated card information.

Hard

2023

Processor Does Not Support This Feature

Your account can't process transactions with the intended feature – for example, 3D Secure or Level 2/Level 3 data. If you believe your merchant account should be set up to accept this type of transaction, contact us.

Hard

2024

Card Type Not Enabled

Your account can't process the attempted card type. If you believe your merchant account should be set up to accept this type of card, contact us for assistance.

Hard

2025

Set Up Error – Merchant

Depending on your region, this response could indicate a connectivity or setup issue. Contact us for more information regarding this error message.

Soft

2026

Invalid Merchant ID

The customer’s bank declined the transaction, typically because the card in question does not support this type of transaction. If this response persists across transactions for multiple customers, it could indicate a connectivity or setup issue. Contact us for more information regarding this error message.