Velocity Limit Decline
A velocity limit decline occurs when a card processes too many transactions in a short time window. Banks and payment processors set velocity limits as an anti-fraud measure — rapid successive charges often indicate stolen card usage. When your recurring charge hits this limit, it's declined not because of anything wrong with the account, but because of timing. This is a soft decline with an 85-90% recovery rate, as simply waiting and retrying resolves the issue.
Affected Percentage
~3% of all declines
Recovery Rate
85-90% recoverable
Recommended Action
Retry with strategy
Common Causes
Multiple subscriptions charging simultaneously
If the customer has several subscriptions all billing on the same date, the rapid sequence of charges can trigger velocity limits.
Retry storms from other merchants
Other merchants may be retrying failed charges on the same card, creating a burst of transaction attempts that triggers the bank's velocity limit.
Duplicate submission from your system
A technical glitch in your billing system might send the same charge request multiple times in rapid succession, triggering velocity controls.
Customer shopping spree
The customer made several purchases in a short period (e.g., online shopping), and your charge was the one that pushed past the limit threshold.
Recommended Retry Strategy
Timing
Wait at least 4-6 hours before retrying. Velocity limits typically reset within hours. Retry during off-peak hours (6-9am customer local time) for best results.
Max Retries
2-3 retries over 3 days
Reasoning
Velocity limits are purely timing-based. The card itself is fine. Waiting a few hours lets the limit reset and retrying during quiet periods avoids competing with other charges on the same card.
Best Practices
- 1
Space your retries at least 4-6 hours apart to ensure the velocity window has reset.
- 2
If you bill multiple products/plans for the same customer, consolidate into a single transaction to minimize velocity impact.
- 3
Retry during early morning hours (6-9am) when the card is less likely to be processing other transactions.
- 4
If you're seeing velocity declines on your own retry attempts, you may be retrying too aggressively — increase the interval between retries.
- 5
Coordinate with your payment processor to understand their specific velocity limits so you can stay within them.
How Rezoki Handles This Automatically
Rezoki identifies velocity limit declines and schedules retries for low-traffic windows — typically early morning when competition from other charges is minimal. Rezoki also detects when multiple customers at the same workspace are hitting velocity limits simultaneously, which can indicate an issue with the billing system's charge timing. In these cases, Rezoki recommends spreading out billing cycles. For individual velocity declines, the automated retry with smart timing resolves 85-90% without any customer contact.