Environment Overview
| Environment | Base URL | Purpose |
|---|---|---|
| Stage | https://stage.tonder.io/api/v1 | Development, testing, and integration validation |
| Production | https://prod.tonder.io/api/v1 | Live withdrawal processing |
Stage Environment
The Stage environment is designed for development and testing purposes. Use this environment to:- Test your integration before going live
- Validate withdrawal request formats
- Test webhook handling
- Verify error scenarios
- Simulate different withdrawal statuses
Test Institution CodeWhen testing in the Stage environment, use institution code 97846 for the
beneficiary_institution field. This is a special test code that simulates bank responses without processing actual transfers.Production Environment
The Production environment processes real withdrawals and transfers funds to actual beneficiary accounts. Only use this environment when:- Your integration is fully tested and validated
- You have completed all testing requirements
- You’re ready to process live transactions
- You have proper error handling and monitoring in place
API Credentials
Each environment requires separate API credentials:- Stage Credentials: Available in the Developers section of the Tonder Staging Dashboard
- Production Credentials: Available in the Developers section of the Tonder Production Dashboard
API keys are environment-specific. Using Stage keys with Production URLs (or vice-versa) will result in authentication errors.
Environment Switching
When switching between environments, ensure you:- Update the base URL in your API client
- Use the correct API credentials for that environment
- Update webhook endpoints if configured
- Verify the environment matches your testing or production needs
Next Steps
- Review integration and security essentials for authentication details
- Check testing requirements for Stage environment testing guidelines
- Learn how to create withdrawals in your chosen environment

