foxhound
Sign in

Decline code

Lost Card

Stripe declined this payment because the cardholder has reported the card lost. The card is gone, the bank has been told, and the card is dead as a payment instrument regardless of who is presenting the number. Stripe's official definition is direct: "the payment was declined because the card is reported lost." The cardholder (or someone with access to their account) told the issuing bank that the physical card is missing, and the bank shut it down. This is not a temporary hold and not a balance issue. It is a permanent block on that specific card number.

Back to decline codes
lost_cardNever retried
Draft content: this page's explanatory copy is Pass 3 template writing pending a dedicated content pass. The classification badge above and the recovery behavior described below are live, not draft: both come directly from the recovery engine.

Why it happens

On a recurring billing product, `lost_card` almost always shows up on a renewal charge for a card that worked fine in the past. The customer lost their wallet, called their bank, and the bank killed the card the same day, sometimes without the customer remembering every subscription tied to it. The customer usually still wants your product. They just have a new card number they haven't gotten around to updating everywhere yet.

How to fix it

No. The card is closed. Retrying the same card number will fail every time and offers no benefit, since the bank has already made the decision permanent from its side. This is one of the more customer-friendly declines on this list, because the underlying story is usually mundane: a lost wallet, not fraud on the account itself. The right response is to ask the customer for an updated card, since they are very likely to have one soon if they don't already. Stop retrying the old card number immediately, since there's no reason to keep hitting a card the bank has already killed. A clear, low-pressure email explaining that their card was reported lost and asking them to update their payment method tends to work well here, because it is factual and not accusatory.

How Foxhound recovers it

Fraud and security declines are never retried, silently or otherwise. Foxhound sends a gentle, clearly worded email sequence across 30 days that names the situation plainly and points the customer to their card issuer, rather than repeating the same charge against a flag the issuer already raised.

Questions

  • Usually not. It typically means the customer's physical card was lost and they reported it to their bank, which is a routine event unrelated to their standing with you.

  • No. The bank has permanently closed that card number. Retries will keep failing and waste a dunning attempt that could go toward getting an updated card instead.

  • Something plain and non-alarming: their card on file was reported lost, and they need to add a new payment method to keep their subscription active.

  • For retry and automation purposes, yes, both sit in Foxhound's fraud bucket and both stop automated retries and the standard dunning sequence. The underlying customer story is usually very different, which is why careful handling rather than a form email matters here.

  • That depends on your dunning and cancellation settings, not on the decline code itself. The decline code only tells you the card is dead, not what your billing system should do next.

See what this looks like on your account

The free audit shows what Stripe already recovered and what is still dying, no signup required.

Run your free audit