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.
Mastercard
Mastercard Issuer Response Code 14: Invalid Card Number
hard decline
Last updated: September 25, 2026
About 14 - "Invalid card number"
Key details
- 14
- Issuer Response Codes
- 14
- Invalid card number
hard decline
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.
Classification & retryability
hardRetryable: conditional
Do not schedule automated retries against the unchanged card number. Retry only after the customer provides a corrected card number or an alternative payment method.
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 customer
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.
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.