Skip to main content
Spending limits (sometimes called velocity limits) help you control risk and keep spend aligned with your product rules.
For exact limit fields and allowed values, use the Cards API reference.

​
When to set limits

Common use cases:
  • Apply default limits when a card is issued
  • Tighten limits when a user is new or higher risk
  • Increase limits after verification or after an internal review

​
How limits work (conceptually)

Limits are usually defined by:
  • Time window (per transaction / per day / per week / per month)
  • Spend type (purchase vs cash withdrawal, depending on program)
  • Currency and amount
If a transaction exceeds a configured limit, it is typically declined.
1

Decide limits based on the product state

Examples:
  • New user → conservative limits
  • Verified and trusted user → higher limits
2

Apply limits to the card

Set limits on the card record. Store your own “limit profile” decision so support can explain why the user is limited.
3

Surface limits in the UI

Tell the user what the limit is, and what they can do if they need a higher limit (for example: complete verification, contact support, or wait for review).