Rate Limiting

We are committed to maintaining a 99.9% service uptime and take proactive measures to prevent abuse of our systems.

To ensure fair usage, our rate-limiting mechanism restricts excessive requests within a short period. If we detect unusually high traffic from a user, a 429 Too Many Requests response will be returned, and access to the service will be temporarily blocked.

Repeated or continuous misuse of our APIs may result in more severe access restrictions.

1. Webhooks: For faster and more efficient communication, we recommend using webhooks rather than polling. When a merchant provides a webhook URL, we send real-time notifications to it as events occur. If the webhook is temporarily unreachable, our system will automatically retry delivery.

   Learn more in the Webhooks section.

   
   

1. Structured polling:Instead of continuously polling for transaction updates, use a background worker or scheduled service that runs at longer intervals—such as every 30 minutes—to check transaction status. Once a transaction is marked as successful, further polling is unnecessary. For real-time updates, it's best to use webhooks, which are more efficient and reliable than polling.