call_issuer
The issuing bank wants the cardholder to call before approving.
What just happened
Bank's fraud system flagged the transaction. They won't approve until the cardholder confirms with them directly.
Retry strategy
Don't retry blindly. Ask the customer to call their bank, then retry.
What to tell the customer
Your bank declined the charge and wants you to call them. After confirming, reply and we'll re-run it.
Recommended action
Email customer with their bank's fraud line (often on the back of their card). One retry after 48h.
Want to see what this looks like on your Stripe?
See how often "call_issuer" hits your Stripe account in the last 30 days — and how much MRR is at risk because of it.
Related codes
Frequently asked questions
Is "call_issuer" a soft or hard decline?+
It's classified as a issuer block: The issuing bank refused. Customer must call their bank or use a different card.
Should I retry a "call_issuer" decline?+
Don't retry blindly. Ask the customer to call their bank, then retry.
What should I tell my customer when this happens?+
Your bank declined the charge and wants you to call them. After confirming, reply and we'll re-run it.
How do I prevent this decline going forward?+
Email customer with their bank's fraud line (often on the back of their card). One retry after 48h.
Does Rechurn handle this decline code automatically?+
Yes. Rechurn classifies "call_issuer" and runs the optimal retry cadence with a personalized email sequence. Run a free audit to see how many of your failed charges are this code.