Stripe decline code

card_velocity_exceeded

The card exceeded a velocity limit — too many charges, or too much total spend, within a short window set by the issuer.

Primary source: Stripe’s official decline codes reference

Why it happens

  • Many charges were attempted on the card in a short period.
  • The card hit a daily or per-period spending cap.
  • Repeated retries in quick succession tripped the issuer's limit.

Should you retry it?

Sometimes — it depends on the issuer

Once the limit window passes, the same card often succeeds. Spacing retries out — rather than hammering the card — is essential here.

How to recover it

Space retries well apart so the velocity window can reset, and avoid rapid repeated attempts that keep the limit tripped.

Let Stripe's retry schedule run first. For invoices that stay unpaid after it ends, Recoverly opens a case and — with your approval — sends a 3-step payment-update sequence (Day 0 / 3 / 7) linking to Stripe's hosted payment page.

See how much failed-payment revenue you can recover

Connect Stripe (we only read) and Recoverly shows your recoverable revenue in 30 seconds.

Related decline codes

Written by the Recoverly team · Published June 25, 2026 · Last reviewed July 17, 2026

Recoverly finds invoices Stripe’s retries left unpaid and — with your approval — sends payment-update emails, then verifies what actually came back. This page is informational and not affiliated with Stripe.