Skip to main content
SmartRetry - Payment Recovery Platform

Mastercard

Mastercard Issuer Response Code 14: Invalid Card Number

hard decline

Last updated: October 8, 2026

Key details

Brand
Mastercard
Code
14
Response
14
Detailed Response
Invalid card number
hard decline
This transaction is not retriable

Payments failing with code 14 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 14 indicates that the issuing bank declined the transaction because the submitted credit card number does not exist or cannot be found. This is a primary data-validation failure at the issuer level, meaning the numerical sequence provided does not correspond to an active or recognizable account in their system.

Why does code 14 occur?

  • The customer made a typographical error when entering their credit card number during checkout.
  • The payment request transmitted a corrupted, truncated, or malformed Primary Account Number (PAN) to the processor.
  • The merchant attempted to charge an obsolete or improperly stored card credential that the issuer can no longer validate.

How to solve 14?

First, validate the transmitted card number in your system logs for obvious formatting or truncation errors. If the data was formatted correctly, prompt the shopper to re-enter their complete card number. Ensure the checkout or payment request is using the intended card rather than an incorrect stored credential. Once a valid number is supplied, submit a new authorization request.

Solving as a merchant

Halt automated retries on the unchanged card data, as blind retries will continuously fail. Preserve the code 14 response and flag the associated payment token as invalid in your vault. Prompt the customer via email or your checkout UI to update their payment details. Do not permanently delete a user's billing profile based solely on this code without further processor diagnostics, but do require card-data correction before proceeding.

Solving as a client

Carefully review the credit card number you entered for typos and submit the correct information. If you are using a saved payment method, delete it and re-enter your card details. If the number is definitely correct but still declining, contact your issuing bank or provide a different payment method.

Tip from SmartRetry Immediately suppress automated background retries for this decline to avoid unnecessary network fees and potential card-testing flags from the issuer. Instead, divert the shopper to an in-session correction flow that performs client-side Luhn checks before attempting a fresh authorization.

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.