DunningKit

← All decline codes · Articles

Stripe decline code: card_velocity_exceeded

Card velocity exceeded — The card has been used too many times in too short a window.

Common cause

Issuer rate-limit. Common when a customer's card was just charged elsewhere, or when retries are too aggressive.

Recovery strategy

Retry strategy	Retry after a delay
Customer-facing action	No customer action needed
Recovery rate (retry only)	~10%
Recovery rate (with customer flow)	~55%

What to do, in order

Wait at least 24 hours before retrying. Aggressive retries here actively make recovery harder by reinforcing the issuer's rate-limit signal.

Code example

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

Where this fits in the bigger picture

card_velocity_exceeded 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.