Atlas for Platform
Embedded Collections, FX and Payouts for your underlying buisness customers/merchants for non-regulated customer usecases.
Atlas for Platform — overview
Atlas for Platforms is designed for non-financial businesses that want to offer multi-currency financial capabilities to their underlying clients under a single Verto integration, and without becoming a regulated financial institution.
These businesses typically already serve a network of users, merchants, or corporate customers, and want to embed cross-border payments, wallet infrastructure, and FX services directly inside their product.
Each underlying client operates as a legally isolated sub-account — a direct Verto customer who has consented to their account being operated by your platform.
Typical Atlas for Platform verticals include:
| Segment / Business Type | Examples (non-exhaustive) |
|---|---|
| B2B Marketplaces | Global supplier marketplaces, wholesale trade networks |
| Enterprise SaaS Platforms | Procurement tools, logistics & freight systems, invoicing systems |
| Travel & Mobility Platforms | Travel operating systems, corporate expense & booking platforms |
| Global Commerce & Distribution Networks | Franchise networks, food/agro commodity trading hubs |
| Software companies with financial workflows | ERP, treasury management tools, agency platform |
Atlas for Platform vs Atlas for FintechUnlike Atlas for Fintech, all financial activity on Atlas for Platform must originate at the sub-account level. Funds cannot be swept or aggregated to the parent account. Each sub-account is a legally independent entity with its own wallets, collection accounts, and payment flows.
How it works
Atlas for Platform sub-accounts are PARTNER_REFERRED entities — Verto's direct customers, with your platform operating their account on their behalf under their explicit consent. This means:
- All collections, FX, and payouts are initiated at sub-account level
- Your platform authenticates as each sub-account to perform operations on their behalf
- Revenue is generated through FX markup applied to sub-account transactions
- Funds cannot be swept to the parent account
End-to-end flow
The table below outlines the typical end to end flow most Atlas customers require as a baseline.
| Step | API Action | API Reference Link |
|---|---|---|
| Create Sub-Account | Create a new sub-account under the parent account. | Create a Sub Account |
| Add Onboarding Data | Provide required business, shareholder, product, and risk information for each sub account | Add Onboarding data |
| Upload Onboarding Documents | Generate upload links and attach KYC documents. | Generate Upload Link |
| Log In As Sub-account | Log In as a Sub Account to perform actions at sub account level | Login as Sub-Account |
| Create a Wallet | Create a Wallet for Any currency for the sub account | Create Wallet |
| Get Funding Details | Generate collection account details for each sub-account | Get Funding Methods |
| Convert | convert funds at the sub-account level with optional markup applied | Get FX RateSet FX Markup Create FX Trade |
| Payout | disburse funds to external beneficiaries from the sub-account wallet | Create a Payment Request |
**IMPORTANT: **All sub-account operations require authenticating as the sub-account using the Sub-Account Login endpoint. This returns a JWT token valid for 1 hour, which must be included as a Bearer token in all subsequent API calls made on behalf of that sub-account.