• France
status page
demonstrations
assistance
FAQContact support
Search
Categories
Tags
English
French
English
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
Snippets
Payment methods
Plugins
Guides
Merchant Back Office
Functional guides

Refusal related to the authorization request

The red exclamation mark to the left of the Details tab indicates that the reason for rejection is related to the authorization request.

 The payment gateway is never the source of these errors. The buyer’s bank refuses the payment with an error code.

This error code depends on the payment method used and the corresponding network.

Example:

  • Code 51: Insufficient balance or exceeded credit limit.

The merchant can communicate the transaction details (error code, date, time of the transaction, etc.) to the buyer. The buyer can contact their bank to understand the reasons of the refusal.

Here is a list of reasons and a description of the most frequently occurring codes.

Value Description
03

Invalid acceptor

This code is sent by the card issuer. It refers to a configuration problem on authorization servers. (e.g. closed contract, incorrect MCC declared, etc.).

To find out the specific reason of the rejection, the buyer must contact his or her bank.
05 Do not honor

This code is sent by the card issuer. This code is used in the following cases:

  • Invalid expiry date
  • Invalid CVV
  • Exceeded credit limit
  • Insufficient funds (etc.)
To find out the specific reason of the rejection, the buyer must contact his or her bank.
51 Insufficient balance or exceeded credit limit

This code is sent by the card issuer. This code appears if the funds on the buyer’s account are insufficient for making the purchase.

To find out the specific reason of the rejection, the buyer must contact his or her bank.
56 Card absent from the file

This code is sent by the card issuer.

The entered card number is incorrect or the card number + expiration date combination does not exist.
57 Transaction not allowed for this cardholder

This code is sent by the card issuer. This code is used in the following cases:

  • The buyer attempts to make an online payment with a cash withdrawal card
  • The authorized payment limit is exceeded
To find out the specific reason of the rejection, the buyer must contact his or her bank.
59 Suspected fraud

This code is sent by the card issuer. This code appears when an incorrect CVV code or expiration date has been entered several times.

To find out the specific reason of the rejection, the buyer must contact his or her bank.
60

The acceptor of the card must contact the acquirer

This code is sent by the card issuer. It refers to a configuration problem on authorization servers. It is used when the merchant ID does not correspond to the used sales channel (e.g.: an e-commerce transaction with a distant sale contract with manual entry of contract data).

Contact the customer service to resolve the problem.
81

Unsecured payment is not accepted by the issuer

This code is sent by the card issuer. After receiving this code, the payment gateway automatically makes a new payment attempt with 3D Secure authentication, when possible.

For more information about the reasons for rejection, the complete list of returned codes can be found in the vads_auth_result chapter of our data dictionary.

 

Before taking any action, check that the buyer has not made another successful payment attempt with another payment method. Simply check the Multiple attempts tab.

© 2025 {'|'} All rights reserved to Scellius
25.18-1.11