Overview

Atlas for Platforms is designed for non-financial businesses that want to offer financial capabilities to their end-users without becoming a regulated financial institution.

These businesses typically already serve a network of users, merchants, or corporate customers, and want to embed cross-border payments, wallet infrastructure, and FX services directly inside their product.

Typical eligible companies include:

All Sub-Accounts under Atlas operate under a Referred Client model and must complete full Verto onboarding (KYC Level 3) and Terms & Conditions acceptance before they are activated.

This guide explains the API workflow, without repeating endpoint details already documented in the API Reference.

Sub-Account Activation Flow (via API)

The process to activate a Sub-Account is as follows:

When to Use Each Call

Create Sub-Account

Used to register the end-client entity under the Partner’s Parent Account. Fields typically include:

Legal name

Country of registration

Industry classification (sub-category)

Identification / registration number

Optional external reference ID (must be unique if used)

Important Error Case If an /externalId is provided and already exists, the system returns 409 Conflict. Error message example:

externalId already exists for this company

Add Onboarding / KYC Data

After creation, the onboarding data request is used to provide structured compliance information such as:

Selected Product(s) (e.g., Collect, Payout, Exchange)

Company details

Company addresses

Shareholders / Controlling Persons

Supporting documents metadata

Risk assessment responses (jurisdiction rules, business model, etc.)

Only the minimum fields required for activation should be submitted.

Upload Documents

If Verto Compliance requires supporting documentation, document uploads are handled via the Generate Upload Link API.

Documents may include (example types):

Certificate of Incorporation

Proof of Address

Shareholder Identification Documents

UBO Structure Documents

The upload is performed using the returned pre-signed secure link. Document requirements vary by jurisdiction and risk profile.

Terms & Conditions Acceptance

Once onboarding has been reviewed and approved, the Sub-Account transitions into a T&C Pending state.

The partner must initiate T&C acceptance by providing:

Director name (or authorized representative)

Email address for signing

The end-client signs electronically. When completed, the Sub-Account becomes Active.

Monitoring Status

The Sub-Account moves through distinct onboarding statuses. Examples may include:

Summary