What generic_decline means
Stripe sets outcome.reason = "generic_decline" when the customer's bank rejects the payment but doesn't return a specific reason code. The issuer is intentionally vague — typically because the decline was triggered by an internal fraud model, a velocity rule, or a country mismatch the bank doesn't want to disclose.
Why it matters
Generic declines are one of the most misunderstood codes in Stripe. Teams either ignore them (assuming "the card was bad") or retry them on a schedule (assuming Smart Retries will fix it). Both lose revenue. Most generic declines clear within 48 hours if the cardholder calls their bank or confirms the merchant.
The recovery play
- Pause retries for 24 hours. Hitting the issuer repeatedly looks like card testing.
- Email the customer. "Your bank declined the charge and didn't share a reason — please confirm with them, then we'll retry."
- Offer an update-card link. Many customers prefer switching to a different card over calling their bank.
- Retry after 24–48 hours, not 4 hours. If it fails again, escalate to a human.
Chaser ships this as the Bank declined (generic) play — see all playbooks for the full set.
Frequently asked questions
›What does generic_decline mean in Stripe?
generic_decline is Stripe's catch-all when the customer's bank rejects the charge without giving a specific reason. The issuer chose not to share why — usually for fraud-prevention reasons. It is a soft decline and is often recoverable with the right outreach, but you cannot blindly retry it like insufficient_funds.
›Can I retry a generic_decline?
Not silently. Generic declines are issuer-side judgement calls — retrying within seconds will almost always fail again and may flag the merchant. Wait at least 24 hours and pair the retry with customer outreach asking them to confirm the card with their bank.
›How do I tell generic_decline apart from do_not_honor?
Both are issuer refusals without a clear reason. do_not_honor (decline_code) is more specific and almost always means the bank wants the cardholder to call them. generic_decline (outcome.reason) is broader and can also fire when the issuer's fraud rules trigger. Treat both with the same playbook: contact the customer, don't auto-retry.