Lost Card
Category: Lost/Stolen (Pickup) Retryable: no
Variability
Meaning varies by network
Take the card brand and processor into account before treating this as diagnostic.
Retryable
no
Namespace: Legacy/conventional ISO 8583 field-39 code as implemented by card networks and processors — not the current ISO 8583:2023 Annex D table.
What this code typically means
The card has been reported lost by the cardholder. Stripe exposes this as a distinct lost_card decline code, but Adyen's public refusal-reason list doesn't break lost and stolen out separately — both fold into its blocked/restricted buckets — a concrete example of how even a seemingly unambiguous code isn't handled with the same granularity everywhere.
What to do about it
Merchant action
Hard decline. Do not retry. For recurring billing, stop the retry schedule immediately and request a new payment method — a lost card will not become valid again on this number.
Customer-facing guidance
Don't disclose 'lost card' to the customer directly; Stripe explicitly recommends presenting this the same as a generic decline, since the specific reason is privacy-sensitive account information.
What's happening on the issuer's side
Card has been deactivated in the issuer's system following a loss report.
Cross-processor equivalents
stripe: lost_card
commonly treated as equivalent
Cross-processor mappings are commonly treated as equivalent, not identical — every processor's own documentation notes lossy or partial mapping between raw network codes and its own vocabulary.
Sources
- Stripe — Card decline codes — fetched 2026-08-20
- Worldpay ISO 8583 Reference Guide V2.58 — Debit/Credit Response Code Mappings — fetched 2026-08-20
- ISO 8583:2023 Annex D — Action codes (current standard, 4-digit) — fetched 2026-08-20
Concept + retry philosophy
Decline Codes: why they're opaque and how to retry them