In order to ensure the platform is available for everyone, in very rare cases, some users may encounter rate limits.
If your request rate exceeds the limit, you may receive one of two responses: the Payment API-specific Rate Limit response, or the System-Wide Rate Limit response.
Payment API-Specific Rate Limit
If you exceed the Payment API rate limit, you will receive a response with the following fields:
| Property | Value |
|---|---|
| response | 3 |
| responsetext | Rate limit exceeded |
| response_code | 301 |
Example Response
response=3&responsetext=Rate limit exceeded&authcode=&transactionid=&avsresponse=&cvvresponse=&orderid=&type=&response_code=301
System-Wide Rate Limit
You may encounter the system-wide rate limit if you are using other services,
for example if you are making requests to both the Payment API and the Query API,
or if there are too many concurrent connections from your IP.
In this case, your request will receive HTTP 429: Too Many Requests
Handling Rate Limit Responses
Wait before retrying
If you receive a response_code of 301 or an HTTP 429 response, do not immediately retry the request.
Immediately retrying may increase the delay before transactions are allowed again.
Use fewer simultaneous connections
Reduce the number of threads or processes sending connections if you regularly encounter rate limits.
Check your credentials
Repeated authentication failures from your IP may result in temporarily lowered rate limits.
Contact support
If you've tried the above fixes and still need additional help, contact Customer Support for other options.