Tip from SmartRetry Halt automated retries on identical payloads, as unallocated account ranges will consistently decline. Instead, gate retries behind an upstream BIN table validation or token vault refresh to ensure the card range is active before re-routing.
Visa
Visa Issuer Response Code 15: No Such Issuer
hard declinetechnical decline
Last updated: September 25, 2026
About 15 - "No such issuer"
Key details
- 15
- Issuer Response Codes
- 15
- No such issuer
hard declinetechnical decline
What it means
Visa response code 15 means "No such issuer." It is a network-generated decline indicating that the primary account number (PAN) is not within a card-number range currently supported or defined by the card network. This typically occurs because the first eight digits (the BIN or account range) do not correspond to any known, active issuing identifier on VisaNet.
Classification & retryability
hardtechnicalRetryable: conditional
Do not attempt automated or time-based retries using the same primary account number (PAN) or token, as this is a Visa Category 1 hard decline. A retry is only permitted if the customer provides a corrected card number or if the merchant fixes an underlying network routing or tokenization error.
Why does code 15 occur?
- The customer entered a malformed or incorrect primary account number (PAN).
- The transaction was routed over the wrong card network for the provided BIN.
- The merchant attempted to process a test card or non-production card number in a live environment.
- The bank identification number (BIN) or account range is inactive or currently unsupported by the scheme.
How to solve 15?
Verify that the correct card network is being used and that production credentials are active. If the PAN or token-to-PAN mapping is malformed or invalid, the transaction cannot be processed as-is. The underlying card data or network configuration must be corrected before submitting a new authorization request.
Solving as a merchant
Check your payment gateway's tokenization and routing configuration to ensure you aren't sending account numbers over the wrong network or passing test data into production. Validate the card number and BIN/account-range consistency. If the issue is tied to a specific integration, investigate for defects; otherwise, prompt the user for an alternative payment method.
Solving as a customer
Check the entered card number for typos and re-enter the payment details. If the card number is correct but still declining, provide an alternative payment method.
Frequently asked questions about this topic
No FAQs available for 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.