Start using a sub-account
Once a sub-account has been submitted and approved, there are two things left to do before you can use it: get the nominated director/authorised signatory to accept Verto's Terms & Conditions (Atlas for Platform only), and authenticate as the sub-account so you can operate on its behalf.
The flow
| Atlas for Platform | Atlas for Fintech | |
|---|---|---|
| After approval | The director must accept Verto's Terms & Conditions before the sub-account is active | No T&C step. Sub-accounts are auto-approved on data submission and sanctions screening |
| To start operating | Authenticate as the sub-account | Authenticate as the sub-account |
Step 1: Director T&C acceptance (Atlas for Platform only)
Every Atlas for Platform sub-account is a legally isolated Verto customer. The sub-account's director must accept Verto's Terms & Conditions, which also grants your platform permission to operate the account. Until they do, the sub-account can't be used.
Emails are sent directly to the director by Verto, to ensure that legal agreement is formed for the provision of financial services to that entity.
Before you start
- The sub-account's
companyStatusmust beAPPROVED - At least one shareholder must be flagged as a director (
isControllingOfficer: true) with a valid email address, submitted through the onboarding data endpoint
Directors are mandatory, with an email address, for all Atlas for Platform sub-accounts. If no director has been added, this step will fail.
Send the email
Call Send T&C email with the sub-account's company ID as subCompanyId in the path, and the director's details in the body:
{
"email": "[email protected]",
"shareholderId": "shareholder-id-from-onboarding-data"
}| Field | Description |
|---|---|
email | The address the Terms & Conditions link will be sent to. Use the director's email from onboarding |
shareholderId | The ID of the director to email. Must be an active, UBO-approved director (controlling officer) of the sub-account. Get it from the shareholders list returned by Get Onboarding Data for the sub-account |
| Status | Meaning |
|---|---|
200 | Email sent and the sub-account's linked status updated to pending acceptance |
400 | The shareholder exists but is not a director of the sub-account |
404 | Sub-account not found, or shareholderId doesn't match an active, UBO-approved director |
401 | Unauthorized |
500 | Server-side error |
What happens next
The director receives an email, reviews Verto's Terms & Conditions and accepts them. When they do, the sub-account's linkedStatus moves from PENDING to ACCEPTED, and the sub-account is fully active.
If the director says they haven't received the email, check that the address submitted during onboarding is correct before sending it again. If the problem continues, contact [email protected].
Step 2: Authenticate as the sub-account
Everything you do on a sub-account, including creating wallets, receiving funds, converting currency and making payouts, is done as that sub-account. Call Sub-Account Login with the sub-account's company ID as subCompanyId in the path to get a sub-account token.
Send that token as a Bearer token on every request you make on behalf of the sub-account. Tokens are time-limited (1 hour). When one expires, call Sub-Account Login again for a new one. Each token belongs to a single sub-account, so request a separate token for each sub-account you operate.
| Status | Meaning |
|---|---|
200 | Returns the sub-account token |
400 | Unacceptable request |
401 | Unauthorized |
403 | The sub-account's onboarding was rejected, or the company is archived |
500 | Server-side error |
This applies to both Atlas for Platform and Atlas for Fintech. If the call returns a403, the sub-account can't be operated and you should contact [email protected].
What you can do next
With the sub-account active and a token in hand, you're ready to start using it:
| Task | Guide |
|---|---|
| Create wallets in the currencies you need | Wallets |
| Generate account details and receive funds | Funding wallets |
| Convert between currencies | FX overview |
| Send payouts to beneficiaries |
In this section
| Endpoint | Description |
|---|---|
POST Send T&C email | Sends the Terms & Conditions acceptance email to a sub-account's director (Atlas for Platform only) |
POST Sub-Account Login | Returns a token to authenticate as the sub-account |
Need help?
If you have questions about your integration or need support, contact our enterprise API support team at [email protected] or reach out to your account manager directly.

