Stripe decline code
call_issuerThe card issuer requires the customer to contact them before approving the charge.
Type
Recoverable
Frequency
Uncommoncall_issuer is returned when the bank has flagged something suspicious but is willing to approve the charge if the cardholder verifies it. Common triggers: unusual geography, large amount, new merchant, or a new travel flag.
Wait at least 24 hours for the customer to call their bank. Then retry once. If it fails again, send a reminder; if it fails a third time, ask for a different card.
This one requires customer action. Send a clear message: "Your bank has flagged this charge for verification. Please call the number on the back of your card to approve, then we will retry automatically."
Temporary issue. The card is still valid. High recovery rate with proper retry timing.
They should reference the merchant name, the charge amount, and the date. Most banks can lift the flag in minutes and approve the next attempt.
How Rebounce handles call_issuer
Rebounce classifies every failed payment by its Stripe decline code and applies the optimal recovery strategy automatically. For call_issuer, that means a limited retry window combined with customer outreach. Multi-channel follow-up through email, SMS, WhatsApp, and in-app banners ensures the customer actually sees the message.
do_not_honorSoft declineThe issuing bank has flagged the charge, usually for a fraud or risk reason, and will not approve it right now.
generic_declineSoft declineThe card issuer declined the charge but did not provide a specific reason. This is a catch-all soft decline used when the bank will not say why.
authentication_requiredAuthentication requiredThe card issuer requires Strong Customer Authentication (3D Secure) before the charge can proceed.