Stripe Decline Code · Glossary
lost_card is a hard decline fired when the customer's issuing bank has been notified that the physical card is lost — the card has been permanently flagged at the network level and will reject every future charge attempt regardless of timing, amount, or merchant.
What It Means
What It Means
lost_card is a hard decline fired when the customer's issuing bank has been notified that the physical card is lost — the card has been permanently flagged at the network level and will reject every future charge attempt regardless of timing, amount, or merchant. Critically, Stripe explicitly instructs merchants never to reveal this specific reason to the customer — you must present it as a generic decline, because the person attempting the transaction may not be the legitimate cardholder.
Not sure if this code is recoverable for your specific situation? Use the Stripe Failure Lookup →
Why It Happens
Why It Happens
What NOT to Do
What NOT to Do
✕ Never tell the customer their card was reported lost
This is Stripe's explicit official guidance — and it's not just a courtesy rule. If a fraudster is attempting to use the card, disclosing the lost_card status tips them off and could enable social engineering attacks. Always surface this as a generic payment failure to the person attempting the transaction.
✕ Don't retry — not even once
lost_card is a permanent hard decline. The card is dead at the network level — no retry interval, no paycheck cycle logic, no "try one more time" automation will ever succeed. Every retry wastes an API call, adds a failed attempt to your merchant health record, and does exactly zero for recovery.
✕ Don't treat it identically to expired_card
While both require a new payment method, expired_card is a predictable lifecycle event you can pre-empt. lost_card is sudden, unannounced, and has a fraud-signal dimension that expired_card never has. Your response workflow, email tone, and internal flagging logic must be completely separate for these two codes.
Retry Timing
Retry Timing
There is no retry timing for lost_card — this is a zero-retry, new-payment-method-only recovery path.
Recovery Benchmark
Recovery Benchmark
| Metric | Result |
|---|---|
| Overall recovery rate | 10–20% |
| Recovery from legitimate customers (card replaced) | 30–40% of the recoverable subset |
| Recovery via alternate payment method offer | +8–12% additional lift |
| Recovery with blind retries | ~0% |
| Non-recoverable (fraud attempts, true card loss) | ~60–70% of all occurrences |
| Median recovery window | 3–7 days if customer is legitimate |
A 15–20% overall recovery rate on lost_card is realistically the ceiling — because a significant portion of occurrences involve either genuine card abandonment or fraud scenarios where the "customer" has no intention of updating a legitimate payment method. Focus your energy on speed of outreach and frictionless alternate payment method capture, not retry optimization.
At Scale
At Scale
Automated
Manual Escalation
FAQs
FAQs
What does the Stripe lost_card decline code mean?
The lost_card decline code means the customer's issuing bank has flagged the card as reported lost, permanently blocking all future charge attempts on that card number. It is a hard decline — no retry will ever succeed — and Stripe recommends never disclosing the specific lost_card reason to the customer, instead presenting it as a generic decline.
What are the most common causes of a lost_card error in Stripe?
The most common causes are: the customer reported their card lost to the bank and received a replacement with a new card number; the bank proactively flagged the card after detecting suspicious activity; or the old card remained on file in Stripe after the customer received a replacement card but forgot to update their payment method.
Should I tell my customer their card was reported lost?
No. Stripe's official guidance is to never disclose the lost_card reason to the person attempting the transaction. The person making the payment may not be the legitimate cardholder. Always present it as a generic payment failure and direct the customer to update their payment method.
Should I retry a payment after a Stripe lost_card decline?
Never. lost_card is a permanent hard decline — the card is blocked at the network level and every retry will fail with zero exception. Remove this code from all retry schedulers immediately and focus entirely on getting the customer to add a new payment method.
What is the recovery rate for Stripe lost_card failures?
Overall recovery rates for lost_card are 10–20%, significantly lower than soft declines. Among legitimate customers who simply need to update to their replacement card, 30–40% recovery is achievable with fast, neutral-toned outreach and an alternate payment method offer. A large portion of lost_card failures involve true card abandonment or fraud scenarios that are not recoverable.
What to do next
You are here
lost_card
Decline code reference
Check recoverability
Stripe Failure Lookup
See what's recoverable — and what isn't →
Then
Sign up for Recurflux
Automate recovery for every decline code →
Before you retry
Before you retry
Most lost_card failures are retried on the wrong schedule — which recovers the payment about 30% of the time. The other 70% leaves permanently. See what this code is actually costing at your MRR before deciding how to handle it.
Stop leaving revenue on the table
Recurflux handles code-specific retry scheduling, adaptive dunning, and dispute intelligence across all 30 Stripe decline codes. Connect in under 5 minutes.