Card velocity exceeded: what the decline means and what to do
Card velocity exceeded means the card hit a spending or usage limit set by the bank. What it means on Stripe, Braintree, Adyen and Recurly, and when to retry.

“Card velocity exceeded” means the customer’s bank refused the payment because the card hit one of its limits: the balance or credit limit, a limit on the amount per transaction or period, or a limit on how many times the card can be used. It is not a fraud flag on your side and the card is not dead. The customer can lift the limit with their bank, wait for it to reset, or pay with another card, so a spaced-out retry often works.
This guide covers what the decline is called on Stripe, Braintree, Adyen and Recurly, how it differs from the “velocity” rules in your own fraud tools, how many retries the card networks allow, and what to tell the customer. Every rule below comes from the providers’ documentation, listed in the sources.
What does “card velocity exceeded” mean?
In payments, “velocity” is how much or how often a card is used over a period. Card issuers put limits on both, and when a payment would cross one, they decline it.
Stripe’s decline code card_velocity_exceeded reads: “The customer has exceeded the balance, credit limit, or transaction amount limit available on their card.” The next step Stripe gives is that the customer needs to contact their card issuer for more information.
So one code covers several situations, and you cannot tell from the code which one applies:
- The credit limit or balance is used up. On a credit card, the open balance plus your charge is above the limit.
- An amount limit. The bank caps how much the card can spend in one transaction or over a period, such as a day.
- A count limit. The bank caps how many transactions the card can make over a period.
Adyen’s raw acquirer responses list the two limit responses that sit behind this kind of decline: 61 “Exceeds withdrawal amount limit(s)”, where “the shopper has exceeded their card limit”, and 65 “Exceeds withdrawal count limit”, where the shopper “has exceeded their card usage frequency limit”. In both cases Adyen says the shopper can try again after resolving the issue with their bank, or use another payment method.
Is it the same as insufficient funds?
Close, but not the same. Stripe has a separate code, insufficient_funds: “The card has insufficient funds to complete the purchase.” Its next step is different too: the customer needs to use an alternative payment method, where card_velocity_exceeded sends them to their bank.
Stripe also lists withdrawal_count_limit_exceeded: “The customer has exceeded the balance or credit limit available on their card”, with the same next step as insufficient_funds. In practice, treat all three as the same family: a soft decline about money or limits, which another day or another card can fix.
How is it different from your own velocity rules?
The word “velocity” also appears in fraud tools, and that is a different thing. A card velocity decline comes from the customer’s bank. A velocity rule in your fraud tool is yours: it blocks a card, an email or an IP address that tries too many payments in a short time.
Recurly shows the split clearly. Its fraud_velocity code sits under Fraud: “The transaction was part of a high-volume from a single source, indicating possible fraudulent activity.” Its too_many_attempts code, under Soft, means the payment “was declined because of too many authorization attempts”, and the customer message asks them to wait before retrying the card.
The fix is not the same:
| Where the limit sits | Example | Who can lift it |
|---|---|---|
| The customer’s bank | Stripe card_velocity_exceeded, Braintree 2002, Adyen 28 or 29 |
The customer, with their bank, or time |
| Your fraud tool | Recurly fraud_velocity, a velocity rule in Stripe Radar or your gateway |
You, by reviewing the rule |
| Your own merchant account | Recurly merch_max_transaction_limit_exceeded |
You, with your gateway |
The last row is rare but worth knowing: Recurly’s merch_max_transaction_limit_exceeded means “the limit has been exceeded for your daily or monthly dollar or transactions amount”, a limit on your gateway account, not the customer’s card. Recurly’s advice is to contact the gateway to increase the limit amount. Telling the customer to call their bank would not help.
What is it called on each provider?
| Where | Code | Type in the docs |
|---|---|---|
| Stripe | card_velocity_exceeded; close cousins withdrawal_count_limit_exceeded and insufficient_funds |
No type given; read the advice code |
| Braintree | 2002 Limit Exceeded, 2003 Cardholder's Activity Limit Exceeded |
Soft, Visa Category 2 |
| Adyen | Refusal reason 28 “Withdrawal amount exceeded”, 29 “Withdrawal count exceeded” |
Raw responses 61 and 65 say the shopper can try again after fixing the limit |
| Recurly | exceeds_daily_limit, exceeds_max_amount |
Soft |
Braintree’s explanation for 2002 is that the transaction “exceeds the withdrawal limit of the account”, and for 2003 that it “exceeds the activity limit of the account”. For both, it says the customer will need to contact their bank to change the account limits or use a different payment method.
If you bill with Chargebee, Zuora, Maxio or Paddle on top of a gateway, look for the gateway’s own code in the payment’s error details: that is where you will see which of these you got. For the full Stripe list, see Stripe decline codes explained.
Should you retry a card velocity decline?
Yes, a few times and spaced over days, unless the advice code says stop. A limit clears when the customer pays down the card, when the period resets or when the bank raises it. Another attempt in the same minute meets the same limit.
- 01 Read the advice code try_again_later allows a retry; do_not_try_again means stop
- 02 No retry on the same day A daily limit will refuse the same payment again
- 03 Spread a few retries over days Inside Stripe's eight and Visa's 15 in 30 days
- 04 Ask the bank or another card Retry at once when the card is updated or the limit lifted
On Stripe, read outcome.advice_code first. try_again_later means the issuer declined but you can retry. do_not_try_again means you should not use the card again for the same transaction. The advice code has the final word over any general rule.
Card network limits. Braintree lists 2002 and 2003 in Visa Category 2, “Issuer Cannot Approve At this Time (Reattempt Allowed)”, with retries limited to 15 over a rolling 30-day period. Above the threshold, the fee is $0.10 per domestic and $0.15 per international transaction. For Mastercard, Braintree says retries “should be based only on the Merchant Advice Codes”, and Mastercard charges $0.10 for every reattempt beyond 10 retries in 24 hours for MAC 03 and MAC 21.
Stripe’s own ceiling is lower. Its card declines guide recommends a maximum of eight retries for charges that permit retries, and warns that issuers can see extra retries as potential fraud, which can cause more declines on legitimate charges. Adyen has a refusal reason, 46, for transactions it blocked itself “to make sure that you are not charged penalty fees”.
A schedule that fits this decline:
- No retry on the same day. If a daily limit is the cause, the same day will fail again.
- Spread a few attempts over several days, well inside Stripe’s eight and Visa’s 15 in 30 days. Stripe Smart Retries, Chargebee, Recurly and others each have their own schedule; they are compared in payment retry schedules compared.
- Retry at once when the customer updates their card or says the bank lifted the limit, instead of waiting for the next slot.
- Stop on a “do not try again” signal (Stripe
do_not_try_again, Mastercard MAC03or21) and ask for another payment method.
Why do subscriptions hit card limits?
A few billing patterns make limit declines more likely. None of them is a reason to change your pricing, but each has a simple fix:
- Annual renewals. Twelve months charged at once is the payment most likely to cross an amount limit. A reminder before the renewal gives the customer time to make room on the card; see annual plan renewal reminders.
- Several charges on the same day. An add-on, a usage invoice and the base plan billed as separate payments count as several transactions against a count limit. Where your billing tool allows it, put them on one invoice.
- Large upgrades mid-cycle. A prorated upgrade charge lands on top of the renewal. If the upgrade fails on a limit, keep the customer on their current plan rather than cancelling anything.
- Retries in a loop. Each failed attempt counts toward the network retry limits above, and Stripe warns that issuers can see extra retries as potential fraud. A tight loop makes things worse.
What should you tell the customer?
Tell them their bank declined the payment because of a limit on the card, and give them two ways out: ask the bank to lift the limit, or use another card. Never show card_velocity_exceeded or a raw code. Adyen’s refusal reasons page says not to expose the details of the refusal reason to shoppers, “to prevent malicious use”.
Recurly’s customer message for exceeds_daily_limit shows the right tone: “This transaction exceeds your daily approval limit. Please contact your bank or try another card.”
A renewal email can read:
Subject: Your payment for [Product] didn't go through
Hi [First name],
Your bank declined this month's payment of [amount] for [Product] because it is above a limit on your card. This is usually a spending or transaction limit, and your bank can lift or raise it.
You can also use another card here: [update link]
We'll try again on [date]. If the limit resets or your bank raises it before then, you don't need to do anything.
Do not hint at the customer’s balance or credit. “A limit on your card” is accurate and polite; “you have no money left” may be wrong and is not your business.
What mistakes should you avoid?
- Treating it as fraud. A card velocity decline comes from the bank’s limits, not from a fraud signal. Do not block the customer or the card.
- Confusing it with your own velocity rules. If the code is
fraud_velocityor a Radar rule, the fix is on your side, not the customer’s. - Retrying the same day. A daily limit will refuse the same payment again, and each attempt counts toward the network limits.
- Cancelling after one failure. This is a soft decline. Give the retries and emails time to work before the subscription ends.
- Asking the customer to re-enter the same card details. The details are not the problem; a limit is. Ask for a bank call or another card.
How do you test a card velocity decline?
Stripe’s test card 4000000000006975 returns a card_declined error with the decline code card_velocity_exceeded (also available as pm_card_visa_chargeDeclinedVelocityLimitExceeded). Use it in test mode to check that your checkout shows a clear message, and that your renewal flow sends the email, waits before retrying and retries at once when the card is updated.
How NoChurn helps
NoChurn reads the decline code and history of every failed renewal. For soft declines such as a card limit, retries land on likely paydays in the customer’s time zone, inside the days and hours you allow, or you keep your provider’s own retries, such as Stripe Smart Retries. The recovery emails go out on days 0, 3, 7 and 14 by default, each written by AI for that customer and that decline and checked before it leaves; they never show the raw code, and each one links to a hosted card update page with no login. See failed payments.
FAQ
What does “card velocity exceeded” mean?
The customer’s bank declined the payment because the card reached one of its limits: the balance or credit limit, a limit on the amount spent, or a limit on how often the card can be used. Stripe returns it as card_velocity_exceeded.
Can you retry a card velocity exceeded decline?
Usually yes, if the advice code allows it and you space the attempts over days. Braintree marks the matching codes 2002 and 2003 as soft and Visa Category 2: at most 15 retries over a rolling 30 days. Stripe recommends at most eight.
How long does a card velocity limit last?
It depends on the issuer. Some limits reset after a day or another period, and a credit limit clears when the customer pays down the card. Only the customer’s bank knows, which is why Stripe’s next step is to contact the card issuer.
Is card velocity exceeded a sign of fraud?
No. It comes from the customer’s bank applying limits to the card. Fraud tools also use “velocity” rules, such as Recurly’s fraud_velocity, but those are your own rules and show different codes.
How is it different from insufficient funds?
On Stripe, insufficient_funds means the card does not have enough funds and the next step is another payment method. card_velocity_exceeded is broader: a balance, credit or transaction limit, with the customer contacting their bank as the next step.
Sources
All accessed 18 November 2026.