Why Two Environments?
Revolv3 provides two separate environments so you can safely test your integration before processing real payments. This prevents mistakes, protects your customers, and ensures everything works correctly before going live.Sandbox Environment
The sandbox is a testing environment that mimics production but doesn’t process real payments.What It’s For
- Development: Build and test your integration
- Testing: Try different scenarios without risk
- Learning: Understand how the API works
- Debugging: Fix issues before going live
Key Details
| Aspect | Details |
|---|---|
| Portal URL | portal-sandbox.revolv3.com |
| API URL | api-sandbox.revolv3.com |
| Real Money | No — uses test data only |
| Real Cards | No — use test card numbers |
| Credentials | Separate sandbox API key |
| Processors | Uses processor test environments |
When to Use Sandbox
- You’re building your integration
- You’re testing new features
- You’re debugging issues
- You’re learning how the API works
- You want to try different scenarios safely
Important: Always test thoroughly in sandbox before using production. It’s free, safe, and prevents costly mistakes.
Production Environment
The production environment is for live payment processing with real customers and real money.What It’s For
- Live payments: Process actual customer transactions
- Real revenue: Money actually moves
- Customer data: Real customer information
- Business operations: Your actual payment processing
Key Details
| Aspect | Details |
|---|---|
| Portal URL | portal.revolv3.com |
| API URL | api.revolv3.com |
| Real Money | Yes — actual transactions |
| Real Cards | Yes — customer payment methods |
| Credentials | Separate production API key |
| Processors | Uses live processor systems |
When to Use Production
- Your integration is tested and ready
- You’ve completed certification (if required)
- You’re ready to process real payments
- You understand the API and error handling
Critical: Only use production when you’re confident your integration works correctly. Mistakes here affect real customers and real money.
Key Differences
| Feature | Sandbox | Production |
|---|---|---|
| Purpose | Testing and development | Live payment processing |
| Money | Test transactions only | Real money moves |
| Cards | Test card numbers | Real customer cards |
| API Key | Separate sandbox key | Separate production key |
| Portal | portal-sandbox.revolv3.com | portal.revolv3.com |
| API Endpoint | api-sandbox.revolv3.com | api.revolv3.com |
| Rate Limits | May differ from production | Production limits apply |
| Support | For testing issues | For production issues |
Switching from Sandbox to Production
When you’re ready to go live, follow these steps:1. Complete Testing
- Test all payment flows in sandbox
- Test error handling and edge cases
- Verify webhooks work correctly
- Test with different payment methods
- Complete any required certification
2. Request Production Access
See the Certification & Go-Live Checklist for how to request production access, certification steps (if required), and contact points.3. Get Production Credentials
Revolv3 will provide:- Production portal login
- Production API key (different from sandbox)
- Production merchant account setup
- Any processor-specific credentials
4. Update Your Integration
Update your code to use production endpoints and credentials: Before (Sandbox):Important: Use environment variables or configuration files so you can easily switch between environments.
5. Test in Production (Carefully)
- Start with a small test transaction
- Verify the payment processes correctly
- Check that webhooks are received
- Monitor for any errors
- Gradually increase volume
Important Notes
Credentials Don’t Cross Over
- Sandbox credentials won’t work in production
- Production credentials won’t work in sandbox
- Always use the correct credentials for each environment
Keep Environments Separate
- Use separate API keys for sandbox and production
- Don’t mix test data with production data
- Keep separate code branches or configurations if needed
- Never use production keys in development
Testing in Production
If you need to test in production (after going live):- Use small amounts
- Test with your own payment methods
- Be careful not to charge real customers during testing
- Consider using a test mode or staging account if available
Best Practices
- Always test in sandbox first: Never skip sandbox testing
- Use environment variables: Store API keys and URLs in config, not hardcoded
- Keep credentials separate: Never mix sandbox and production credentials
- Monitor carefully: Watch for errors when first going live
- Have a rollback plan: Know how to quickly switch back if needed
Common Questions
Q: Can I use the same API key for both environments? A: No. Sandbox and production have separate API keys. You’ll get a new key when you’re approved for production. Q: Will my sandbox data transfer to production? A: No. Sandbox and production are completely separate. You’ll start fresh in production. Q: How long can I use sandbox? A: As long as you need. Sandbox is free and available for ongoing testing and development. Q: What if I make a mistake in production? A: Contact Revolv3 support immediately. They can help you resolve issues, process refunds if needed, and prevent further problems.Next Steps
- Obtain API Keys — Get your sandbox and production API keys
- Production Limitations — Understand rate limits and throttling
- Sandbox Environment Limitations — Learn about sandbox-specific limitations
- Make a Payment — Process your first test payment in sandbox