BaaS (Banking as a Service) enables you to embed banking account capabilities directly into your own platform through APIs. With BaaS, you can easily register a legal entity, create virtual accounts (VA), perform internal fund transfers, and access real-time balance and transaction data, all without relying on traditional bank integrations.

Core Capabilities

Entity Onboarding: Support both individual and business onboarding.
Virtual Account Management: Create and manage multiple virtual accounts under a single entity.
Documents Management: Submit or upload additional documents for compliance review.
Webhook Notification: Receive real-time updates on account and transaction status.
Account & Transaction Queries: Retrieve account details, balances, and transaction history.
Internal Transfers: Enable seamless fund movement between linked accounts under the same master account or entity.

Supported APIs

API	Function
Create Legal Entity	Create a new legal entity for an individual or company.
Update Legal Entity	Submit and update documents for compliance review.
Get Legal Entity	Retrieve detailed information including the current status of onboarding process.
Create Virtual Account	Create a new Virtual Account (VA).
Get Business Accounts	Retrieve a list of Business Accounts under the current user.
Get Account Balance	Retrieve account balance details.
Get Account Transactions	Retrieve transaction records by range or condition.
Submit Refund Bank Account	Submit refund bank account information for a rejected deposit.
Intra-account Business Transfer	Enable fund transfers between accounts owned by the same user, including Business Account, Infinity Account, and CryptoConnect Wallet.
Different-account Business Transfer	Enable fund transfers between Business Accounts under the same Master Account, including transfers between Master and Sub-Accounts, and among Sub-Accounts.

Integration Workflow

Before starting the integration, confirm your operating model: MoR (Merchant of Record), Gateway, or Distributor Mode. Refer to the official documentation for guidance: Determine Your Integration Model.

Step 1 — Master Merchant Onboarding

The master merchant must complete account registration, submit KYC/KYB information, and activate API access. For detailed steps, please refer to Quick Start.

Step 2 — Downstream Customer Onboarding

Once the master merchant account is approved, downstream customer onboarding can begin. Before creating a banking entity via API, the accountId of the corresponding downstream customer must first be obtained.

The onboarding process varies by integration model:

MoR: Use the Register an Account API to create an end-customer and obtain the accountId.
Gateway - Business Sub-merchants: Onboard the sub-merchant and submit the required KYC/KYB information through the Dashboard, then retrieve the sub-merchant's accountId through the List All Accounts API.
Gateway - Individual Sub-merchants: Use the Register an Account API to create the sub-merchant and obtain the accountId, then submit KYC through the Submit KYC API.
Distributor: Follow the corresponding MoR or Gateway onboarding process above based on the integration model used for the downstream client.

Step 3 — Create a Legal Entity

Use the Create Legal Entity API to create a new legal entity for onboarding. The accountId obtained in Step 2 must be included in the request to associate the legal entity with the corresponding end-customer or sub-merchant. A unique entityId will be returned upon successful submission.

1. Consumer Use Program

Individual onboarding is fully automated. Once the API request is submitted successfully, the entity is created without manual review.

Body parameter: "personType": "INDIVIDUAL"
Required Fields: Personal information including identity document, proof of address, and basic profile details.
Review: KYC is processed automatically. The entity is considered approved once the webhook returns "status" = "ACTIVE".

2. Business Use Program

Business entities require manual compliance review before activation.

Body parameter: "personType": "COMPANY"
Required Fields: Company information including legal representative details, UBO information, and supporting documents.
Review: Interlace will be responsible for the review process. The entity is considered approved once the webhook returns "status" = "ACTIVE".

Step 4 — Create a Virtual Account

Use the Create Virtual Account API to create one or more virtual accounts under the approved entity.

Deposit Refund

If a deposit is rejected by Interlace during compliance review, the transaction status will change to REJECTED and a deposit.rejected Webhook event will be sent.
To initiate the refund, submit the refund bank account details and proof of account ownership through the Submit Refund Bank Account API. Interlace will review the submitted information and process the refund.
Once the refund is completed, a deposit.refund.completed Webhook event will be sent.