CentralPay Documentation CentralPay Documentation
  • Informations générales
  • Documentation
  • Développeurs
  • English
    • FrenchSwitch to French
CentralPay Documentation CentralPay Documentation
  • Informations générales
  • Documentation
  • Développeurs
  • English
    • FrenchSwitch to French
Card transaction
  • Folder icon closed Folder open iconGeneral information
  • Folder icon closed Folder open iconCUSTOM payment form
  • Folder icon closed Folder open icon3DS 2.0 Authentication
  • Folder icon closed Folder open iconCard transactiontransaction
  • Folder icon closed Folder open iconRecurring card transactiontransaction
  • Folder icon closed Folder open iconCard transaction via walletApplePay / GooglePay
  • Folder icon closed Folder open iconCard Refund Transactionrefund / credit / dispute
  • Folder icon closed Folder open iconConfirmation email
  • Folder icon closed Folder open iconBank statement descriptor
  • Folder icon closed Folder open iconCurrency management
  • Folder icon closed Folder open iconVirtual Card Management (VCC)
  • Folder icon closed Folder open iconCallbacks, statuses and hooks

Callbacks, statuses and hooks

Estimated reading: 2 minutes

1. Bank Return Codes for Card Transactions

When a card transaction (Transaction) is initiated, an authorization request is submitted to the card-issuing bank. It responds with a code, allowing for the interpretation of the authorization’s acceptance, refusal, and the reason for refusal.

The cardholder’s bank (also called the “issuing bank”) expresses its refusal based on its own choices, which are entirely independent of CentralPay. CentralPay possesses no additional information if a card is declined and has no means of obtaining it.

Main bank return codes:

CodeDescription
A1 – VADS FallbackDSP2 and Soft decline
The bank declines the transaction because it does not have strong authentication (3DS 2.0).
It is necessary to re-process this transaction with 3DS to avoid this code.
57, 3 and 5Generic Bank Refusal
The bank declines without providing a specific status.
This could be an incorrect CVV code or another decision unknown to us.
This status does not confirm that the bank will not accept the authorization after further attempts.
4, 7, 14, 15, 31, 33, 34, 41, 43, 54, 55, 56, 59, 63, 76Suspicion of Fraud or Card Theft
The issuing bank believes its customer is no longer in possession of the card and that it is a case of identity theft.
51, 61Insufficient Funds / Limit Reached
The card has exceeded the authorized limit amount or does not have sufficient funds.
The card may be accepted again later, as limits are calculated on a 7-day rolling basis, so a transaction can certainly be retried the next day.
12Invalid Transaction
The bank declines without providing a specific status. This could be:
– Simply an invalid transaction
– A code 75 from the issuing bank (the card’s PIN code was entered incorrectly too many times).
– An incorrect CVV (provided by the ACS during 3DS authentication)
– Or another decision unknown to us.

Consult the complete list of bank return codes ➝

2. Card Transaction Statuses

Consult Transaction Statuses ➝

Consult Refund Statuses ➝

Consult Credit Statuses ➝

Consult Dispute Statuses ➝

Consult Subscription Statuses ➝

Consult Installment Statuses ➝

3. Webhooks for Card Transactions

Consult Transaction Webhooks ➝

Consult Card Webhooks ➝

Consult Refund Webhooks ➝

Consult Credit Webhooks ➝

Consult Customer Webhooks ➝

Consult Dispute Webhooks ➝

Consult Subscription Webhooks ➝

Consult Installment Statuses ➝

Callbacks, statuses and hooks - PreviousVirtual Card Management (VCC)Next - Callbacks, statuses and hooksBank Transfer Transaction
CONTENU

Doc Contents

Doc Footnotes

Doc Elements

  • Mentions légales
  • Politique de confidentialité

© 2026 CentralPay

You must log in to continue.

Login to CentralPay Documentation

Forgotten account?

Reset your password

Enter your username or email address and we will send you a link to reset your password.

Back to login
  • French