Skip to main content
Kalixo limits request bursts and payment attempts to keep the platform fast and to protect you from card-testing attacks. A limited request fails with 429 and rate_limit_error.

Limits

Kalixo can raise these limits for your account; ask Kalixo integrations. Kalixo also applies per-payment and daily amount limits, which fail with 402 amount_limit_exceeded.

Handling 429

  • Wait for the number of seconds in the Retry-After header, then retry. If you retry again, back off exponentially with jitter.
  • Retry a POST with the same Idempotency-Key, so it is applied at most once. See Idempotency.
  • @kalixo/checkout-node retries 429 and 5xx responses twice with backoff, reusing the idempotency key. Set maxRetries to change this.
  • too_many_attempts does not go away with time: the session has used all its attempts. Create a new checkout session for the shopper. Repeated declines on many sessions can mean card testing: check the shopper before you create more sessions.

Reduce your request volume

  • Use webhooks instead of polling payments.
  • Page through lists with limit=100.
  • Cache objects you read often, such as webhook endpoints.