Subaccounts
Subaccounts let you create Asaas accounts for partners, customers, or merchants linked to a parent account. Each subaccount can have its own financial operation, customers, charges, transfers, balance, and settings.
Before starting the integration, choose between a non-BaaS subaccount and a BaaS subaccount. Creation uses the same API, but the account holder experience, onboarding, and the parent account's responsibilities are different.
Choose the subaccount model
| Model | When to use | Account holder access | Onboarding and communication |
|---|---|---|---|
| Non-BaaS | When the account holder will use the features directly in Asaas. | The account holder accesses the Asaas website or app after setting their password. | Asaas sends the activation communication and the account holder completes the registration steps through the interface. |
| BaaS | When the financial services will be offered within your own website or app. | The customer uses the experience built by the parent account and does not need to access the Asaas dashboard. | The parent account drives the customer journey. Documents are sent through the onboarding flow designed for BaaS. |
Before you startCreating subaccounts via API is allowed for business (CNPJ) parent accounts.
New customers who start creating subaccounts via API are also subject to the regulatory evaluation period for API services.
See the Evaluation Period FAQ to understand the limits and conditions of this period.
Non-BaaS subaccounts
Use this model when the subaccount holder needs to access Asaas directly.
After creation, the account holder receives the activation communication to set their password and continue their journey in Asaas.
Follow these guides:
- Creating subaccounts — implement creation and store the returned identifiers.
- Detailed Subaccount Approval Flow — understand how the account holder completes activation and document submission.
BaaS subaccounts
Use BaaS when your platform offers financial services within its own experience, without the customer needing to manage the account through the Asaas dashboard.
The BaaS model must be aligned and enabled for your operation in advance. Creating an account via the API without this configuration does not automatically turn it into a BaaS subaccount.
If you are still defining the model, see BaaS (Banking As A Service) with Asaas.
To implement:
- Creating subaccounts with Asaas BaaS — create the subaccount according to your operation's BaaS configuration.
- Onboarding and sending documents via link — manage the submission of registration documents.
Manage existing subaccounts
After creation and approval, use the guide that matches the operation you need to perform.
| Need | Guide |
|---|---|
| Periodically confirm or update registration data | Annual Business Data Confirmation for Subaccounts |
| Change the name of a business subaccount | Change the name of a business subaccount via API |
| Manage API keys of BaaS subaccounts | Subaccount API key management |
| Close an eligible non-BaaS subaccount | Closing non-BaaS subaccounts |
Free closingNon-BaaS subaccounts closed within 48 hours of creation are not charged the creation fee, when applicable. To qualify, the subaccount must meet the criteria for closing non-BaaS subaccounts, including never having logged in. After this period, closing through this flow is no longer allowed.
Check the amounts applicable to your contract in Account Settings > Fees.
Next steps
Updated 2 days ago