On this page
In short
- Most declines come from the customer's bank, and only the bank can explain them.
- Stripe tells you not to share detail for fraud-type codes, and to present them like a generic decline.
- A blocked payment never reaches the bank, so it is not the bank's decision.
Three kinds of failure
Stripe's declines page says there are three reasons a payment fails. An issuer decline means the customer's bank or card provider said no, based on signals such as spending habits, balance and card data. A blocked payment means Stripe Radar stopped a high risk payment without asking the bank. An invalid request means the payment details sent to Stripe were wrong. You can see the type in the Dashboard on the payment.
| Decline code | Stripe's meaning | Stripe's next step |
|---|---|---|
| insufficient_funds | Not enough money on the card | Customer uses another payment method |
| incorrect_cvc | Security code wrong | Customer tries again |
| expired_card | Card has expired | Customer uses another card |
| generic_decline | Unknown reason, or Radar blocked it | Customer contacts the issuer |
| offline_pin_required | Card needs a PIN | Insert the card and enter PIN |
Reading the code
Stripe publishes a list of decline codes with a suggested next step. Many say the customer needs to contact their card issuer. Some are simple: wrong CVC or card number means try again, expired card means use another card, insufficient funds means use another method. For codes such as fraudulent, lost_card and stolen_card, Stripe says not to report detail to the customer and to present it the same way as a generic decline. For generic_decline, Stripe says the reason is unknown, or that Radar or Adaptive Acceptance blocked it.
What to do at the counter
- Look at the payment in the Dashboard to see whether it was an issuer decline or a block.
- If the issuer declined, ask the customer to call the number on the back of the card, or offer another card.
- If a card was tapped, hold it to the reader until it reads. Stripe notes some cards need a PIN or insertion, and offline_pin_required means exactly that.
- If the payment was blocked by a rule you set, and you recognize the customer, see our Stripe Radar page.
Worked example
Example: a $150 boutique purchase declines with generic_decline. The customer insists the card is fine. In the Dashboard the outcome says blocked, not issuer declined, so the bank never saw it. The customer may even see a pending hold on their statement. Stripe says that for some card types the issuer's authorization can appear on the statement, though Stripe has not charged the amount, and it typically drops off within a few days. The owner offers another card and reviews the rule later. Details are invented for illustration.
What to avoid
- Do not tell a customer their card is stolen or fraudulent. Stripe advises against sharing that detail.
- Do not keep retrying the same card many times. Stripe mentions retry penalties on some pricing plans and says failed retries skew your decline-rate numbers.
- Do not blame the reader before checking the code.
How a second way to take cards helps
MazalPOS payments run through your store's own Stripe account, so Stripe's declines and risk checks apply the same way. When a card fails at the register you can take cash, another card, or send a pay link (3% fee), and the sale stays on one ticket. Refunds can be done from the register, manager phone or back office. See payments.
Common questions
Stripe says it is an issuer decline, a Radar block, or an invalid request. The payment details in the Dashboard show which.
Stripe says the card was declined for an unknown reason, or Radar or Adaptive Acceptance blocked it.
For fraud-related codes Stripe says no, present it like a generic decline.
No. Card approval depends on the bank and Stripe. MazalPOS gives you other ways to complete the sale.
Sources
Checked on 2026-11-08. Rules and prices change, so confirm on the official page before you act.
Related
Stripe Radar blocking good customers: what to doStripe card reader not connecting or Tap to Pay not working: what to checkStripe chargeback: what to do when a customer disputes a payment
Written by Mike Akop, founder of MazalPOS. We build and support the register, online store and staff app that stores from Las Vegas to Honolulu run on. Questions? Talk to a real person.
