"Call issuer" card decline: what it means and what to do
What a "call issuer" or "card issuer declined" response means, how Stripe, Braintree and Recurly report it, whether to retry a renewal, and what to tell the customer.
“Call issuer” means the bank that issued the card declined the payment and wants the cardholder to contact it. The bank gives no reason to the merchant. The card may be blocked for online payments, flagged by a fraud check, or held for a reason only the bank knows, and only the customer can find out by calling the number on the back of the card.
For a subscription renewal, treat it as a decline you should not keep retrying on your own. Ask the customer to call their bank or to use another card, then let them pay again once it is sorted.
This guide uses what payment providers document themselves: Stripe’s decline codes, card declines and network decline codes pages, Braintree’s declines article and authorization responses and Merchant Advice Codes, and Recurly’s transaction errors. All accessed 9 November 2026.
What does “call issuer” mean exactly?
When a card payment is sent for authorization, the card network passes it to the bank that issued the card. The bank answers with a response code. “Refer to card issuer” (code 01 on Visa and Mastercard) and “call issuer” are the bank’s way of saying: declined, and the cardholder should get in touch with us.
For a recurring payment, nobody is at the checkout when the decline comes back, so the only person who can make that call is the customer.
Stripe describes call_issuer as “The card was declined for an unknown reason” and says “The customer needs to contact their card issuer for more information.” Its card declines guide adds that, “for privacy and security reasons, card issuers discuss the specifics of a decline only with their cardholders.” Neither you nor your payment provider will get a better answer from the bank.
Is “card issuer declined” the same thing?
Mostly, yes. “Card issuer declined”, “declined by issuer” and “issuer decline” are how many apps and checkout pages phrase any refusal that came from the customer’s bank rather than from the merchant or the payment provider. The specific code behind it can be call_issuer, do_not_honor, generic_decline or another one. If you see the phrase without a code, look up the payment in your provider’s dashboard: the code is there.
“Issuer not available” is different. It means the bank could not be reached to answer, which is a technical problem, not a refusal. Stripe lists it as issuer_not_available with the advice to “attempt the payment again.”
Which code is “call issuer” on each network and provider?
| Where | What you see |
|---|---|
| Visa network code | 01 “Refer to card issuer”, 02 “Refer to card issuer, special condition” |
| Mastercard network code | 01 “Refer to card issuer” |
| American Express network code | 107 “Call issuer” |
| Stripe | decline_code: call_issuer, plus network_decline_code and an advice_code |
| Braintree | 2044 Declined – Call Issuer (hard) or 2043 Error – Do Not Retry, Call Issuer (hard) |
| Recurly | call_issuer or call_issuer_update_cardholder_data |
The network codes come from Stripe’s network decline codes page. Recurly shows the customer “Your transaction was declined. Please contact your bank for further details or try another card.”
Billing platforms that sit on top of a gateway, such as Chargebee, Zuora or Maxio, pass on or translate the gateway’s response, so the wording you see depends on the gateway behind them. If you sell through a merchant of record like Paddle, Lemon Squeezy or Polar, or through the App Store or Google Play, the platform collects the money and runs its own recovery, so you may only see the result.
Should you retry a “call issuer” decline?
Not automatically. The providers agree on that more than the code’s name suggests:
- Braintree marks both
2043and2044as hard declines, meaning “the decline is not temporary and subsequent attempts with the same payment method will likely not be successful.” - Visa puts
2044in its Category 1, “Do not retry”, according to Braintree’s declines article. Retries beyond the threshold cost $0.10 per domestic transaction and $0.15 per international transaction, and Braintree notes that “Retrying Category 1 declines carry the highest network fees because each retry attempt is fined.” - Stripe does not label
call_issueritself as soft or hard. It gives a separateadvice_codeon the charge outcome:try_again_later(you can retry),do_not_try_again(do not use the card again for this transaction) orconfirm_card_data(some card details are wrong). Read it before scheduling a retry. - Mastercard retries, Braintree says, “should be based only on the Merchant Advice Codes.” Mastercard charges $0.10 for every reattempt beyond 10 retries in 24 hours for MAC
03(“Do not try again”) and MAC21(“Stop recurring payment”).
Braintree’s own description of 2044 says to “have the customer attempt the transaction again” and, if the decline persists, to contact their bank. That is a retry by the customer, after they have spoken to the bank, not a retry by your billing system on a schedule.
For the general rule, Stripe recommends “a maximum of eight retries for charges that permit retries” and warns that issuers “might see creating additional retries as potential fraud.” A call_issuer decline with do_not_try_again is not one of those charges. See payment retry schedules compared.
What should you tell the customer?
Be specific about the action, neutral about the cause. You do not know why the bank said no, so do not guess “insufficient funds” or “fraud”. Braintree recommends showing “a relatively generic message” at checkout and logging the response code so support can use it.
A renewal email for this case can look like this:
Subject: Your bank declined your [Product] payment
Hi [First name],
Your bank declined today's payment of [amount] for [Product]. They did not tell us why: banks only share the reason with the cardholder.
Two quick ways to fix it:
1. Call the number on the back of your card and ask them to allow payments to [descriptor].
2. Or use another card here: [update payment link]
Your account stays active until [date].
[Sign-off]
Three details matter:
- Name the descriptor. The customer’s bank will ask which merchant they mean. Give the exact text that appears on statements; see billing descriptors.
- Offer another card in one click. Many customers will not call their bank. A link to update the payment method is often the faster path.
- Give a date. A grace period before access stops makes the email useful rather than alarming. See dunning email templates.
Why do banks send “call issuer” on renewals?
The code itself says nothing, but Stripe’s card declines guide lists situations where the customer has to speak to the bank:
- Suspected fraud: a bank’s checks can be triggered by a large purchase or by many transactions in a short time, and “your customer must resolve this issue by communicating with their card issuer and confirming their identity.”
- Card type restrictions: some cards, such as FSA or HSA cards in the US, are limited to certain types of business, and some issuers block purchases from certain countries.
- Cross-border payments: cards issued in a different country from your account can see more declines; the customer must contact the bank to authorize the charge.
For a subscription, an annual renewal (a larger amount than usual) or a merchant abroad are typical moments when a bank asks the cardholder to confirm.
Can you reduce “call issuer” declines?
You cannot remove them, but you can make them rarer and easier to fix:
- Use a clear statement descriptor so the bank and the customer recognize the charge.
- Remind customers before a large renewal, so they expect it and can tell their bank. See annual plan renewal reminders.
- Keep card details current with network tokens and account updater services. See network tokens and card account updater.
- Log the network code and advice code for every decline, not only the provider’s label. It tells you whether a pattern comes from one bank, one country or one card type. See Stripe decline codes.
FAQ
What does “call issuer” mean on a card payment?
The bank that issued the card declined the payment and asks the cardholder to contact it. The merchant is not told the reason.
Is “call issuer” a hard or a soft decline?
Braintree classes it as hard, and Visa puts it in its “do not retry” category. On Stripe, check the advice_code that comes with it.
Can I retry a “call issuer” payment?
Not on an automatic schedule. Ask the customer to contact their bank or use another card, then let them pay again. Repeated retries can be fined by the card networks.
What is the difference between “call issuer” and “do not honor”?
Both are bank refusals without a stated reason. “Do not honor” (code 05) is usually treated as soft and can be retried within limits; “call issuer” asks for the cardholder to speak to the bank. See “do not honor” card decline.
What should the customer say when they call the bank?
That a payment to your business, under the descriptor shown on statements, was declined, and that they want it allowed. The bank can then explain the reason and lift a block if there is one.
Does “card issuer declined” mean my card is blocked?
Not necessarily. It means the bank refused that payment. The card can still work elsewhere; only the bank can say why it refused this one.
How NoChurn helps
NoChurn reads every failed payment and its decline code. A call_issuer decline is not retried blindly: NoChurn sends an AI-written recovery email, which you review, that asks the customer to contact their bank or switch cards, with a link to update the payment method. The decline shows on the customer’s timeline and feeds the churn score from 0 to 100.
It connects to Stripe in one click and works with Braintree, Chargebee, Recurly, Paddle and others, or with any billing through the API. Pricing depends only on MRR, with no commission (a custom sending domain needs a paid plan, from $9). See failed payments.