How platforms use virtual accounts and mass payouts

Platforms use virtual accounts to give each of their users local account details, and mass payouts to pay many recipients at once into bank accounts or mobile money wallets. With Verto Atlas, a platform adds both through one integration, or on the Verto platform if it has no developers free. Your users stay in your product while Verto runs the accounts and payments behind it. This guide is written for the operations or finance lead.

What is a virtual account for a platform?

A virtual account gives your user their own account details in a currency's home country, so they can receive money by domestic transfer. On Atlas, your platform opens a sub-account for each user, and each user gets their own virtual accounts to receive money locally in NGN, KES, TZS, AED, XOF, XAF, ZAR, DKK, UGX, USD, GBP and EUR.

For the payer, it feels like paying a local account. For your platform, each payment lands in the right user's account with a clear reference. Availability for each currency depends on your business and use case, so confirm your markets with Verto's team.

What are mass payouts?

Mass payouts send money to many recipients in one run, straight to bank accounts or mobile money wallets. Platforms use them to pay sellers, contractors, freelancers or remittance recipients across Africa without sending each payment by hand.

In many African markets a recipient's main account is a mobile wallet, and the GSMA's State of the Industry Report on Mobile Money tracks how central these wallets have become. Paying into them, as well as into bank accounts, means recipients receive money in the account they already use.

Which platforms use virtual accounts and mass payouts?

Atlas for Platforms is designed for marketplaces, software companies, expense management platforms and brokers that want to embed payments, virtual accounts, cards and other financial services into a product that wasn't built as a financial one. The common thread is that the platform serves its own end users and wants to offer money features without becoming a finance company.

Financial companies such as payment service providers and banks use Atlas for Fintechs instead, to embed collections, FX and payouts in their own products.

What can a platform offer with Atlas?

How should you structure accounts for your users?

Your platform holds a parent account and opens a sub-account for each user, with wallets in the currencies they need. You manage them centrally through the Verto platform or the API. Decide the structure before launch, because changing it later means moving balances.

A common starting point is one sub-account per user and one wallet per currency. Agree the payment reference format at the same time, because reconciliation relies on it.

How do mass payouts work in practice?

You choose the recipients, amounts and currencies, and start the run through the API or on the Verto platform. Funds go to bank accounts or mobile money wallets. Webhook notifications tell your system when each payout succeeds or fails, so you can update balances without polling or checking by hand.

Conversion runs 24/7 through the API, so a payout run scheduled for a Saturday can be converted on Saturday. Beyond Africa, global payments reach 100+ countries in 48 currencies.

Example: how a marketplace uses them

A marketplace is one example of a platform, so here is the flow, illustrated rather than based on a real customer. A buyer pays a seller's virtual account by domestic transfer, over rails such as NIBSS Instant Payment in Nigeria or PesaLink in Kenya. The money lands in the seller's sub-account. The seller holds it or converts it. The marketplace then pays sellers out in a batch, to bank accounts or mobile money.

B2B marketplaces can also use Verto to store client funds and facilitate transactions between their users.

Who does what in your team?

Splitting responsibilities early avoids gaps:

What should you monitor every day?

Reconcile your own ledger against what Verto reports daily, not monthly. Watch three things: incoming payments without a matching user, payouts that failed or were returned, and conversions awaiting action. Keep a record of every payout run so a dispute can be checked in minutes. Atlas comes with 24/7 customer support and a dedicated account manager who knows your set-up.

Do you need developers?

Not necessarily. You can run everything Atlas offers directly on the Verto platform, or use the API for full control inside your own product. Teams often start with payout runs on the platform while engineering builds the API flow.

Triply, an African travel platform, used the Atlas API to run its payment operation in one integration: issuing virtual accounts, converting currency in real time and paying out funds. A process that took several days and several vendors became one automated flow.

What stays with your platform?

Atlas supplies the accounts, conversion and payouts. You still own your user terms, your support and how you present fees. Take legal advice on how your product and terms fit the rules in each market you serve. [VERIFY] Confirm with Compliance how to describe Verto's role in checking end users.

If you want API access to run your own company's payments and FX, rather than offer them to your users, Verto's Core API is the better fit. To compare providers on the same terms, use our checklist for choosing an embedded finance provider.

Launch checklist

1. Choose your first markets and currencies.

2. Agree the sub-account structure and payment reference format.

3. Set the FX policy and who approves payout runs.

4. Connect webhooks and test a failed payout.

5. Run a small pilot payout before opening to all users.

Keeping every user's money visible and under control lets a platform grow without losing track. To discuss your markets and whether the API or the Verto platform suits you, speak to our team about Verto Atlas or Get started.