Overview
The sandbox environment:- Does not connect to real accounts or move actual funds
- Simulates production environment to help test various scenarios
- Prepares your integration and ensures readiness for go-live
- Does not replace testing with real accounts and transactions before deployment
- Test session creation and different user scenarios, and integrate accordingly
- Review front-end design and configuration, ensuring they align with your expectations
Base Testing Flow
During testing, follow this sequence:- Authenticate with sandbox using your secret credentials
- Initiate session using test scenario name and desired dynamic parameters
- Launch iFrame with Session ID appended to trigger front-end scenario
- Complete front-end flow by entering specified username/password for that scenario
- “Happy” paths will return a SUCCESS JS event
- “Unhappy” paths will display relevant error screen or event
- Check session status by calling /sessions/status endpoint
Sandbox Environment Access
Your sandbox credentials and base URI will be provided during onboarding. The sandbox environment includes:- API Endpoints: Same as production but with test data
- Dashboard Access: Client dashboard instance for UI familiarization
- Test Data: Predefined scenarios with known outcomes
- Event Simulation: Full event flow testing capabilities
Authentication
Use your sandbox credentials exactly as you would in production:- Include your API key in the
x-api-keyheader and your client ID in thex-client-idheader - Use these headers for all API calls during testing
Next Steps
Once you understand the sandbox basics:- Test Scenarios: Learn about specific test cases and user flows
- Testing Best Practices: Implement automated testing
- Production Readiness: Verify you’re ready to go live
Related Documentation
- Setup Guide: Implementation steps
- Event Handling: Frontend event integration
- API Reference: Complete API documentation