Skip to main content
SmartRetry - Payment Recovery Platform

Mastercard

Mastercard Issuer Response Code 54: Expired card

hard decline

Last updated: October 8, 2026

Key details

Brand
Mastercard
Code
54
Response
54
Detailed Response
Expired card
hard decline
This transaction is not retriable

Payments failing with code 54 are hard declines and typically cannot be recovered by retrying. SmartRetry still helps you avoid future hard declines with smarter routing and validation.

But many other declines in your payment flow may still be recoverable. SmartRetry identifies which failed transactions have recovery potential and applies the right strategy to recover them.

Find out what you can recover >

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.

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 client

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.

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.

See the full list of Mastercard's decline codes >Find code on Mastercard's website >

Frequently asked questions about this topic

Share this article

Share on XShare on FacebookShare on LinkedIn
Kyle Regacho

Author

Kyle Regacho
LinkedInFind me on Linkedin

Focused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue

Read all articles >

Articles you may find interesting:

View all
How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

Discover how automated risk reviews trigger gateway freezes and how payment teams can insulate revenue through multi-acquirer setups and smart retry logic.

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Payment rejections cost merchants billions in lost sales and unforced churn. Discover the root causes behind issuer declines and how intelligent recovery strategies salvage legitimate revenue.

Why Payment Tests Pass in Staging and Fail in Production

Why Payment Tests Pass in Staging and Fail in Production

Passing a sandbox check rarely guarantees live authorization success. Learn how real-world issuer ambiguity, webhook delays, and network retry rules impact revenue pipelines.

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Sandboxes verify API formatting, but live issuers determine transaction success. Discover how multi-layered testing, safe retry logic, and real-time observability safeguard authorization rates and reduce involuntary customer churn.

Decline codes tell you why. We fix it.

SmartRetry reads every decline reason and applies the right retry strategy for each one. Your recovery rate goes up without any changes to your payment provider.