When a card payment fails, the issuer sends back a response code with the decline. There are two layers you will see. The raw network codeis a two-character code from the card network, such as Visa's 05 or 51. Your processor may translate it into its owndecline code, such as Stripe's do_not_honor or insufficient_funds. Stripe notes that the meaning of a raw code differs by network, so always read it together with the card brand.
The meanings below come from Stripe's published network decline code tables and its decline code list. The retry rules come from Visa's own rulebook, Table 7-2 of the Visa Core Rules and Visa Product and Service Rules, October 24, 2026 edition.
Visa's four categories, and the retry rules
Visa sorts every decline response code into one of four categories, and the category decides whether, and how often, you may ask again for the same card:
| Category | Meaning | Merchant reattempt limit |
|---|---|---|
| 1 | Issuer will never approve | Never resubmit an authorization for the same payment credential |
| 2 | Issuer cannot approve at this time | Up to 20 attempts in 30 days |
| 3 | Data quality: revalidate payment information | Up to 20 attempts in 30 days |
| 4 | Generic response codes (all other decline codes) | Up to 20 attempts in 30 days |
Visa also says that a merchant reattempting after a decline must not manipulate data in the original request, such as the MCC, the merchant country or the e-commerce indicator. Stripe, for its part, recommends no more than eight retries for charges that permit them, because issuers can read extra retries as fraud.
Common Visa decline codes
Explanation from Stripe's Visa table; Stripe code where Stripe's list has a direct equivalent; Visa category from Table 7-2.
| Code | Meaning | Similar Stripe code | Visa category |
|---|---|---|---|
05 | Don't honor | do_not_honor | 4: generic |
51 | Not sufficient funds | insufficient_funds | 2: cannot approve now |
54 | Expired card or expiration date is missing | expired_card | 3: data quality |
14 | Invalid account number (no such number) | incorrect_number | 1: never approve |
N7 | Decline for CVV2 failure | incorrect_cvc | 3: data quality |
82 | Negative CAM, dCVV, iCVV, or CVV results | 3: data quality | |
59 | Suspected fraud | 2: cannot approve now | |
61 | Exceeds approval amount limit | 2: cannot approve now | |
62 | Restricted card (card invalid in this region or country) | restricted_card | 2: cannot approve now |
65 | Exceeds withdrawal frequency limit | 2: cannot approve now | |
57 | Transaction not permitted to cardholder | 1: never approve | |
04 | Pick up card (no fraud) | pickup_card | 1: never approve |
07 | Pick up card, special condition (fraud account) | 1: never approve | |
41 | Lost card, pick up (fraud account) | lost_card | 1: never approve |
43 | Stolen card, pick up (fraud account) | stolen_card | 1: never approve |
46 | Closed account | 1: never approve | |
R0 / R1 / R3 | Stop this payment / stop all future payments / stop all merchants | 1: never approve | |
12 | Invalid transaction | 1: never approve | |
03 | Invalid merchant | 2: cannot approve now | |
19 | Re-enter transaction | reenter_transaction | 2: cannot approve now |
91 | Issuer or switch inoperative | issuer_not_available | 2: cannot approve now |
96 | System malfunction | 2: cannot approve now | |
93 | Transaction can't be completed, violation of law | 2: cannot approve now | |
5C | Transaction not supported/blocked by issuer | 2: cannot approve now | |
9G | Blocked by cardholder/contact cardholder | 2: cannot approve now | |
1A | Additional customer authentication required | authentication_required | 3: data quality (CEMEA and Europe) |
Visa's Table 7-2 also lists 15 (no such issuer) in Category 1; 39, 52, 53, 75, 78, 86, N3 and N4 in Category 2; and 55 and 6P in Category 3, with 70 (PIN data required) in Category 3 only in the CEMEA and Europe regions. The Stripe column is a guide to the closest Stripe decline code, not an official mapping; Stripe returns its own code based on what it receives.
Mastercard: response codes plus advice codes
Mastercard pairs some response codes with a Merchant Advice Code (MAC), and Stripe reports it as network_advice_code. The same response code can mean different things depending on the MAC. A few rows from Stripe's Mastercard table:
| Code | Stripe's explanation |
|---|---|
05 (MAC 01, 03, 21) | Don't honor |
51 (MAC 01, 02, 03) | Insufficient funds / over credit limit |
54 (MAC 01, 03) | Expired card |
79 (MAC 01) | Expired card (lifecycle decline; updated card data available) |
79 (MAC 02) | Invalid credentials (lifecycle decline; may retry later) |
79 (MAC 03) | Account credentials not found (don't retry) |
83 (MAC 02) | Retry the transaction later |
82 (MAC 03) | Invalid transaction or merchant, don't retry |
65 | Exceeds withdrawal count limit (or Identity Check soft-decline of EMV 3DS authentication) |
Stripe decline codes and what to tell the customer
Stripe's list has 48 card decline codes (including two deprecated ones). The ones a store sees most, with Stripe's next step:
| Stripe code | Meaning | Next step |
|---|---|---|
generic_decline | Declined for an unknown reason, or blocked by Stripe Radar or Adaptive Acceptance | Customer contacts their card issuer |
do_not_honor | Declined for an unknown reason | Customer contacts their card issuer |
insufficient_funds | Not enough funds | Customer uses another payment method |
card_velocity_exceeded | Balance, credit limit or transaction amount limit exceeded | Customer contacts their card issuer |
incorrect_cvc, incorrect_number, incorrect_zip | The details entered are wrong | Customer tries again with the correct details |
expired_card | The card has expired | Customer uses another card |
authentication_required | The issuer requires authentication such as 3D Secure | Run authentication and let the customer retry |
card_not_supported | The card does not support this type of purchase | Customer checks with their issuer |
processing_error, issuer_not_available | An error, or the issuer could not be reached | Try again; if it fails, customer contacts issuer |
fraudulent, lost_card, stolen_card, merchant_blacklist | Suspected fraud, card reported lost or stolen, or on your block list | Show the customer a generic decline, not the reason |
Stripe also returns an advice_code with three values: do_not_try_again, try_again_later andconfirm_card_data. If you retry automatically, use it as the switch.
Turning decline codes into fewer lost sales
- Fix data declines at checkout. Wrong CVC, number, postal code or expiry are the declines a customer can solve in seconds, if your error message says what to fix.
- Collect CVC and postal code. Stripe says this helps avoid declines from suspected fraud, and 3D Secure can lower decline rates where it is supported.
- Respect Category 1. Visa's rules forbid resubmitting a lost, stolen or closed card, and Stripe warns that issuers can read extra retries as possible fraud.
- Space out retries. For subscriptions, spread retries across days rather than minutes, so you stay inside Visa's 20-in-30-days limit and Stripe's suggested maximum of eight. Stripe Billing's Smart Retries picks the timing for you.
- Answer the customer quickly. A buyer whose payment failed often writes in asking whether they were charged. Shopify notes that customers can mistake authorization holds for duplicate charges, and a confused buyer is a future "duplicate" or "unrecognized" dispute. Thecustomer service email templates include replies for this.
Declines are the issuer saying no before the money moves; chargebacks are the issuer taking it back afterwards. If a decline code is what you are investigating because a declined charge was disputed anyway, see Visa 11.2 Declined Authorization.
Questions
What does decline code 05 mean?
05 is 'Don't honor' (do not honor). The issuer declined without giving a specific reason. Stripe reports it as do_not_honor and says the customer needs to contact their card issuer. Visa puts it in Category 4, generic response codes, which may be retried up to 20 times in 30 days.
What does decline code 51 mean?
51 is 'Not sufficient funds': the card does not have the balance or credit available. Stripe calls it insufficient_funds and suggests the customer use another payment method. Visa lists 51 in Category 2, issuer cannot approve at this time, so a retry later is permitted within the 20-in-30-days limit.
Which decline codes should never be retried?
Visa's Category 1 codes, where the issuer will never approve: 04, 07, 12, 14, 15, 41, 43, 46, 57, R0, R1 and R3. After one of these, Visa says a merchant must never resubmit an authorization for the same payment credential.
How many times can I retry a declined card?
Under Visa's rules (October 2026 edition), never for Category 1 codes, and up to 20 attempts in 30 days for Categories 2, 3 and 4. Stripe recommends at most eight retries for charges that permit retries, and warns that issuers may see extra retries as possible fraud.
Should I tell the customer the exact decline reason?
Not for fraud-related declines. Stripe says to present fraudulent, lost_card, stolen_card and merchant_blacklist declines to the customer as a generic decline. For data errors such as a wrong CVC or expiry, telling the customer what to fix is the point.
Sources: Visa Core Rules and Visa Product and Service Rules (October 24, 2026 edition, section 7.3.6.3 and Table 7-2, Decline Response Code Use; section 1.7.2.1); StripeNetwork decline codes,Stripe decline codes andCard declines; Shopify Help CenterResponding to chargebacks. Checked October 30, 2026.
Keep the evidence before you need it
Rebutdesk is an open-source helpdesk where Stripe and PayPal disputes open inside the buyer's support case, so the conversation, refunds and shipping events are already in order when the deadline starts. See how it works.
14 days free, no card needed. Already have an account? Sign in
More guides
- Chargeback vs refund: what's the difference for merchants?
- Chargeback fees: who pays and how much
- PayPal Seller Protection: what it covers and how to qualify
- How to write a chargeback rebuttal letter
- How to respond to a Stripe dispute
- PayPal disputes for sellers: how to respond and win
- Chargeback time limits by card network
- Chargeback representment: what it is and how to win it
- Pre-arbitration chargebacks: what happens after your first response
- Billing descriptors: how to stop 'I don't recognize this charge' disputes
- Chargeback alerts: Ethoca, Verifi CDRN and Rapid Dispute Resolution
- Visa VAMP: the ratio, thresholds and fees for merchants
- Visa Compelling Evidence 3.0: how CE 3.0 works for fraud disputes
- Customer service email templates for online stores
- How does a chargeback work? The process from dispute to decision
- American Express chargebacks: how inquiries and disputes work
- PayPal chargebacks: what happens when the buyer goes to their bank
- Shopify chargebacks: how to respond and what Shopify does for you
- Friendly fraud: what it is, how to spot it and how to win
- Ecommerce customer service: a playbook that also prevents chargebacks