Decline Reason Codes

Transaction refusal codes constitute a standardized classification system designed to communicate the precise reason for payment authorization failures within the electronic payment processing infrastructure. This reference documentation establishes a comprehensive framework for interpreting declined transactions across multiple failure scenarios.

Decline Codes

The table below describes each Decline Code in more detail.

Refusal Reason Code

Refusal Reason

Description

0

(none)

Sometimes refusalReasonCode: 0 is returned along with resultCode: Authorised. When this happens, ignore the refusal reason code. The transaction succeeded.

2

Refused

The transaction was refused.

3

Referral

Referrals.

4

Acquirer Error

The transaction did not go through due to an error that occurred on the acquirer's end.

5

Blocked Card

The card used for the transaction is blocked, therefore unusable.

6

Expired Card

The card used for the transaction has expired, therefore unusable.

7

Invalid Amount

An amount mismatch occurred during the transaction process.

8

Invalid Card Number

The specified card number is incorrect or invalid.

9

Issuer Unavailable

It is not possible to contact the consumer's bank to authorise the transaction.

10

Not supported

The shopper's bank does not support or allow this type of transaction.

11

3D Not Authenticated

3D Secure authentication was not executed, or it did not execute successfully.

12

Not enough balance

The card does not have enough money to cover the payable amount.

14

Acquirer Fraud

Possible fraud.

15

Cancelled

The transaction was cancelled.

16

Shopper Cancelled

The consumer cancelled the transaction before it was completed.

17

Invalid Pin

The specified PIN is incorrect or invalid.

18

Pin tries exceeded

The consumer entered an incorrect PIN more than three times consecutively.

19

Pin validation not possible

It is not possible to validate the specified PIN number.

20

FRAUD

The pre-authorisation risk checks resulted in a fraud score of 100 or more. Therefore, the transaction was flagged as fraudulent and was refused.

21

Not Submitted

The transaction was not submitted correctly for processing.

22

FRAUD-CANCELLED

The sum of pre-authorisation and post-authorisation risk checks resulted in a fraud score of 100 or more. Therefore, the transaction was flagged as fraudulent and was refused.

23

Transaction Not Permitted

The following declined codes are mapped to this refusal reason:

  • 57: Transaction not permitted to issuer/cardholder
  • 57: Transaction not allowed for this merchant
  • 58: Transaction not permitted to acquirer/terminal

24

CVC Declined

The specified CVC (card security code) is invalid.

25

Restricted Card

The following decline codes are mapped to this refusal reason: "62: Restricted Card" "62: Invalid card in this country"

26

Revocation Of Auth

Indicates that the consumer requested to stop a subscription. Decline codes such as the following are mapped to this refusal reason: "R1: Revocation of Authorization Order" "R3: Revocation of All Authorizations Order" "R0: Stop Payment Order"

27

Declined Non Generic

This response maps all those response codes that cannot be reliably mapped. This makes it easier to tell generic declines (for example, Mastercard "05: Do not honor" response) from more specific ones.

28

Withdrawal amount exceeded

The transaction amount was higher than the withdrawal amount permitted for the consumer's card.

29

Withdrawal count exceeded

The consumerexceeded the number of withdrawals that is permitted for the consumer's card.

31

Issuer Suspected Fraud

Issuer reported the transaction as suspected fraud.

32

AVS Declined

The address data the consumer entered is incorrect.

33

Card requires online pin

The consumer's bank requires the consumer to enter the PIN.

34

No checking account available on Card

The consumer's bank requires a checking account to complete the purchase.

35

No savings account available on Card

The consumer's bank requires a savings account to complete the purchase.

36

Mobile pin required

The consumer's bank requires the consumer to enter a mobile PIN.

37

Contactless fallback

The consumer abandoned the transaction after attempting a contactless payment and being prompted to try a different card entry method (PIN or swipe).

38

Authentication required

The issuer declined the authentication exemption request and requires authentication for the transaction. Retry with 3D Secure.

39

RReq not received from DS

The issuer or the scheme wasn't able to communicate the outcome via RReq.

40

Current AID is in Penalty Box

The payment network is currently unavailable. Retry the transaction with a different payment method.

41

CVM Required Restart Payment

A PIN or signature is required. Retry the transaction.

42

3DS Authentication Error

The 3D Secure authentication failed due to an issue at the card network or issuer. Retry the transaction, or try again with a different payment method.

46

Transaction blocked by Adyen to prevent excessive retry fees

Adyen's excessive retry prevention service blocked the transaction to make sure that you are not charged penalty fees.

1062

Unauthorized – Machine is not active

Machine is not found or not active.

1063

Unauthorized – VAS eCOM provider is not active or not exist

VAS is not found or not active.

1064

Unauthorized – VAS SDK integrator is not active or not exist

VAS is not found or not active.

1065

Unauthorized – Token is not valid

Expired token.

1066

Unauthorized - Authentication failed

Other reason.

1067

The request failed validation because required fields are missing.

When getting a request that is missing a mandatory field.

1068

The request was declined 81

When the request is rejected due to risk.

1069

Immediate decline from the provider

980

Unauthorized - Authentication failed

Failed.

981

Unauthorized – Machine is not active

982

Unauthorized – VAS eCOM provider is not active or not exist

983

Unauthorized – VAS SDK integrator is not active or not exist

601

Card token is not valid

In the case the Token is not approved/exists in Nayax DB.

602

Card Token is pending

In the event that we have yet to receive a response from the billing provider.

603

Transaction not found

In the event we couldn’t locate the transaction that the merchant asked us to check.

604

Transaction is pending

In the event that the last status we received from the billing provider was “Pending”.

33

Failed to Authenticate

Invalid cipher (structure or value).

34

Decryption Failure

The provided cipher decryption failed.

984

Unauthorized – Token is not valid

The TokenId was not found for EcmVas.

998

Validation error

ValidateMerchant had an exception.

992

Timeout

997

Did not receive mandatory parameters

999

General error

29

Invalid Token

If Token exists, check failed.

29

Invalid Token

If Token is not “Active”.

29

Invalid Token

If Token ID is not associated with Actor ID.

29

Invalid Token

If Token ID is not associated to VAS eCOM.

29

Invalid Token

If Random ≠ Random.

29

Expired Request

Timestamp ≥ 5 minutes.

See Also