Environments
Choose the correct Verto environment, configure service-specific sandbox routes, and prepare your application to move safely from sandbox to production.
Environments
Use this page to choose the correct Verto environment, configure the right base URL, and prepare your application to move safely from sandbox to production.
1. Pick the environment for your current stage
Use sandbox while you build and test your flows. Move to production only after your authentication, webhook handling, idempotency, and compliance requirements are ready.
| 🧪 Sandbox (Non-Production) | 🚀 Live (Production) | |
|---|---|---|
| Base URLs | Use the service-specific sandbox hosts listed below. | Use the production hosts provided during go-live onboarding. |
| Objective | Test authentication, wallet, beneficiary, FX, payment, and onboarding workflows. | Authorized live transaction routing and definitive settlements. |
| Rate Limit | 100 Requests / Min | 60 Requests / Min |
2. Configure your environment variables
Set your API base URL, credentials, and any webhook or callback configuration separately for each environment. Do not reuse production secrets in sandbox or commit live values to shared repositories.
🔄 New service sandbox routes
Use the API reference for the exact request schema for each endpoint. The merged services use service-specific sandbox hosts instead of a single shared base URL.
| Service | Sandbox host | Key reference pages |
|---|---|---|
| Login | https://api-company-sandbox.vertofx.com | Login |
| Wallet | https://api-wallet-sandbox.vertofx.com | Create wallet, Get all Wallets, Get specific Wallet Details |
| Beneficiary | https://api-beneficiary-sandbox.vertofx.com | Fetch user beneficiaries, Create beneficiary, Fetch beneficiary by ID, Update beneficiary, Delete beneficiary |
| Exchange | https://api-exchange-now-sandbox.vertofx.com | Get FX rate, Get bulk FX rates, Create FX trade, List FX trades, Get FX trade details |
| Onboarding | https://api-onboarding-sandbox.vertofx.com | Add Onboarding Data, Get Onboarding Data, Generate Upload Link |
Do not use legacy api-v3-sandbox.vertofx.com/profile/... routes for new integrations where a new service route is documented above.
Use the service host shown on each API reference page as the source of truth for that endpoint. Some legacy APIs may remain available for older integrations, but new implementations should use the merged service routes where documented.
Critical Warnings
- Never commit active Production parameters to public Git branches!
- Always refresh your bearer tokens dynamically before the 60-minute expiry.
- Use Sandbox mock responses carefully. Sandbox simulates bank routing but does not reproduce real production settlement latency.
🏃 Moving to Production
Use production only after you have validated the full transaction lifecycle in sandbox, including authentication, event handling, and support processes.
| 🏦 Atlas for Fintech (Licensed Integrations) | 🏢 Atlas for Platforms (Embedded SaaS) |
|---|---|
| KYB Verification: Execute your own due diligence and submit your operational license to Verto. Review timeline: 2-4 weeks across external banking channels. Result: Production access for approved direct flows. | KYB Verification: Submit UBOs and onboarding data through the required onboarding flows. Review timeline: Typically 1-3 weeks initially, depending on the model and scope. Result: Production access for approved sub-account flows. |
3. Production rollout checklist
- Execute full QA across your API flows in sandbox.
- Confirm your production credentials, IP allowlisting, and webhook endpoints are ready.
- Complete KYB and commercial approvals with Verto.
- Update your environment variables to the production service hosts provided by Verto.
- Roll out with monitoring enabled for auth failures, webhook delivery failures, and transaction errors.
🎯 Next Steps
| Quickstart Guide → Build and test your first integration in sandbox. | Go-Live Requirements → Review the approval path for production access. |
Updated 10 days ago