Skip to main content

Rate limits

Rate limits protect platform availability and partner integrations.

Limit model​

Limits may apply by:

  • API key.
  • Account.
  • Endpoint group.
  • Environment.
  • Customer tier.
  • Partner route.

Rate limit response​

When you exceed a limit, the API returns HTTP 429.

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Too many requests. Retry after the time indicated in the response headers."
  }
}

Headers​

Responses may include:

X-RateLimit-Limit: 600
X-RateLimit-Remaining: 42
X-RateLimit-Reset: 1780304442
Retry-After: 30

Retry strategy​

Use exponential backoff with jitter. Do not retry immediately in a tight loop.

Recommended behavior:

  • Retry 429 responses after Retry-After.
  • Retry temporary 5xx responses with backoff.
  • Do not retry validation errors without changing the request.
  • Use idempotency keys when retrying payment creation.

Webhook retries​

Webhook delivery retries are managed by CashXChain. Your endpoint should return quickly and process events asynchronously.

Higher limits​

Enterprise customers can request higher limits based on traffic patterns, payment volume, and production readiness.