Error codes
Hard decline
Stripe
lost_card
The payment was declined because the card is reported lost.
What does lost_card mean?
The lost_card decline code is returned when the cardholder has reported the card as lost to their issuing bank. The issuer has placed a block on the specific card number, and any subsequent attempts will continue to fail until the customer activates a replacement card.
This decline should be handled carefully for security reasons. The card in question may be in the possession of someone other than the legitimate cardholder, so Stripe explicitly recommends not disclosing the specific reason to the customer — display it as a generic decline instead.
Is it a soft or hard decline?
lost_card is a hard decline. The specific card number is blocked permanently and no amount of retries will recover the transaction using the same credentials. Recovery requires updated card details — typically the replacement card the issuer has sent or will send to the cardholder.
Common root causes
The cardholder reported the card as physically lost
The cardholder lost a wallet or bag containing the card
The card was lost in the mail before activation
A family member or secondary user reported the card lost
Recommended recovery steps
Never retry the same card. A blocked card will never succeed on the same PAN.
Never disclose
lost_cardto the customer. Show a generic decline instead, for security.Query account updater services. Visa Account Updater and Mastercard Automatic Billing Updater will return new credentials once the replacement card is activated.
Try a backup payment method on file, if one exists.
If outreach is required, keep it generic. Ask the customer to update payment details without mentioning fraud or loss.
How FlyCode handles lost_card
FlyCode automatically enrolls every merchant in Visa Account Updater and Mastercard Automatic Billing Updater. When a lost_card decline occurs, FlyCode queries the networks in real time to check whether the cardholder has received and activated a replacement card. If so, the stored credentials are refreshed silently and the charge proceeds — the customer never sees a failed payment notification.
For cards that have not yet been replaced, FlyCode routes the customer to a non-alarming payment update flow and uses backup payment methods where available. The combined approach recovers a significant portion of lost_card declines that would otherwise result in immediate subscription cancellation — all without exposing security-sensitive details to the customer.
What does lost_card mean?
The lost_card decline code is returned when the cardholder has reported the card as lost to their issuing bank. The issuer has placed a block on the specific card number, and any subsequent attempts will continue to fail until the customer activates a replacement card.
This decline should be handled carefully for security reasons. The card in question may be in the possession of someone other than the legitimate cardholder, so Stripe explicitly recommends not disclosing the specific reason to the customer — display it as a generic decline instead.
Is it a soft or hard decline?
lost_card is a hard decline. The specific card number is blocked permanently and no amount of retries will recover the transaction using the same credentials. Recovery requires updated card details — typically the replacement card the issuer has sent or will send to the cardholder.
Common root causes
The cardholder reported the card as physically lost
The cardholder lost a wallet or bag containing the card
The card was lost in the mail before activation
A family member or secondary user reported the card lost
Recommended recovery steps
Never retry the same card. A blocked card will never succeed on the same PAN.
Never disclose
lost_cardto the customer. Show a generic decline instead, for security.Query account updater services. Visa Account Updater and Mastercard Automatic Billing Updater will return new credentials once the replacement card is activated.
Try a backup payment method on file, if one exists.
If outreach is required, keep it generic. Ask the customer to update payment details without mentioning fraud or loss.
How FlyCode handles lost_card
FlyCode automatically enrolls every merchant in Visa Account Updater and Mastercard Automatic Billing Updater. When a lost_card decline occurs, FlyCode queries the networks in real time to check whether the cardholder has received and activated a replacement card. If so, the stored credentials are refreshed silently and the charge proceeds — the customer never sees a failed payment notification.
For cards that have not yet been replaced, FlyCode routes the customer to a non-alarming payment update flow and uses backup payment methods where available. The combined approach recovers a significant portion of lost_card declines that would otherwise result in immediate subscription cancellation — all without exposing security-sensitive details to the customer.
What does lost_card mean?
The lost_card decline code is returned when the cardholder has reported the card as lost to their issuing bank. The issuer has placed a block on the specific card number, and any subsequent attempts will continue to fail until the customer activates a replacement card.
This decline should be handled carefully for security reasons. The card in question may be in the possession of someone other than the legitimate cardholder, so Stripe explicitly recommends not disclosing the specific reason to the customer — display it as a generic decline instead.
Is it a soft or hard decline?
lost_card is a hard decline. The specific card number is blocked permanently and no amount of retries will recover the transaction using the same credentials. Recovery requires updated card details — typically the replacement card the issuer has sent or will send to the cardholder.
Common root causes
The cardholder reported the card as physically lost
The cardholder lost a wallet or bag containing the card
The card was lost in the mail before activation
A family member or secondary user reported the card lost
Recommended recovery steps
Never retry the same card. A blocked card will never succeed on the same PAN.
Never disclose
lost_cardto the customer. Show a generic decline instead, for security.Query account updater services. Visa Account Updater and Mastercard Automatic Billing Updater will return new credentials once the replacement card is activated.
Try a backup payment method on file, if one exists.
If outreach is required, keep it generic. Ask the customer to update payment details without mentioning fraud or loss.
How FlyCode handles lost_card
FlyCode automatically enrolls every merchant in Visa Account Updater and Mastercard Automatic Billing Updater. When a lost_card decline occurs, FlyCode queries the networks in real time to check whether the cardholder has received and activated a replacement card. If so, the stored credentials are refreshed silently and the charge proceeds — the customer never sees a failed payment notification.
For cards that have not yet been replaced, FlyCode routes the customer to a non-alarming payment update flow and uses backup payment methods where available. The combined approach recovers a significant portion of lost_card declines that would otherwise result in immediate subscription cancellation — all without exposing security-sensitive details to the customer.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
Is lost_card a soft or hard decline?
Should I tell the customer their card is reported lost?
Hard decline. The specific card number is permanently blocked by the issuer, so retrying with the same card will never succeed. Recovery requires new card credentials, typically via account updater services or customer action.
How does FlyCode handle lost_card declines?
FlyCode automatically uses Visa Account Updater and Mastercard Automatic Billing Updater to detect when customers have been issued replacement cards and refresh stored details silently — often before the lost_card decline becomes a subscription cancellation.
