Standard
100 TPM: Verification APIs that require real-time processing and external data validation
Medium
200 TPM: Lightweight verification services with faster processing capabilities
Restricted
5 TPM: Resource-intensive bulk operations that require significant processing time
Rate limits
- Standard (100 TPM)
- Medium (200 TPM)
- Restricted (5 TPM)
Standard rate limit: 100 transactions per minuteSecure ID APIs that require real-time processing and external data validation.
Rate limit error handling
When you exceed the rate limit for any API, the system returns an HTTP 429 status code.Error Response Structure
Error Response Structure
The following response structure is returned when rate limits are exceeded:
Best practices for rate limit management
Use these guidelines to optimise your API usage and avoid rate limit errors.Implement exponential backoff
Implement exponential backoff
When you receive a 429 response, implement retry logic with exponential backoff:
Monitor rate limit headers
Monitor rate limit headers
Check the rate limit headers in successful responses to proactively manage your request timing:
Distribute requests evenly
Distribute requests evenly
Avoid sending bursts of requests at the beginning of each minute. Instead, distribute your requests evenly throughout the time window.Example strategy:
- For 100 TPM limit: Send 1 request every ~600ms
- For 200 TPM limit: Send 1 request every ~300ms
- For 5 TPM limit: Send 1 request every ~12 seconds
Requesting rate limit increases
If your application requires higher rate limits, you can submit a request through the support form or contact your account manager directly. When you submit your request, include the following information:- Your merchant ID
- Current usage patterns and volumes
- Expected future usage requirements
- Business justification for the increase