Issuer block · recoverable

approve_with_id

Issuer requires identification before approving the charge.

What just happened

The issuing bank suspects unusual activity and wants the cardholder to confirm identity before authorizing.

Retry strategy

Retry once after 24h. If still failing, ask the customer to call their bank.

What to tell the customer

Your bank held this charge for verification. Please confirm with them and we'll automatically retry.

Recommended action

Send a personalized email asking the customer to confirm with their bank, then auto-retry on day 1, 3, 7.

Want to see what this looks like on your Stripe?

See how often "approve_with_id" hits your Stripe account in the last 30 days — and how much MRR is at risk because of it.

Run free audit

Related codes

Frequently asked questions

Is "approve_with_id" 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 "approve_with_id" decline?+
Retry once after 24h. If still failing, ask the customer to call their bank.
What should I tell my customer when this happens?+
Your bank held this charge for verification. Please confirm with them and we'll automatically retry.
How do I prevent this decline going forward?+
Send a personalized email asking the customer to confirm with their bank, then auto-retry on day 1, 3, 7.
Does Rechurn handle this decline code automatically?+
Yes. Rechurn classifies "approve_with_id" 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.