Quickstart

Create a sandbox account, authenticate with Verto, and make your first API request as either a direct fintech integration or a platform integration.

1. Complete the setup steps

1. Create or access your sandbox environment in Environments.
2. Generate your Client ID and API Key in Access Your Credentials.
3. Review Authentication and choose your authentication method.
4. Decide whether you are integrating as a direct fintech or as a platform managing sub-accounts.
5. Configure the service-specific sandbox base URLs you need. Start with Login at https://api-company-sandbox.vertofx.com and Wallet at https://api-wallet-sandbox.vertofx.com.

🧪

Sandbox access

Sandbox lets you test both Atlas for Fintech and Atlas for Platforms before you request production access. Review Go-Live Requirements → before you plan your production rollout.

🛣️ Choose Your Setup Path

Choose the path that matches how you will move funds through Verto.

2. Make your first API request

Use the direct flow if you are moving your own funds. Use the platform flow if you need to isolate balances and actions per downstream customer.

🏦 Fintech Integration (Master Ledger)

Use this flow when you manage your own wallets directly.

# 1. Create the access token and store companyId
curl -X POST https://api-company-sandbox.vertofx.com/users/login \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "YOUR_CLIENT_ID",
    "apiKey": "YOUR_API_KEY",
    "mode": "apiKey"
  }'

# 2. Create the company wallet
curl -X POST https://api-wallet-sandbox.vertofx.com/YOUR_COMPANY_ID/wallets \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "currency": "GBP",
    "type": "standard",
    "customReferenceLabel": "Default GBP Wallet"
  }'

When this request succeeds, you have a bearer token, a companyId, and a wallet ID to build on. Your next step is usually to inspect the wallet, fund it, or continue into receive, exchange, or send flows.

🏢 Atlas Platform Integration (Sub-Account Ledger)

Use this flow when you need to scope actions to a specific downstream customer with X-Sub-Account-Id.

# 1. Create the master access token and store companyId
curl -X POST https://api-company-sandbox.vertofx.com/users/login \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "YOUR_CLIENT_ID",
    "apiKey": "YOUR_API_KEY",
    "mode": "apiKey"
  }'

# 2. Create the customer sub-account
curl -X POST https://api-onboarding-sandbox.vertofx.com/sub-accounts \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "TechStartup LLC",
    "country": "United Kingdom",
    "subCategory": "Advertising & marketing company",
    "identificationNumber": "UK12345678",
    "accountType": "sub_client"
  }'

# 3. Create the wallet using the merged wallet service
curl -X POST https://api-wallet-sandbox.vertofx.com/YOUR_COMPANY_ID/wallets \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "currency": "GBP",
    "type": "standard",
    "customReferenceLabel": "Customer GBP Wallet"
  }'

When these requests succeed, you have validated the core platform pattern: authenticate, create the downstream customer context, then use the merged service routes for wallet and money-movement workflows.

Use a subCategory value from Supported Industry Classifications when you create the sub-account.

Use the migrated company login route shown above for sandbox authentication. Do not use legacy api-v3-sandbox.vertofx.com/users/login or older unified auth paths for new quickstart implementations.

Use Environments to find the merged service host for each API area, including Wallet, Beneficiary, Exchange, Payment, and Onboarding.

Optional: Common sandbox mistakes to avoid

Watch for these issues while you build:

• ❌ Expired tokens: Bearer tokens expire after 60 minutes, so your backend should refresh them before retrying protected requests.
• ❌ Missing idempotency keys: Retrying write operations without an Idempotency-Key header can create duplicate payments.
• ❌ Wrong environment: Do not mix sandbox credentials, service hosts, and production configuration.

🎯 Next Steps

Once your first request works, move into the guide or use case that matches your integration.