Choose the right APIs
Choose the Verto integration model that matches your compliance ownership, customer relationship, and technical implementation pattern.
Choose Your Integration Path
Choose the Verto integration model that matches your compliance ownership, customer relationship, and technical implementation pattern.
✅ Before you choose a path
Answer these questions first:
- Are you moving your own funds or acting on behalf of downstream customers?
- Who owns KYB or KYC for the end user: your business or Verto?
- Do you need isolated sub-account balances and actions for each customer?
- Do you need advanced capabilities like booked FX execution, embedded account issuance, or downstream customer onboarding?
🏛️ The Atlas Comparison Matrix
| Feature | 🏦 Atlas for Fintech | 🏢 Atlas for Platforms |
|---|---|---|
| Regulatory Tier | Licensed (Bank, EMI, PSP). | Non-Licensed (SaaS, Marketplace). |
| KYB Ownership | Partner-led (You verify users). | Verto-led (We verify users). |
| Go-Live Speed | High (1-3 weeks). | Standard (Varies by user). |
| Auth Model | Master Identity. | Scoped sub_acc_id Context. |
📦 Feature Availability Tiers
While both paths share the core API gateway, certain institutional features are tailored for specific tiers.
| Capability | Atlas Fintech | Atlas Platforms |
|---|---|---|
| Corporate Wallets | ✅ | ✅ |
| Sub-Account Segregation | ✅ | ✅ |
| Wholesale FX Liquidity | ✅ | ✅ |
| Booked FX Execution | ✅ | ✅ |
🚀 Choosing Your Trajectory
🎯 Case A: "I want to build a Neo-Bank"
Your Path: Atlas for Fintech. You handle the customer relationship and regulation; Verto serves as your global clearing and treasury rail.
Start with Quickstart, then move into Wallets, FX Conversion Guide, and Send.
🎯 Case B: "I want to enable my merchants to get paid"
Your Path: Atlas for Platforms. Verto acts as the regulated partner for your merchants, handling their KYB while you provide the software orchestration.
Start with Sub-Accounts, Create a Sub-Account, Create Wallets, and Receive.
🤝 Understanding Relationship & Routing Models
Routing items effectively depends on the legal relationship type established within the Atlas ecosystem.
👥 The 'Referred Client' Model (Atlas for Platforms)
- Structure: The end-client (your user) has a direct contractual relationship with Verto.
- Routing: The platform acts as a "Parent Account" with operator permissions. Funds route through Verto-verified sub-accounts to ensure full compliance oversight.
- Best For: Markets requiring strict Verto-led KYB (e.g., E-commerce, Marketplaces).
👥 The 'Sub-Client' Model (Atlas for Fintechs)
- Structure: The end-client has a relationship only with you (the Partner). You own the financial services relationship.
- Routing: Verto relies on your compliance framework (Nested Assessment). Funds route through your master balance into partitioned sub-ledgers.
- Best For: Regulated FIs, MSBs, and PSPs with their own compliance maturity.
🎯 Next Steps
| Core Concepts → Understand the core primitives behind wallets, accounts, and rails. | Go-Live Requirements → Review the approval path for production. |
Updated about 1 month ago