What decline code means
A decline code identifies a card payment attempt that was not approved. Payment systems do not all use the same format: one may show a number, while another displays a text description or both. That is why a code alone does not always tell you the exact reason for a decline.
You may see the code or its description in your checkout system, payment terminal, or processor transaction report. It can help you decide whether to retry, use another payment method, or contact the customer. A decline code is narrower than a response code, which also covers results such as approvals and pending transactions.
The rest of this page explains response codes, the broader term for these transaction results.
What a response code is
A response code is a short result sent back after a payment attempt. It tells your point-of-sale system, gateway, or transaction report whether the payment was approved, declined, delayed, or stopped for another reason. Codes can be numeric, letter-based, or displayed as words.
There is no single code list used by every payment system. For example, one system maps 00 to approved, 51 to insufficient funds, and 91 to an unavailable issuer. Another system might show a mapped status such as Refused or Cancelled alongside the raw response from the issuer or card network.
A response code is not always a decline. The result can say partial approval, pending, or approved pending settlement. One gateway’s list also uses 10 for partial approval. Read the full status, not just whether a code field is present.
A response code tells you what happened, but the correct next step depends on the code’s system-specific meaning.
How it affects your business
The code helps you decide what to do next. A 51 points to insufficient funds, while a 91 means the issuer was unavailable. Those outcomes call for different responses: repeating an unavailable-issuer request is not the same as asking a customer to use another payment method.
The code itself is not a standard processing-fee line, and the research does not identify a fee tied to a specific response code. Repeated retries are the cost risk to watch. Mastercard retry guidance says not to retry when Merchant Advice Code 03 says “Do not try again” or code 21 indicates payment cancellation. Retries in those cases can lead to penalty fees.
For insufficient-funds declines, a Mastercard Merchant Advice Code can provide a retry interval. Codes in the guidance include 02 for 72 hours and 24 for 1 hour. The issuer does not return this advice on every payment, so do not invent a retry schedule when no guidance is supplied.
Where interpretation goes wrong
A raw code is not a universal instruction. For example, 04 or 07 can signal that a card should be retained in some card-network response systems, while other systems use different mappings. Use the meaning documented for your own payment setup rather than applying a code list from another provider.
A timeout also does not prove the payment failed. One gateway response mapping uses TIMED_OUT when no bank reply arrived, and SUBMITTED when a response has not yet been received. Confirm the final transaction status before running the payment again, or you could create a duplicate charge.
Use codes to improve payment handling
Keep the raw response and the customer-facing message separate. Raw responses can change, and payment-system guidance says not to expose that technical wording to shoppers. Show a clear message such as “Use another payment method” when the result supports that action.
For online payments, compare the raw code, mapped result, and final transaction status in your payment records. If your integration supports idempotent requests, resubmitting the exact same request can return the original result instead of creating a second operation. That protection depends on the integration and does not make a new payment attempt safe by itself.
What you can actually change
- Map each result. Use the code definitions for your own gateway or payment system. Record the raw response and its plain-English meaning for your staff.
- Stop blind retries. Follow a returned Merchant Advice Code, including codes 03 and 21 that say not to retry. When no retry guidance appears, do not assume a specific wait time.
- Confirm the outcome. Check the final transaction status after a timeout or pending response before submitting a fresh payment. This reduces the risk of charging the customer twice.
Frequently asked questions
Is a decline code the same as a response code?
A decline code is one kind of response code, used when a payment attempt is not approved. Response codes also describe other results, including approvals and pending transactions.
Do decline codes mean the same thing in every payment system?
No. Formats and descriptions differ between payment systems, so do not rely on a number alone to interpret a decline. Use the accompanying description in your transaction report or checkout system.
Where can I find a decline code?
Look in the transaction details in your checkout system, payment terminal, or processor report. The result may appear as a code, a text description, or both.