Sub-Accounts

What is a sub-account?

A sub-account is a fully isolated entity that sits under your parent Verto account.
Each sub-account has its own independent wallet structure — meaning a sub-account
can hold multiple currencies simultaneously, with each currency held in a separate
wallet under that sub-account. A sub-account is not a single-currency construct;
it is a complete financial unit.

All core Verto functionality — collections, FX, payouts, and wallet management —
can be performed at the sub-account level without touching the parent account.
This makes sub-accounts well suited to embedded finance use cases where each
underlying client needs collect, convert or payout funds.

---

When do you need a sub-account?

Sub-accounts are required when you are building an embedded finance product and need to segregate funds, wallets, and payment flows per underlying client.

Sub-accounts are not required for:

• Corporate use cases — where your business is sending or receiving funds on
  its own behalf
• Bulk disbursement — paying multiple recipients from your own master wallet
• Financial institutions making payouts from their master wallet on behalf of
  underlying customers — even for FI use cases, sub-accounts are not needed if
  you are operating from a single master wallet using the sender object to identify
  the underlying party

If you are unsure whether your use case requires sub-accounts, contact your Sales/account manager or reach out to [email protected]

---

The two sub-account models

Verto offers two sub-account models depending on your regulatory setup and the nature of your underlying clients. The right model for your integration depends on your compliance framework, client base, and currency requirements — speak to your account manager or contact [email protected] for guidance before
integrating.

Atlas for Fintech — SUB_CLIENT

Designed for fintechs and financial institutions with existing regulated compliance infrastructure. Under this model:

• Verto assesses your internal compliance controls and AML framework
• A level of reliance is then placed on your own KYB/KYC processes for
  underlying clients
• Sub-accounts are auto-approved once required data is submitted — no manual
  review per client
• Currency coverage is more limited under this model as a result of the reliance
  approach

Best for fintechs with a regulated compliance programme already in place who want to onboard underlying clients at scale without individual Verto review.

Atlas for Platform — PARTNER_REFERRED

Designed for platforms, marketplaces, and neobanks onboarding their own clients as independent entities. Under this model:

• Verto conducts full KYB and KYC on each sub-account directly
• Each sub-account director must accept Verto's Terms & Conditions and consent
  to the platform operating their account
• Broader currency coverage is available as a result of full Verto verification
• An FX markup can be applied to sub-account trades to generate platform revenue

Best for platforms where each underlying client is a distinct legal entity that
needs to be fully onboarded and verified by Verto.

---

Choosing the right model

The two models have different compliance requirements, onboarding flows, and currency coverage. Before integrating, speak to your account manager - they can help assess
which model fits your use case and confirm currency availability for your target
corridors.

---

Core API flows

All core Verto functionality is supported at the sub-account level. The table
below gives a high-level overview — refer to the linked guides for full
integration details.

---

Key limitations

Sweeping funds to the parent account

PARTNER_REFERRED sub-accounts cannot sweep funds to the parent account by default. All funds must remain within the sub-account and be managed at that
evel for risk and regulatory reasons.

If sweeping to the parent account is required for your use case, this
requires prior compliance approval — contact [email protected] to discuss this.

Examples of support used cases - payment of subscription fees.

Examples of not supported use cases - aggregation of client funds.

FX markup

For PARTNER_REFERRED (Atlas for Platform) accounts, an FX markup can be applied to sub-account trades to generate revenue on conversions. See the FX Markup guide for details.

Currency coverage

Currency and corridor availability differs between the two models. Confirm coverage for your target markets with your sales/account manager before integrating.

---

Getting started

For full integration guides covering onboarding, collections, FX, and payouts,see the relevant product section:

- Atlas for Fintech — for fintechs and financial institutions using the SUB_CLIENT model
- Atlas for Platform — for platforms and marketplaces using the PARTNER_REFERRED model