Financial Services Onboarding
This guide is for platforms onboarding financial services clients (financial institutions and similar businesses) as sub-accounts under Atlas for Platform. These clients are handled differently from other businesses, so read this before you onboard one.
By default, a financial services sub-account is onboarded for operating expenses (OPEX), first-party and own funds use cases only. It can't make or receive payments on behalf of its own customers. Doing that needs a separate approval, which isn't done through the API (see "Paying on behalf of customers").
At a glance
| What the sub-account wants to do | Included by default? | What's needed |
|---|---|---|
| Move its own money: treasury, operating costs, payroll, suppliers | Yes | Standard onboarding (below) |
| Receive its own money from its own bank accounts, or from collection partners Verto has vetted | Yes | Standard onboarding |
| Pay its own bank accounts, or pre-fund its payout partners with its own money | Yes | Supporting documents when a beneficiary is created, and a contract for payouts |
| Pay out on behalf of its customers (POBO) | No | Downstream assessment, the sender object on every payment, and an extra charge. Speak to your Verto sales contact first |
| Collect on behalf of its customers (COBO), or give its customers their own accounts | Not in scope right now | Sub-accounts can't be nested under a sub-account |
What a financial services sub-account can do by default
Financial services sub-accounts are onboarded as own funds, non-nested activity. In practice that means:
- Treasury and operating payments. Moving the client's own money and paying its own costs, such as payroll and suppliers.
- Money in from its own bank accounts and from collection partners that Verto has already vetted, such as payment acquirers.
- Money out to its own bank accounts (first party), and to pre-fund payout partners with its own funds.
It can't be used for payments related to the client's own customer activity: payments from, to, or on behalf of its customers.
When the client sets up a beneficiary, it must classify it correctly: its own organisation (first party), or a third party. Supporting documents are required at that point to evidence the relationship. A contract must be in place for payouts.
Paying on behalf of customers (POBO)
If a financial services client needs to pay out on behalf of its own customers, it's effectively using the Atlas for Fintech proposition, through you as the technical partner. Extra requirements apply.
POBO has an additional charge for each financial services sub-account, and it's significant. Speak to your Verto sales contact or account manager before you go further with a financial services use case.
1. Talk to your Verto sales contact first.
Agree the use case, the currencies and the cost before anything else.
2. Downstream assessment.
The client must pass Verto's downstream assessment before it can pay on behalf of its customers. This isn't done through the API. Your Verto sales contact starts it. The assessment includes a compliance-to-compliance call with the client's MLRO (Money Laundering Reporting Officer).
3. Send the sender object on every payment on behalf of a customer.
Once approved, each payout made on behalf of a customer must say who the real sender is. Include the sender object in the payout request, and in the FX and payout request. It captures:
- whether the underlying sender is a business or an individual;
- their identification: for example registration number, industry and bank account details;
- their full address.
See Sender information for the full list of fields.
Platforms are normally exempt from the sender object, because a sub-account's sender identity comes from its KYB data. A financial services sub-account paying on behalf of its own customers is the exception. Those customers aren't sub-accounts, so Verto needs the sender details on each payment.
4. Stay within what's approved.
Verto's system flags any payment type a client isn't approved for. Payments on behalf of customers without approval aren't allowed, and Verto monitors for them. Some currencies also need extra approval from our banking partner, which can take around two weeks.
What isn't supported
- Nesting. Verto serves the financial institution's direct customers only. It doesn't serve a non-bank financial institution's own customers through them.
- Crypto and iGaming or betting customers.
Onboarding a financial services sub-account through the API
Use the standard flow in Sub-account onboarding. For a financial services client:
| Item | What to do |
|---|---|
| Industry | Choose the financial services industry from the supported industries list |
| Licence | Send company.licensedCountry and company.licensedType, and upload the active operating licence(s) or permit(s) |
| AML policy | Upload the client's AML (anti-money laundering) policy. It's mandatory for financial services businesses |
| Use case | Onboard the client for own funds use only. Don't set up customer payments until downstream approval is in place |
| Review time | Financial Services clients can take up to 10 working days for review |
Everything else is the same as any other sub-account: directors and owners, documents, submission checks, review and the director's Terms & Conditions.
The journey
| Step | Who | What happens |
|---|---|---|
| 1 | You and your Verto sales contact | You agree the use case. Own funds only, or customer payments too, including cost |
| 2 | You | You onboard the sub-account through the API, with the licence and AML policy |
| 3 | Verto | Compliance reviews the application |
| 4 | The client's director | They accept Verto's Terms & Conditions, and the sub-account becomes active for own funds use |
| 5 | Verto, if customer payments are needed | Downstream assessment, including the MLRO call |
| 6 | You | Customer payments are enabled. You send the sender object on each payment |
Frequently asked questions
Can a financial services sub-account pay on behalf of its customers straight away?
No. By default it is own funds only. Customer payments need downstream approval first.
Can it collect on behalf of its customers, or give them their own accounts?
Not right now. Collections on behalf of customers (COBO) are not in scope, because a sub-account can't be nested under another sub-account. This applies even with downstream approval.
Can I request downstream approval through the API?
No. Ask your Verto sales contact. Verto's compliance team runs the assessment and speaks to the client's MLRO on a compliance to compliance call.
Do we always need the sender object?
For payments made on behalf of the client's customers, yes. For the client's own funds payments, no.
Is there an extra cost?
Yes. POBO has an additional charge for each financial services sub-account, and it's significant. Check with your sales contact or account manager before you start.
This is charged PER underyling POBO use case, since Verto's ongoing monitoring and compliane costs scale on a per sub-account basis.
What if we're not sure whether a payment is own funds or on behalf of a customer?
Ask before you send it. Payments a client isn't approved for are flagged.
Contact [email protected] before going live.
Need help?
Commercial questions, pricing and downstream approval. Contact your Verto sales contact or account manager.
Your integration. Contact our enterprise API support team at [email protected].
Your client's application. Your client can contact Verto's onboarding team at [email protected].
Updated 2 days ago

