Integration Model

Every Infinia integration is built on the same hierarchy: your company, optional sub-companies, the account owners, and their accounts. The structure you choose decides where accounts live and how they're reviewed by compliance.

This page explains each level of the hierarchy, helps you choose a model for your use case, and describes how sub-companies are approved.

Company and account hierarchy

Company
└── Sub-company (optional)
    └── Account Owner
        └── Account (one or more)

Level	Description
Company	Your top-level entity in Infinia, created during onboarding. Every API operation is scoped to your company or to a sub-company beneath it.
Sub-company	An optional child entity under your company. Use it to segregate accounts held on behalf of third-party merchants or clients, typically when you operate as a PSP. Each sub-company holds its own set of accounts.
Account owner	The verified individual or business that owns the accounts. It stores the identity and compliance information needed to operate accounts in its name. You create it before opening any account, and one account owner can hold several accounts.
Account	A virtual account that holds a balance in one currency. Every named account is linked to an account owner, which must exist before the account is created.

To act on behalf of a sub-company, send its company ID in the X-Company-Id header with your own credentials. See Authentication.

Choose a model

Whether you operate on your own company or create sub-companies depends on whose funds the accounts hold.

Use case	Description	Model
Treasury or own funds	You manage your own funds, for example for internal treasury operations.	Accounts under your own company. No sub-companies needed.
Wallet (B2B or B2C)	You offer accounts directly to businesses or consumers under your own brand.	Accounts under your own company. No sub-companies needed.
PSP (B2B2C or B2B2B)	You're a payment service provider onboarding merchants who in turn serve their own clients.	One sub-company per merchant. Accounts live under each sub-company.
Mixed (wallet and PSP)	You operate both direct accounts (B2B or B2C) and merchant accounts (B2B2C or B2B2B).	A sub-company in your own name for your direct accounts, and one more sub-company per merchant.

📘
If you're unsure which model fits your integration, discuss your use case with your account manager during onboarding. Choosing the wrong model can require restructuring later.

Account owner requirements

Every named virtual account needs an account owner. There are no exceptions.

Legal entity. The account owner represents the verified legal entity that holds the account.
Type. It can be an individual (a natural person) or an organization (a legal entity).
Nationality. It's national when it's domiciled in the account's country, and foreign when it's domiciled outside it.
Capabilities. The account owner's type and nationality decide the account's capabilities, such as which payin and payout types it can make. See Account Capabilities.

For the KYC integration options, see Account Owners.

Sub-company approval

Adding a sub-company isn't self-serve by default. Each new sub-company represents a new merchant or client, and Infinia's compliance team must review it.

Standard flow

You submit the merchant's information for compliance review.
Infinia's compliance team approves it or requests additional documentation.
Once it's approved, the sub-company is created and you can open accounts under it.

Expedited flow

Depending on your compliance agreement with Infinia, you may be authorized to create sub-companies in real time with Create Subcompany, subject to:

Operating limits applied to the sub-company from creation.
A mandatory documentation submission within the agreed timeframe, which lifts those limits.

⚠️
Don't create sub-companies without coordinating with your account manager first. Sub-companies created without compliance approval can be suspended, and their accounts restricted.