Tip from SmartRetry Immediately suppress this credential across all automated billing schedules to avoid incurring unnecessary network penalty fees, and trigger an automated dunning sequence to capture a replacement payment method.
Mastercard
Mastercard Issuer Response Code 41: Lost Card
hard decline
Last updated: September 25, 2026
About 41 - "Lost card"
Key details
- 41
- Issuer Response Codes
- 41
- Lost card
hard decline
What it means
Mastercard issuer response code 41 means the issuing bank declined the authorization request because the cardholder previously reported the card as lost. This is a hard decline indicating that the specific card credential has been invalidated by the issuer and cannot be used for transactions.
Classification & retryability
hardRetryable: no
Why does code 41 occur?
- The cardholder misplaced their physical credit or debit card and reported it as lost to their issuing bank.
- The merchant attempted to process a stored card on file or recurring subscription credential that the issuer recently marked as lost.
How to solve 41?
Because the issuer has permanently flagged the specific card number as lost, you cannot resolve this decline by modifying the authorization payload. The transaction must be treated as a hard failure. Prompt the customer to select or enter an alternative payment method to complete their checkout or update their subscription billing details.
Solving as a merchant
Immediately halt any automated SmartRetry attempts and recurring subscription dunning for this specific card credential, as subsequent attempts will fail. Record the decline in your system to prevent reuse of the card. Provide a clear fallback option for the shopper without exposing unnecessary issuer-security details. Note that while code 41 flags the card as lost, it does not independently require you to confiscate a physical card during an in-person transaction.
Solving as a customer
Provide a different credit card or alternative payment method to complete the transaction. If you believe the card was reported lost in error or if it was recently recovered, contact the issuing bank directly to correct your account status.
Frequently asked questions about this topic
Share this article
Author
Kyle Regacho
Find me on LinkedinFocused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >Related codes
Articles you may find interesting:
View all
Turning Payment Declines into Revenue with Context-Aware Retry Logic
Blind retries waste fees and damage issuer trust. By analyzing decline codes and timing reattempts around payroll cycles, payment teams can successfully salvage recurring revenue without customer disruption.
Why Payments Fail: Decoding Decline Codes and Modernizing Retry Logic
Surface-level decline messages conceal critical issuer signals. Discover how intelligent retries, network tokens, and behavioral timing protect MID health and systematically recover lost recurring revenue.
Decoding Payment Declines: Turning Authorization Failures into Recovered Revenue
Blindly retrying failed transactions hurts authorization rates and risks network fines. Discover how decoding issuer responses turns card declines into recovered revenue.
The Real Cost of Payment Declines and How to Recover Lost Revenue
Payment failures cost merchants billions in uncaptured revenue and customer churn. Discover how data-driven retries and response code intelligence help teams recover failed transactions and protect conversion.