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.
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:
Because several parties can be involved, the same payment failure may be described differently across providers or payment methods.
Decline codes are often grouped by the type of issue they describe. Common categories include:
Some codes describe a final rejection, while others describe a temporary or recoverable issue.
Decline codes help businesses decide what should happen after a payment fails. Depending on the code, a business may:
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.
