Skip to content

Decline code 15: No Such Issuer

Jordan MederichBy Jordan Mederich · Co-Founder & CEOReviewed by Sean WeasUpdated 3 min read
Summarize with AI

Quick answer

Decline code 15 — “No Such Issuer” — means the card number’s issuer identification number (the leading BIN digits) doesn’t correspond to any valid issuing institution on the network. Under the ISO 8583 standard it’s a hard decline: the transaction can’t route to a bank, so a retry of the same number always fails. Stripe reports the equivalent as an incorrect_number / invalid card error, and Authorize.net returns reason code 37 (card number invalid). Recovery takes a corrected or replacement card.

What code 15 means

Hard declineDo not retry

Don't retry the same card — a 15 means the card's issuer identification number doesn't route to a real issuing bank, and re-running it produces the same decline. Recover it by getting a valid card from the customer, then charging that.

Cross-processor equivalents

The same issuer decision surfaces under a different code on every processor. Here is how code 15 maps across the stacks Revatto recovers on.

ISO 8583
Code15
CalledNo Such Issuer
Stripe
Codeincorrect_number
CalledIncorrect numberalso invalid_cvc, invalid_expiry_*
Braintree
Code2005
CalledInvalid Card Number
Authorize.net
Code37
CalledCard number invalidresponseReasonCode 37
NMI
Code220
CalledInvalid card data
Chargebee
Codeinvalid_card
CalledInvalid card
Recurly
Codeinvalid_card
CalledInvalid card
IxoPay
Code2007
CalledInvalid card
Shopify
CodeINVALID_PAYMENT_METHOD
CalledInvalid payment methodalso PAYMENT_METHOD_NOT_FOUND
Whop
Codeinvalid_card
CalledInvalid cardnormalized — no processor-specific code (free-text categorized)

Why it happens

  • A mistyped or transposed card number whose leading digits no longer map to a valid issuer identification number.
  • A test or sample card number (or a number generated for testing) that was never issued by a real bank.
  • A card from a network or issuer range the acquirer/processor isn’t configured to route.
  • A truncated or corrupted PAN — missing or extra digits change the BIN and break issuer lookup.
  • Rarely, a recently launched issuer BIN range that has not yet propagated across the network’s routing tables.

How to recover it

  1. 1Don’t re-run the same number — a 15 will return identically until the underlying card number changes.
  2. 2Reach the customer on a channel they actually answer — email and SMS — let them know the card on file isn’t going through, and ask them to re-enter or switch to a different card.
  3. 3Verify the corrected number passes a basic format check (length + Luhn) before charging, so an obvious typo doesn’t fail the same way twice.
  4. 4
    When the customer goes quiet, a real person — not another automated email — follows up and works the card update directly. That AI-plus-human handoff is exactly what Revatto does for you: we recover the payment end to end, and you only pay if it works (20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime).See how Revatto recovers 15declines →

See what Revatto would recover for you

Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.

See Your Recovery Potential

Frequently asked questions