Choosing your model
Verto's API gives businesses access to payments, collections, FX, and multi-currency accounts — whether you are managing your own funds, or building embedded financial services for your underlying clients.
Choosing the right model before you integrate is important — each has different compliance requirements, onboarding flows, currency coverage, and relationship structures. Getting this right upfront avoids rework and ensures your integration is built on the correct compliance framework from day one.
Verto supports three distinct integration models depending on your use case, regulatory status, and the nature of the funds you are moving. Choosing the right model before you integrate is important — each has different compliance requirements, onboarding flows, and product capabilities.
If you are unsure which applies to your use case, contact [email protected] or speak to your account manager before starting your integration.
Quick decision guide
| Question | If YES | Recommended model |
|---|---|---|
| Are you moving your own funds — paying suppliers, managing treasury, pre-funding nostro accounts, or receiving into your own account? | You are the principal sender or receiver | Corporate / Own Funds |
| Do you need to collect or pay on behalf of underlying clients, and you are a directly regulated FI with an independent AML audit? | Verto places reliance on your compliance framework | Atlas for Fintech |
| Do you need to collect or pay on behalf of underlying clients, and you are not regulated or do not have an independent AML audit? | Verto handles compliance directly per client | Atlas for Platform |
| Do you need USD, GBP, or EUR sub-accounts for your clients? | G10 currencies require Platform | Atlas for Platform |
| Do you want to earn revenue via FX markup on client conversions? | FX markup is only available on Platform | Atlas for Platform |
The three models
Corporate / Own Funds
For businesses and financial institutions moving their own funds. No sub-account infrastructure required. Your business is the principal sender or receiver of funds throughout — the recipient can be a third party (supplier, vendor, contractor, counterparty) as long as the funds originate from your own balance.
Covers: payroll, supplier payments, treasury FX, nostro pre-funding, 1st party collections, and intercompany transfers.
See the Corporate / Own Funds guide
Nested and downstream activityVerto operates automated systems to detect nested or downstream payment activity conducted through corporate or financial institution accounts outside of the Atlas product. Using a corporate or own funds account to collect or pay on behalf of underlying third-party clients — without the appropriate Atlas compliance framework in place — is a breach of Verto's terms of service. This will result in account suspension and, where applicable, reporting to the relevant regulatory authorities where unlicensed activity is identified.
🏛️ Atlas for Fintech
Atlas for Fintech is designed for regulated financial institutions that want to embed Verto's payment and FX infrastructure to serve their own underlying clients. You retain the compliance relationship with your clients — Verto assesses your internal controls and places a level of reliance on your existing framework.
- Best for: Directly licensed financial institutions (Fintechs, Neobanks, PSPs, MSBs, MTOs).
- How Compliance Works: You keep full ownership of your end-clients. Verto relies on your existing KYB/KYC processes after completing a Downstream Compliance Assessment.
- Key Capabilities:
- Collect (COBO) for corporate clients only; Pay out (POBO) for both corporates and individuals.
- Access emerging market currencies (NGN, KES, ZAR, TZS, XOF, XAF).
- Key Limitations: Does not support major G10 currencies (USD, GBP, EUR) at the sub-account level or FX markups.
See the Atlas for Fintech guide
🌐 Atlas for Platform
Atlas for Platforms is designed for non-licensed, non-financial businesses that want to offer embedded cross-border financial services to their clients under Verto's licensing and infrastructure.
- Best for: Non-regulated businesses, marketplaces, SaaS/Payroll platforms, white-label brokers, or fintechs without an independent AML audit.
- How Compliance Works: Verto directly verifies each sub-account and holds the financial service relationship under Verto's licenses. Your clients accept Verto's Terms & Conditions.
- Key Capabilities:
- Full Currency Access: Includes G10 currencies (USD, GBP, EUR) alongside emerging markets.
- Monetization: Generate platform revenue by adding custom FX markups to client conversions.
- No License Needed: Operates entirely under Verto's regulatory licenses.
See the Atlas for Platform guide
At a glance
| Corporate / Own Funds | Atlas for Fintech | Atlas for Platform | |
|---|---|---|---|
| Who it's for | Corporates and FIs moving their own funds | Regulated FIs serving underlying clients | Platforms and non-regulated businesses serving underlying clients |
| Sub-accounts required | No | Yes (SUB_CLIENT) | Yes (PARTNER_REFERRED) |
| Compliance model | Standard Verto onboarding | Reliance-based — Verto relies on your KYB/KYC | Full KYB/KYC per sub-account conducted by Verto |
| Own licence required | No | Yes — directly regulated entity with AML audit | No — Verto's licensing covers your clients |
| Currency coverage | Full — all Verto currencies | Emerging markets only (NGN, KES, ZAR, TZS, XOF, XAF) + G10 currencies (case by case) | Full — including G10 (USD, GBP, EUR) |
| Collections (COBO) | Own account only | Corporates only | Supported - Corporates only |
| Payouts (POBO) | Own funds only | Corporates and individuals | Supported - Corporates only |
| FX markup | Not applicable | Not available | Available |
| Sender object required | No | Yes — for POBO flows if via master account | No — inherited from sub-account KYB |
🔀 Side-by-side use case examples
| Use case | Recommended model | Why |
|---|---|---|
| Business paying suppliers and vendors in local currency | Corporate / Own Funds | Principal sender — funds originate from the business's own balance |
| Payroll platform disbursing salaries to employees across Africa | Corporate / Own Funds | Business is sender of record for its own payroll obligations |
| Financial institution converting between its own currency positions | Corporate / Own Funds | 1st party FX — institution is converting its own funds, not acting on a client instruction |
| Bank or PSP pre-funding a nostro or correspondent account | Corporate / Own Funds | Funding a liquidity position in the institution's own name |
| Fintech offering NGN and KES collection accounts to corporate clients | Atlas for Fintech | Directly regulated, COBO for corporates, emerging market currencies |
| Remittance provider paying out to individuals across Africa | Atlas for Fintech | Directly licensed MTO, POBO for individuals supported |
| Licensed PSB collecting on behalf of corporate clients in ZAR | Atlas for Fintech | Regulated entity, emerging market currency, reliance-based model |
| Fintech helping businesses pay overseas suppliers in local currency — licensed MTO/PSP | Atlas for Fintech | Directly regulated, paying on behalf of corporate clients, reliance placed on their compliance framework |
| Fintech helping businesses pay overseas suppliers in local currency — non-licensed technology platform | Atlas for Platform | Non-regulated, Verto conducts full KYB/KYC on each underlying business client directly |
| B2B marketplace offering USD accounts to merchant clients | Atlas for Platform | Non-regulated platform, USD sub-accounts required |
| Payroll SaaS platform disbursing salaries in multiple African markets | Atlas for Platform | Non-regulated, disbursing on behalf of employer clients |
| White-label FX broker applying custom rates to end clients | Atlas for Platform | FX markup only available on Platform model |
| Fintech without an independent AML/FinCrime audit | Atlas for Platform | Cannot pass Downstream Assessment — Verto handles compliance directly |
| Consumer wallet provider offering multi-currency accounts to users | Atlas for Platform | End-users are Verto's direct clients, full KYC per user required |
| E-commerce platform collecting payments on behalf of merchants | Atlas for Platform | COBO for underlying merchants, non-regulated platform |
Getting started
Once you have identified the right model, contact your account manager or [email protected] to begin the qualification process:
- Corporate / Own Funds — standard Verto onboarding applies. Once your account is live you can begin using APIs in production immediately.
- Atlas for Fintech — your account manager will guide you through the Downstream Compliance Assessment before API access is enabled.
- Atlas for Platform — your account manager will initiate the partner setup process and commercial agreement before API access is enabled.
If you are still unsure which model applies to your use case, contact [email protected] or speak to your account manager before starting your integration.
Updated about 2 hours ago

