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.
Mastercard
Mastercard Issuer Response Code 15: Invalid Issuer
hard declinetechnical decline
Last updated: September 25, 2026
About 15 - "Invalid issuer"
Key details
- 15
- Issuer Response Codes
- 15
- Invalid issuer
hard declinetechnical decline
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.
Classification & retryability
hardtechnicalRetryable: conditional
A single reattempt is only reasonable after the customer corrects or re-enters their card details. Automated, blind retries should not be used, as the underlying issuer-range or routing problem will not resolve itself through repeated attempts.
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 customer
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.
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.