Tip from SmartRetry Immediately suppress automated retries on Code 54 to avoid excessive network decline fees, routing the underlying token directly into an automated Account Updater queue instead. If updated credentials cannot be retrieved automatically, trigger a time-sensitive update prompt to the cardholder before scheduling any further authorization attempts.
Mastercard
Mastercard Issuer Response Code 54: Expired card
hard decline
Last updated: September 25, 2026
About 54 - "Expired card"
Key details
- 54
- Issuer Response Codes
- 54
- Expired card
hard decline
What it means
Mastercard issuer response code 54 indicates that the card used in the transaction is expired. The issuing bank returns this decline in DE 39 of the network response message when the card's expiration date is in the past, or when the expiry data submitted in the payment request is missing, outdated, or incorrect.
Classification & retryability
hardRetryable: conditional
Do not automatically retry the transaction using the same card details. Retries should only be attempted after obtaining an updated expiration date from the customer or via an Account Updater service.
Why does code 54 occur?
- The physical credit or debit card's expiration date has passed.
- The expiration date submitted in the authorization request was missing, incorrectly formatted, or contained a typographical error.
- The merchant attempted to charge a stored card-on-file that has not been updated with the customer's newest replacement card details.
How to solve 54?
First, check the original authorization request to verify that the submitted expiration month and year are present and contain no typographical errors. Do not blindly retry the same payment details, as the issuer will continue to decline it. Instead, inspect the response for any accompanying Merchant Advice Codes (MAC). If MAC 01 is present, utilize an Account Updater service to retrieve the new expiry date before retrying. Otherwise, prompt the customer to update their card details or provide an alternative payment method.
Solving as a merchant
Suppress automated retries on the unchanged payment credential to avoid unnecessary authorization attempts. Check the returned Merchant Advice Code (MAC); if it is MAC 01, trigger an account updater flow. If it is MAC 03, flag the payment method as unusable and reach out to the customer for a replacement payment method.
Solving as a customer
Review the expiration date entered during checkout and correct any typos. If the card is genuinely expired, enter the details of your newly issued replacement card or use a completely different payment method to complete the transaction.
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.