Skip to main content

Overview

Transaction API implements rate limiting to ensure fair usage and system stability. Different endpoints have different rate limits based on their resource requirements.

Rate Limit Tiers

Authentication

5 requests/minute
  • /auth/register
  • /auth/login
  • /auth/verify-email
  • /auth/resend-verification

Payment Creation

10 requests/minute
  • /payment/create
  • /payment/select-crypto

Other Endpoints

100 requests/minute
  • All other API endpoints

Rate Limit Headers

All API responses include rate limit information in the headers:
integer
Maximum requests allowed per window
integer
Number of requests remaining in current window
integer
Unix timestamp when the rate limit resets

Rate Limit Exceeded

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:

Best Practices

Implement Exponential Backoff

Monitor Rate Limit Usage

Batch Operations

Instead of making multiple individual requests, batch operations when possible:

Rate Limit Strategies

For High-Volume Applications

1

Implement Caching

Cache frequently accessed data to reduce API calls.
2

Use Webhooks

Subscribe to webhook events instead of polling for updates.
3

Batch Requests

Combine multiple operations into single requests when possible.
4

Queue Operations

Use a queue system to manage request timing and avoid bursts.

For Development

1

Use Sandbox Mode

Test with sandbox mode which has higher rate limits.
2

Implement Delays

Add delays between requests during development.
3

Monitor Headers

Always check rate limit headers in your responses.

Monitoring and Alerts

Set Up Monitoring

Alert Configuration

Set up alerts when approaching rate limits:

Common Scenarios

Scenario: High-volume payment processingSolution:
  • Use webhooks instead of polling payment status
  • Implement request queuing
  • Cache product and price data
Scenario: Frequent API calls from mobile devicesSolution:
  • Implement local caching
  • Batch multiple operations
  • Use background sync
Scenario: Real-time data fetching for dashboardsSolution:
  • Use WebSocket connections
  • Implement data aggregation
  • Cache dashboard data

Rate Limit Increases

For applications requiring higher rate limits:
  1. Contact Support: Reach out to our support team with your use case
  2. Provide Metrics: Share your current usage patterns and requirements
  3. Business Justification: Explain why higher limits are needed
  4. Implementation Plan: Show how you’ll handle the increased volume
Enterprise Plans: Higher rate limits are available for enterprise customers. Contact sales for more information.