Decline codes

What are decline codes?

Decline codes are response codes that explain why a payment transaction was rejected or could not be completed. They are returned by an issuer, acquirer, processor, payment provider, card network, or payment method after a failed payment attempt.

A decline code helps the merchant or payment system understand what happened and what action, if any, should be taken next. In simple terms, decline codes are payment failure reasons written in a standardized or provider-specific code format.

How decline codes work

When a customer submits a payment, the transaction is sent through the payment flow for processing and authorization. If the payment cannot be completed, the system returns a response code that may indicate the card has insufficient funds, the issuer declined the transaction, authentication is required, the card details are invalid, the transaction was blocked for risk reasons, or a technical issue occurred.

Decline codes can come from different parts of the payment chain, including:

• issuing bank;
• acquiring bank;
• payment processor;
• payment service provider;
• card network;
• fraud or risk system;
• payment method provider.

Because several parties can be involved, the same payment failure may be described differently across providers or payment methods.

Common types of decline codes

Decline codes are often grouped by the type of issue they describe. Common categories include:

• insufficient funds — the customer does not have enough available balance or credit;
• invalid payment data — card number, expiry date, CVV, or other details are incorrect;
• authentication required — the customer must complete 3D Secure or another verification step;
• suspected fraud — the transaction was blocked because of risk signals;
• issuer decline — the issuing bank rejected the transaction without giving a detailed reason;
• expired or blocked card — the card is no longer valid or cannot be used;
• transaction limit reached — the payment exceeds a limit set by the issuer, provider, merchant, or payment method;
• unsupported transaction — the currency, country, method, or transaction type is not supported;
• technical error — the transaction failed because of a timeout, provider downtime, or a processing issue.

Some codes describe a final rejection, while others describe a temporary or recoverable issue.

How businesses use decline codes

Decline codes help businesses decide what should happen after a payment fails. Depending on the code, a business may:

• retry the payment later;
• cascade the payment to another provider;
• ask the customer to complete authentication;
• suggest another payment method;
• request updated card details;
• block the transaction for risk reasons;
• show a clearer payment error message;
• investigate provider or issuer performance;
• adjust routing, fraud, or authentication logic.

Decline codes are also useful for payment reporting. They help teams track failed payments by issuer, provider, country, currency, payment method, card type, transaction route, and customer segment.

Corefy helps payment teams monitor transaction statuses, provider responses, decline reasons, and routing outcomes across multiple payment providers and methods. This gives teams a clearer view of failed payments and helps them configure more controlled routing, cascading, and recovery logic.