Call issuer — The issuer wants the cardholder to call them before authorizing further charges.
Usually a soft fraud-flag or unusual-activity check.
| Retry strategy | Retry after a delay |
|---|---|
| Customer-facing action | Ask customer to contact their issuer |
| Recovery rate (retry only) | ~15% |
| Recovery rate (with customer flow) | ~50% |
Wait 24h before retrying. Email the customer suggesting they call the number on the back of their card; many will, and the next retry succeeds.
The recommended Stripe Customer Portal session for the recovery flow:
session = stripe.billing_portal.Session.create(
customer=customer_id,
return_url="https://yourapp.com/billing/thanks",
flow_data={"type": "payment_method_update"},
)
update_link = session.url
call_issuer is one of dozens of decline codes Stripe returns; recovery rates vary by code by 5x or more. The recovery-rate reference covers the full set; the card-update flow article covers the customer-facing side; dunning emails covers how to write the messages.
DunningKit's open-source CLI parses your Stripe failed-charges CSV and gives you the breakdown by code, with recoverable-revenue estimates. pip install dunningkit.