Tip from SmartRetry Immediately suppress this card across your billing system to prevent unnecessary gateway decline fees and protect your merchant fraud metrics. Instead, trigger an automated notification prompting the customer to authenticate a completely new payment method, such as a digital wallet or bank transfer.
Visa
Visa Issuer Response Code 41: Lost Card
hard declinefraud decline
Last updated: September 25, 2026
About 41 - "Lost card"
Key details
- 41
- Issuer Response Codes
- 41
- Lost card
hard declinefraud decline
What it means
Visa response code 41 indicates a hard decline because the card being used has been reported lost to the issuing bank. This is an issuer action code signaling that the account is blocked for fraud control, and the issuer may instruct the merchant to retain the card if presented in person.
Classification & retryability
hardfraudRetryable: no
Why does code 41 occur?
- The cardholder previously contacted their issuing bank to report the physical card as lost.
- The issuing bank proactively flagged the account as lost for fraud control purposes.
How to solve 41?
Because the issuer has permanently blocked this specific card number due to it being reported lost, no further authorization attempts should be made with these card details. Treat the transaction as a hard decline and permanently remove the payment method from active billing cycles. To recover the revenue, you must obtain a completely different payment method from the customer.
Solving as a merchant
Configure your payment platform or SmartRetry logic to suppress automated retries for code 41, as repeated authorizations risk unnecessary network traffic and scrutiny. Do not expose the exact 'lost card' or 'pick up' phrasing in customer-facing error messages; instead, display a generic payment failure notice. For e-commerce, immediately prompt the shopper for an alternative payment method. For card-present transactions, follow your terminal's specific instructions for card capture or retention.
Solving as a customer
Provide an alternative credit card or payment method to complete the purchase. If the customer believes the card's lost status is an error, they must contact their issuing bank directly to resolve the issue or wait for a replacement card.
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.