Sandbox Base URL
Getting Started
You use the same Yativo account for both sandbox and production. Switch between environments by changing the base URL in your requests.- Sign up at app.yativo.com (if you haven’t already)
- Get your credentials — Dashboard → Developer → API Key
- Authenticate using the sandbox base URL:
Sandbox Behavior
| Feature | Sandbox | Production |
|---|---|---|
| Payments | Simulated — no real funds | Real money moves |
| KYC | Auto-approves instantly | Takes minutes to hours |
| Virtual accounts | Work end-to-end | Live bank accounts |
| Exchange rates | Live rates returned | Live rates |
| Webhooks | Fired normally | Fired normally |
| API logs | Recorded | Recorded |
How to Test
Authenticate
Use the same Account ID and App Secret. Call
POST /auth/login against the sandbox URL to get a token.Create test customers
Use
POST /customer to create customers. KYC auto-approves in sandbox — no documents needed.Create virtual accounts
Once a customer is created (KYC auto-approved), call
POST /business/virtual-account/create.Simulate deposits
Use the sandbox dashboard or API to trigger test deposits to your virtual accounts.
Example: Full Sandbox Test Flow
Node.js
Differences from Production
- KYC is instant — submit a customer and
is_kyc_submitted/is_va_approvedare set immediately - No real funds — wallet balances may be pre-funded in sandbox; payouts simulate the full transaction lifecycle
- Some payment methods may be limited — not all live corridors are available in sandbox; contact your integration team if you need a specific one
- Webhooks fire normally — you’ll receive all webhook events in sandbox; make sure your test endpoint is reachable
Switching to Production
When you’re ready to go live:- Change your base URL from
https://smtp.yativo.com/api/v1tohttps://api.yativo.com/api/v1 - Ensure your business KYC is approved in the dashboard
- Real customers will need to complete KYC (not auto-approved)
- Update your webhook URL to point to your production endpoint
Your Account ID and App Secret are the same for both environments. Only the base URL changes.

