How we classify payment failures

Every error code maps to one of 18 reasons a payment fails. This is the reference the tool checks before it answers.

Sources: NPCI UPI v2.9, NPCI NACH, ISO 8583, Razorpay, Cashfree, StripeLast updated: 22 Sep 2026Unknown codes waiting for review: 1

Reasons payments fail 18

Retry: Yes
Retry: After an action
Retry: No
Retry: Not until checked

Not enough balance

Retry: Yes

Customer didn't have enough money when the debit was attempted.

WHEN TO RETRY

Cards: no sooner than 24h after the decline, within network caps (Visa: 15 retries per card in 30 days). Recurring: time retries near likely salary credit (1st–7th). UPI Autopay: up to 3 retries in the cycle after the first attempt, inside the permitted IST execution windows; the pre-debit notification is needed before the scheduled debit, not before each retry.

PREVENT IT

Set debit dates near salary credit, and remind customers two days before each debit.

INSUFFICIENT_FUNDS

Spending limit reached

Retry: Yes

A daily, per-transaction or frequency limit set by the customer or bank was hit.

WHEN TO RETRY

Daily or frequency limits: after the limit resets (typically next day). Per-transaction limits don't reset: charge a smaller amount or collect another way. FL/FP first-time UPI limits: after 24h.

PREVENT IT

Tell customers about bank limits before large debits, or bill large amounts in smaller cycles.

LIMIT_EXCEEDED

Bank or network was down

Retry: Yes

Bank, network or gateway was unavailable or timed out. Nothing wrong with the customer.

WHEN TO RETRY

Retry in 1–4 hours. UPI Autopay: only inside the permitted IST windows (before 10:00, 13:00–17:00, after 21:30). NACH: the next presentation cycle.

PREVENT IT

Schedule debits in daytime hours, away from bank maintenance windows.

BANK_OR_NETWORK_DOWNTIME

Bank flagged it as risky

Retry: After an action

Bank or network risk model flagged the payment as suspicious.

WHEN TO RETRY

At most one retry after 24h; otherwise wait for customer to clear it with their bank.

PREVENT IT

Authenticate customers at sign-up (3DS or a verified mandate) so issuers recognise your debits.

ISSUER_RISK_DECLINE

Bank declined without a reason

Retry: After an action

Bank declined without saying why (do not honour, generic decline, bare U30).

WHEN TO RETRY

Retry once after 24h unmodified; abandon if the second attempt also fails.

PREVENT IT

Keep a backup payment method on file so a failing card can switch rails instead of lapsing.

AMBIGUOUS_ISSUER_DECLINE

Customer didn't complete verification

Retry: After an action

Customer didn't finish authentication — wrong PIN/OTP, didn't approve, timed out or cancelled.

WHEN TO RETRY

Only when the customer re-initiates or re-authenticates. UPI Autopay and card e-mandates above Rs 15,000 need authentication on each debit (Rs 1,00,000 for mutual fund subscriptions, insurance premiums and credit card bills).

PREVENT IT

Send approval requests when customers are active, with a reminder before the request expires.

AUTH_NOT_COMPLETED

All error codes 200

Differs by payment method
the same code means something else for another payment method
Hides the real code
the bank's code is inside the error
Retry timing only
changes when to retry, not why it failed
Depends on the situation
needs more payment details
Payment methodCodeOfficial descriptionReasonFlagsSource
Card03Invalid merchantProblem on the merchant's side
—
ISO 8583
Card04Pick up cardCard reported lost or stolen
Differs by payment method
ISO 8583
Card05Do not honorBank declined without a reason
Differs by payment method
Depends on the situation
ISO 8583
Card06ErrorBank or network was down
Differs by payment method
Depends on the situation
ISO 8583
Card07Pick up card, special conditionCard reported lost or stolen
Differs by payment method
ISO 8583
Card12Invalid transactionProblem on the merchant's side
Differs by payment method
ISO 8583
Card13Invalid amountProblem on the merchant's side
Differs by payment method
ISO 8583
Card14Invalid card numberWrong or outdated payment details
Differs by payment method
ISO 8583
Card15No such issuerWrong or outdated payment details
Differs by payment method
Depends on the situation
ISO 8583
Card19Re-enter transactionBank or network was down
Depends on the situation
ISO 8583
Card39No credit accountWrong or outdated payment details
Depends on the situation
ISO 8583
Card41Lost cardCard reported lost or stolen
—
ISO 8583
Card43Stolen cardCard reported lost or stolen
—
ISO 8583
Card46Closed accountAccount closed
—
ISO 8583
Card51Insufficient fundsNot enough balance
Differs by payment method
ISO 8583
Card52No checking accountWrong or outdated payment details
Differs by payment method
Depends on the situation
ISO 8583
Card53No savings accountWrong or outdated payment details
Differs by payment method
Depends on the situation
ISO 8583
Card54Expired cardCard expired
Differs by payment method
ISO 8583
Card55Incorrect PINCustomer didn't complete verification
—
ISO 8583
Card57Transaction not permitted to cardholderCard or account is restricted
Differs by payment method
ISO 8583
Showing 1–20 of 200