Skip to content

Decline code 41: Lost Card

Jay StevensBy Jay Stevens · Principal EngineerReviewed by Jordan MederichUpdated 3 min read
Summarize with AI

Quick answer

Decline code 41 — “Lost Card” — is a hard decline from the cardholder’s issuing bank: under the ISO 8583 standard, response code 41 tells the merchant the card has been reported lost. The issuer will not authorize the charge, so a retry on the same card never clears it. It’s the same issuer decision Stripe reports as the lost_card decline and that Authorize.net returns under reason code 66 (security/fraud). Recovering it takes customer outreach for a new card, not re-attempts.

What code 41 means

Hard declineDo not retry

Do not retry — code 41 means the issuer has flagged the card as lost. The same number will keep declining until the customer supplies a different card, so this needs outreach, not re-attempts.

Cross-processor equivalents

The same issuer decision surfaces under a different code on every processor. Here is how code 41 maps across the stacks Revatto recovers on.

ISO 8583
Code41
CalledLost Card
Stripe
Codefraudulent
CalledFraudulent
Braintree
Code2014
CalledFraud Suspected
Authorize.net
Code66
CalledFailed gateway securityresponseReasonCode 66; AFDS filters 250–254
NMI
Code252
CalledStolen card
Chargebee
Codefraudulent
CalledFraudulent
Recurly
Codefraudulent
CalledFraudulent
IxoPay
Code2010
CalledSuspected fraudadapterCode 34 also maps here
Shopify
CodeFRAUD
CalledFraud
Whop
Codefraud_decline
CalledSecurity declinenormalized — no processor-specific code (free-text categorized)
Fanbasis
Codefraud_decline
CalledSecurity declinenormalized — matched by substring rule, no processor-specific code

Why it happens

  • The cardholder reported the card lost to their bank, and the issuer flagged the number to block all further authorizations.
  • The card was reissued under a new number after the loss, so the stored card on file is now dead.
  • The issuer is treating recent activity on the lost card as potential fraud and is declining out of caution.
  • The customer’s card on file was never updated after they replaced a misplaced or stolen card.
  • A network account-updater hasn’t yet propagated the replacement card details to the merchant of record.

How to recover it

  1. 1Stop retrying the card immediately — repeated 41s won’t recover the charge and add to your decline ratio.
  2. 2Reach the customer on a channel they actually answer — email and SMS — and explain their card was reported lost so the charge couldn’t go through.
  3. 3Make updating the card on file effortless: a single secure link to add the replacement card, then re-run the charge on the new card.
  4. 4
    When the customer goes quiet, a real person — not another automated email — works the card update directly. That AI-plus-human handoff is exactly what Revatto does for you: AI-timed retries where the API supports it, plus email, SMS, and human outreach, fully done-for-you. You only pay if it works — 20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime.See how Revatto recovers 41declines →

See what Revatto would recover for you

Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.

See Your Recovery Potential

Frequently asked questions