Posted on

bank declined transaction

An acceptable decline ratio is about 10% of your transactions, but this may fluctuate based on industry or business model. You can analyze your decline ratio by creating a decline report.

The most common reasons for declines are:
Hard declines are the result of an error or issue which can’t be resolved immediately. Action such as contacting Braintree Support or asking the customer to contact their bank will need to be taken to resolve the issue before the transaction can be retried.

The transaction response object that you receive via the API will indicate whether this flag was passed.

  1. Log into the Control Panel
  2. Click on the gear icon in the top right corner
  3. Click Processing from the drop-down menu
  4. Scroll to the Transactions section
  5. Next to Display Additional Processor Response, click the toggle to turn it on
  • Incorrect credit card number or expiration date
  • Insufficient funds
  • The bank declined based on location
  • The bank’s fraud rules blocked the transaction

Settlement declines happen when the bank denies the transaction after a successful authorization. These are much more rare than authorization declines. Learn more about settlement declined transactions in our developer docs.
A processor decline indicates that the customer’s bank has refused the transaction request. Sometimes you can tell why it was declined by reading the response code, but only the customer’s bank can confirm the specific reason.

  • Soft declines: Do not retry the transaction more than 4 times in 16 days
  • 2004 hard decline: Do not retry the transaction
  • 2005 hard decline: Do not retry the transaction with the same payment information
  • 2015 hard decline: Do not retry the transaction

Transactions / Declines 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