Stripe decline code
call_issuer
The issuing bank declined and wants the cardholder to call them before the charge can go through.
Primary source: Stripe’s official decline codes reference
Why it happens
- A fraud or security check needing the cardholder's confirmation.
- A hold on the account.
- Unusual activity the bank wants to verify.
Should you retry it?
Sometimes — it depends on the issuer
Until the customer calls their bank, retries may keep failing — but some clear once the bank's checks pass. Retry on a measured schedule and nudge the customer.
How to recover it
Retry on a moderate schedule and email the customer asking them to call their bank to approve the charge.
Let Stripe's retry schedule run first. For invoices that stay unpaid after it ends, Recoverly opens a case and — with your approval — sends a 3-step payment-update sequence (Day 0 / 3 / 7) linking to Stripe's hosted payment page.
See how much failed-payment revenue you can recover
Connect Stripe (we only read) and Recoverly shows your recoverable revenue in 30 seconds.
Related decline codes
Written by the Recoverly team · Published June 25, 2026 · Last reviewed July 17, 2026
Recoverly finds invoices Stripe’s retries left unpaid and — with your approval — sends payment-update emails, then verifies what actually came back. This page is informational and not affiliated with Stripe.