Skip to main content

​
Why Sandbox Has Limitations

The sandbox environment is designed for testing, not production workloads. It has limitations to:
  • Prevent abuse: Stop people from using sandbox for production traffic
  • Manage resources: Keep sandbox costs reasonable
  • Simulate real conditions: Some limitations mirror production constraints
  • Maintain stability: Ensure sandbox stays available for all developers
Important: These limitations apply to sandbox only. Production has different (typically higher) limits.

​
WorldPay Sandbox Limitations

If you’re using WorldPay as your processor, these limitations apply in sandbox:

​
Data Retention Policy

  • Maximum retention: Data is retained for a maximum of 30 days
  • Purges may occur more frequently: Depending on system capacity and maintenance
  • Advanced notification: You’ll be notified when possible before data purges
What this means:
  • Test data older than 30 days may be deleted
  • Don’t rely on sandbox data for long-term testing
  • Export or document important test data if you need it longer

​
Maintenance Windows

WorldPay sandbox has scheduled maintenance: General maintenance:
  • Days: Tuesdays and Thursdays
  • Time: 4:00 AM to 8:00 AM ET
  • Impact: Sandbox may be unavailable during these windows
Enterprise eProtect maintenance:
  • Frequency: Every other Thursday
  • Time: 10:00 PM to 6:00 AM ET
  • Impact: eProtect features may be unavailable
What to do:
  • Plan testing around maintenance windows
  • Don’t schedule critical tests during maintenance
  • Check WorldPay status if sandbox seems unavailable

​
Transaction Limits

Online transactions:
  • Daily limit: 1,000 transactions per day
  • Shared capacity: This is shared across all sandbox users, so your actual limit may be lower during peak usage
Batch transactions:
  • Daily limit: 10,000 batch transactions per day
What this means:
  • Don’t run high-volume load tests in sandbox
  • If you hit limits, wait until the next day
  • For high-volume testing, contact Revolv3 about production testing options

​
General Sandbox Limitations

​
Behavior Differences

Sandbox may behave differently from production in:
  • Tokenization: Token behavior may differ
  • Account Updater: Only supported by WorldPay in sandbox
  • Settlement timing: May be faster or slower than production
  • Processor responses: Some processors have different sandbox behaviors

​
Rate Limits

  • Sandbox has rate limits (similar to production)
  • May be more restrictive than production
  • Check with Revolv3 for specific sandbox rate limits

​
Test Data

  • Use only test card numbers and test ACH data
  • Real card numbers will be declined in sandbox
  • Test data is provided by each processor

​
Best Practices

  1. Plan around maintenance: Avoid critical testing during maintenance windows
  2. Don’t rely on long-term data: Export important test data before 30 days
  3. Respect transaction limits: Don’t exceed daily limits
  4. Test incrementally: Build up test volume gradually
  5. Use production for load testing: Sandbox isn’t for high-volume testing

​
Getting Latest Information

For the most current WorldPay sandbox limitations, refer to: WorldPay Sandbox Limits Documentation WorldPay’s documentation is the authoritative source for their specific limitations.

​
Common Questions

Q: Why is my sandbox data gone? A: Sandbox data is retained for a maximum of 30 days. Older data may be purged. Q: Can I increase sandbox transaction limits? A: Sandbox limits are set by the processors. Contact Revolv3 if you need higher limits for testing. Q: What if sandbox is down during maintenance? A: Wait until maintenance completes. Maintenance windows are scheduled and temporary. Q: Can I use sandbox for production-like load testing? A: No, sandbox has lower limits. Use production (carefully) or contact Revolv3 for load testing options.

​
Next Steps