Issuer (issuing bank)

The cardholder's bank: it issued the card and decides whether each card payment is approved or declined.

issuing bankcardholder's bankbank that issued the cardbank that approves the chargecustomer's card bankcard issuerisuerwhose bank declined my customer's card

See it

Live demo coming soon

What it is

When a card is approved or declined, the issuer is usually making the call. It is the bank or financial institution that gave the card to the cardholder, and it checks the account, available funds or credit, card status, and fraud signals during authorization.

Think about the issuer when interpreting declines, supporting cardholder authentication, or explaining pending authorization holds. Your processor can pass better data and authentication evidence, but the issuer makes the approval decision. The exception is stand-in processing: when the issuer is unreachable, the card network can approve or decline on its behalf against issuer-set rules.

Decline messages are often broad on purpose, so neither the merchant nor processor may know the exact reason. Do not tell a customer their balance is low unless the issuer explicitly said so; ask them to try another method or contact their bank.

Ask AI for it

Build issuer-aware decline handling for Stripe PaymentIntents. Store last_payment_error.decline_code and the network decline code from the Charge outcome, map them into safe customer messages, and never guess a private decline reason. For soft declines, run the PaymentIntent's required authentication or allow a controlled retry; for hard declines, stop automatic retries and ask for another payment method. Keep every raw code for support and analytics.

You might have meant

soft decline vs hard decline3 d secure authentication strong customer authenticationauthorization and capturecard testing attack