card_velocity_exceeded
Card has been used too many times in a short window.
What just happened
Issuer's fraud system rate-limited the card after multiple recent transactions.
Retry strategy
Wait 24h, then retry. Don't hammer it.
What to tell the customer
Your card hit a usage limit at the bank. We'll try again tomorrow — no action needed.
Recommended action
Pause retries 24h, then auto-retry on day 1, 3, 7.
Want to see what this looks like on your Stripe?
See how often "card_velocity_exceeded" 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 "card_velocity_exceeded" a soft or hard decline?+
It's classified as a limits exceeded: Card-level or account-level limit hit. Wait window then retry, or use a different card.
Should I retry a "card_velocity_exceeded" decline?+
Wait 24h, then retry. Don't hammer it.
What should I tell my customer when this happens?+
Your card hit a usage limit at the bank. We'll try again tomorrow — no action needed.
How do I prevent this decline going forward?+
Pause retries 24h, then auto-retry on day 1, 3, 7.
Does Rechurn handle this decline code automatically?+
Yes. Rechurn classifies "card_velocity_exceeded" 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.