Stress testing policy

As your business grows, you might be interested in understanding how our API performs under heavy load. This guide explains our policies regarding stress testing and load testing, and provides information about our infrastructure's capability to handle high-volume transactions. We've designed our system to be reliable and scalable, eliminating the need for individual performance testing while ensuring your integration remains robust.

Understanding our policy

We maintain this policy to ensure:

• Consistent performance for all our customers
• System stability and reliability
• Fair resource allocation
• Protection against potential DDoS-like behavior

Infrastructure and reliability

Our platform is built on a robust, elastic infrastructure designed to handle varying loads efficiently:

• Auto-scaling architecture: Our services automatically scale based on demand
• Event queuing system: All events are properly queued and processed with guaranteed delivery
• Event replay capability: In case of any issues, events can be replayed to ensure data consistency
• Disaster recovery: Multiple redundancy layers and automated failover mechanisms
• Geographic distribution: Services are distributed across multiple regions for optimal performance

Sandbox environment limitations

While our sandbox environment is designed for testing your integration, it is not meant for:

• Load testing
• Stress testing
• Performance benchmarking
• Automated mass request testing

Our sandbox environment has the same rate limits as production. These limits are in place to maintain system stability and ensure fair usage for all developers.

Alternatives for performance testing

If you need to evaluate the performance of your integration with our API, we recommend:

1. Integration testing: Focus on testing your implementation's correctness rather than performance
2. Unit testing: Test your code's behavior with mocked API responses
3. Staged testing: Gradually increase your transaction volume in production

Getting authorization for load testing

If your business case requires performance testing:

1. Contact our support team with:

   • Your use case
   • Expected request volumes
   • Preferred testing window
   • Test plan details

2. We will review your request and may:

   • Provide a dedicated testing environment
   • Schedule a supervised testing window
   • Offer alternative solutions

Best practices for production

When going live with your integration:

1. Gradual ramp-up: Increase your transaction volume gradually
2. Monitor response times: Keep track of API response times and error rates
3. Implement retries: Use exponential backoff for failed requests
4. Cache when possible: Cache responses where appropriate to reduce API calls