Skip to main content

​
Card Velocity Exceeded

Decline code: card_velocity_exceeded Error type: card_error HTTP status: 201 Created (payment status becomes failed asynchronously) WL error code: 65

​
What it means

The card has exceeded the maximum number of transactions or the maximum total amount allowed within a time period. The issuing bank’s velocity controls blocked the transaction.

​
Why it happens

  • The cardholder has made too many purchases in a short time period (daily/weekly transaction limit).
  • The total spending amount has exceeded the card’s daily or monthly limit.
  • The issuer’s fraud prevention system flagged rapid successive transactions as suspicious.
  • The card has per-merchant or per-category spending limits that have been reached.
  • Corporate cards may have stricter velocity limits set by the company administrator.

​
API response

The payment is created with status: "pending". After processing, it transitions to failed with decline details: 
{
  "id": "pay_abc123",
  "status": "failed",
  "decline_code": "card_velocity_exceeded",
  "decline_message": "The card has exceeded its withdrawal limit."
}

​
What to tell the customer

Your card has reached its transaction limit. Please try again later, use a different card, or contact your bank to adjust your limits.
This is a non-sensitive decline — it is safe to be specific about the reason, as it helps the customer understand and resolve the issue.

​
What the merchant should do

  1. Show a clear, specific message — unlike lost/stolen card declines, velocity limits are not fraud-sensitive. Tell the customer what happened.
  2. Suggest waiting — velocity limits reset (usually daily). The same card may work the next day.
  3. Offer alternative payment methods — a different card from the same customer will likely work.
  4. Do not retry immediately — the limit will not reset within seconds. Retrying wastes API calls.
  5. Consider the amount — if the transaction is large, the customer may need to call their bank to pre-authorize it.
  6. Do not flag as fraud — velocity declines are normal, especially during sales events or for high-value purchases.

​
Common scenarios

  • Sale events — customers buying multiple items quickly during a flash sale.
  • Subscription renewals — multiple subscription charges processing simultaneously.
  • Business purchases — corporate cards with strict per-day limits.
  • Travel — international transactions may have lower velocity thresholds.

​
Prevention

  • Batch related charges — if possible, combine multiple items into a single charge instead of several small ones.
  • Inform customers of potential limits before high-value purchases.
  • Implement cart/checkout that accumulates items before a single charge.