Skip to main content
SmartRetry - Payment Recovery Platform

Mastercard

Mastercard Issuer Response Code 15: Invalid Issuer

hard decline

Last updated: October 8, 2026

Key details

Brand
Mastercard
Code
15
Response
15
Detailed Response
Invalid issuer
hard decline
This transaction is not retriable

Payments failing with code 15 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 response code 15 indicates a network-level validation failure where the customer's issuing bank does not exist or the primary account number (PAN) falls outside a recognized range. It is essentially a 'No Issuer' message, signaling that the scheme, acquirer, or routing configuration cannot identify or support the card's origin.

Why does code 15 occur?

  • The cardholder entered an incorrect primary account number (PAN) that maps to a non-existent issuer.
  • The card number falls within an unrecognized or unsupported issuer BIN range.
  • The merchant's acquirer or routing configuration cannot handle the specific card brand, geography, or product type.
  • The scheme or acquirer setup has not been configured to support that specific account-number range.

How to solve 15?

First, ask the customer to verify their primary account number (PAN), expiry, and card brand to rule out a simple data-entry typo. If the details are valid but the decline persists, inspect your processor logs for the raw network response and any accompanying acquirer error messages. If you determine the BIN range is valid but restricted by your current acquirer's setup, route the transaction through a compatible processor. Otherwise, offer an alternative payment method.

Solving as a merchant

Check your processor logs to confirm if the code 15 decline stems from a routing limitation, geographic restriction, or unsupported BIN range on your acquirer's end. Ensure your production retry rules rely on normalized refusal classifications and merchant-advice signals rather than raw network responses alone. If the BIN cannot be processed on your primary route, update your routing logic or prompt the customer for a different card.

Solving as a client

Carefully re-enter your credit card number, expiration date, and security code to ensure there are no typos. If the information is completely accurate and the payment is still declined, try a different payment method or contact your issuing bank for further assistance.

Tip from SmartRetry Never replay code 15 declines across the same connection, as identical attempts will consistently fail without an updated routing path. Instead, configure intelligent multi-acquirer failover to automatically redirect valid, newly issued BIN ranges to a compatible processor.

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.