card_velocity_limit_exceeded: Stripe Subscription Fix
Root cause
The card issuer's fraud prevention system has flagged the card for too many charges in a short period, or the charge amount exceeds a per-day or per-transaction velocity limit set by the bank. This is common when retry logic fires too aggressively after an initial decline.
Symptoms
- • Stripe returns decline_code: card_velocity_limit_exceeded on the charge attempt
- • Subscription renewal fails even though the card is valid and has sufficient funds
- • Multiple retries worsen the situation by triggering additional velocity blocks
- • The customer receives no notification from Shopify or Recharge
- • Recharge may continue retrying on its standard dunning schedule, accumulating more declines
How to fix it
Pause all automatic retries immediately
Velocity blocks resolve on their own within 24 hours as the issuer's rolling window resets. Retrying while the block is active wastes attempts and can extend the block duration. In Recharge Admin, locate the subscription and pause the dunning queue. In Stripe Dashboard, confirm no Smart Retry attempts are scheduled within the next 24 hours.
Wait 24–48 hours, then send a single manual retry
After the velocity window resets, trigger one manual billing attempt via Recharge Admin or Shopify subscriptionBillingAttemptCreate mutation. Do not automate multiple retries in rapid succession. A single well-timed retry after the issuer window clears has the highest recovery rate for velocity declines.
Audit and slow down your dunning retry cadence
If velocity blocks are recurring for multiple customers, your retry schedule is too aggressive. Standard best practice: retry on day 3, day 7, day 14 — never same-day or next-day retries. In Recharge Admin, go to Settings > Dunning and increase the gap between attempts to at least 72 hours.
Frequently asked questions
Will retrying immediately fix a card_velocity_limit_exceeded decline?
No. Immediate retries make the problem worse. The velocity limit is enforced by the card issuer's rolling time window — typically 24 hours. Each additional retry during the active block counts against the limit and may cause the issuer to extend the block or permanently flag the card.
Is card_velocity_limit_exceeded the same as do_not_honor?
No. do_not_honor is a generic issuer decline with no specific reason. card_velocity_limit_exceeded is a specific decline type indicating the card has exceeded frequency or amount limits. Velocity blocks are temporary and resolve automatically. do_not_honor may require the customer to call their bank.
Detect this error automatically
Free cross-stack scan finds all billing errors in 60 seconds.
Run Free Scan →