Integration Model
Understand the Company, Sub-company, and Account hierarchy and determine the right structure for your integration.
Company and Account Hierarchy
Every Infinia integration is built on the following hierarchy:
Company
└── Sub-company (optional)
└── Account Owner
└── Account (one or more)
Company — Your top-level entity in Infinia. Created during onboarding. All API operations are scoped to your company or to sub-companies beneath it.
Sub-company — An optional child entity under your company. Used when you need to segregate accounts on behalf of third-party merchants or clients — typically when operating as a PSP. Each sub-company can hold its own set of accounts.
Account Owner — The verified legal entity (individual or business) that owns the accounts. Must be created before any account is opened. Stores the identity and compliance information needed to operate accounts in their name. One Account Owner can hold multiple accounts.
Account — A virtual account that holds a balance in a specific currency. Every account must be linked to an Account Owner, which must exist before the account is created.
Which model fits your use case?
Use the table below to determine whether you should operate on your own company or create sub-companies.
| Use Case | Description | Model |
|---|---|---|
| Treasury / Own Funds | You manage your own funds (e.g., internal treasury operations). | Accounts under your own company. No sub-companies needed. |
| Wallet — B2B / B2C | You offer accounts directly to businesses or consumers under your own brand. | Accounts under your own company. No sub-companies needed. |
| PSP — B2B2C / B2B2B | You are 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 + PSP) | You operate both direct accounts (B2B/B2C) and merchant accounts (B2B2C/B2B2B). | Create a sub-company with your own name for your direct accounts. Create additional sub-companies for each merchant. |
If you are unsure which model applies to your integration, discuss your use case with your account manager during onboarding. Choosing the wrong model may require restructuring later.
Account Owner requirements
An Account Owner is required for every named virtual account. There are no exceptions.
- The Account Owner represents the verified legal entity that holds the account.
- It can be an individual (natural person) or an organization (legal entity).
- It can be national (domiciled in the account's country) or foreign (domiciled outside the account's country).
- The capabilities of the account — such as which payin and payout types are permitted — depend on the Account Owner's type and nationality. See Account Capabilities for details.
For KYC integration options, refer to the Account Owners guide.
Sub-company compliance requirements
Adding a sub-company is not self-serve by default. Each new sub-company represents a new merchant or client that must be reviewed by Infinia's compliance team.
Standard flow:
- You submit the merchant's information for compliance review.
- Infinia's team approves or requests additional documentation.
- Once approved, the sub-company is created and accounts can be opened under it.
Expedited flow (for eligible partners): Depending on your compliance agreement with Infinia, you may be authorized to create sub-companies in real time, subject to:
- Operating limits applied to the sub-company from creation.
- A mandatory documentation submission within the agreed timeframe to lift those limits.
Do not create sub-companies without prior coordination with your account manager. Sub-companies created without compliance approval may be suspended, and their accounts may be restricted.
Updated 6 days ago
