API Reference
FAQSandbox Portal

Create a sub-account (New)

post
https://api-company-sandbox.vertofx.com/sub-accounts

Create a sub-account for a downstream company, validate required fields like subCategory against Verto's supported industry classifications, and prepare the customer for onboarding and later scoped operations.

Use this endpoint to create a sub-account for a downstream business under your parent account.

NOTE:
Confirm your Base URL: If you are testing in the sandbox environment, ensure your base URL is set to the sandbox base url: https://api-company-sandbox.vertofx.com, and if in production, use the production base URL: https://api-company-beta.vertofx.com

Before you call this endpoint Complete these steps first:

  1. Confirm your parent account is enabled for sub-account creation. Collect the business name, registration country, registration number, and supported industry classification.
  2. Make sure the subCategory value exactly matches a supported industry string.

Store the returned sub-account ID because you will need it for onboarding, wallets, and other downstream actions.

Valid subCategory values: The subCategory field uses Verto's Supported Industry list . Refer to it for mapping

The subCategory value must exactly match one of Verto's supported industry classifications. If it does not, the API will return an invalid-input error.

Classifications Implementation notes

  • Validate subCategory in your own application before you send the request. Keep the exact casing and spelling from the supported industry classifications list.
  • If your team maps internal merchant categories to Verto onboarding categories, normalize that mapping before request submission.


    Common validation issue
    If you receive an error similar to Invalid input. Please provide a valid company sub-category, check that:
    1. the submitted subCategory is present in the supported industry classifications list
    2. the value has not been reformatted or abbreviated in your application
    3. your request is using the expected industry string rather than an internal enum label

Type of Account

  • For Atlas for Fintech Use Cases - pass accountType = SUB_CLIENT
  • For Atlas for Platform Use Cases - pass accountType = PARTNER_REFERRED

For more info on the difference between SUB_CLIENT and PARTNER_REFERRED account types , please refer to this guide.

Body Params
string
required

The registered legal name of the company, with the respective government authority.

string | null
enum
required

The country where the sub-account is registered.

string
required

The company's industry classification.

string
required

Indicates official identification number related to this account.

string

The tax registration number of the company with the respective government tax authority.

string

The company identification number in the client's system.

string
enum
required

Indicates the type of account. The possible enum values are:

  • PARTNER_REFERRED: Not supported at this time.
  • SUB_CLIENT: The client of a the partner regulated financial institution.
  • RELATED_ENTITY: Not supported at this time.
Allowed:
Responses

Updated 3 days ago

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 3 days ago

Privacy policy Terms of service

VertoFX Ltd (No. 10973066) designs and operates the VertoFX website and app. VertoFX is authorised by the Financial Conduct Authority under the Electronic Money Regulations 2011, Firm Reference 901073, for the issuing of electronic money. Database rights protect data on VertoFX website(s) (including pricing data).

Please Note: we do NOT and WILL not deal with unregulated exchanges or affiliates as this currently falls outside of our risk appetite.

© Verto 2026

All rights reserved Registered Office: 20-22 Wenlock Road, London, England, N1 7GU