BaaS Asaas: frequently asked questions

Use this page to understand how to handle limits, onboarding, and BaaS subaccount access in your integration with Asaas.

In the BaaS model, the parent account centralizes the integration and operates the end customer experience through its own system or application. BaaS subaccounts follow Asaas operational rules, including limits and onboarding (the account registration and document validation process).

Before you begin

1. Confirm which account is the root account responsible for the BaaS integration.
2. Map which BaaS subaccounts need limit adjustments or onboarding completion.
3. Ensure your system or application can guide the end customer through steps that depend on them, such as document submission.

How to manage limits in BaaS Asaas?

The root account must request limit increases for BaaS subaccounts directly from the account manager. This flow is not initiated by the BaaS subaccount.

Use this process when a subaccount needs to operate above its current limit. Until the increase is approved, the subaccount remains subject to the current limits.

Recommended flow

1. Identify the BaaS subaccount that needs the limit increase.
2. Gather the request context for the account manager, such as the affected subaccount and the operational reason for the increase.
3. Submit the request through the root account's contact with the account manager.
4. Wait for the account manager's guidance on analysis, approval, and next steps.
5. Update your system or operational team according to the approved limit.

📘

The criteria, required data, and analysis timelines must be confirmed with the account manager, as they depend on the request and the subaccount's situation.

Does my customer need to send documents to Asaas?

Yes. Every Asaas account must go through the onboarding process for document submission, including BaaS subaccounts.

Document submission is part of the validation required for the account to operate in Asaas. If onboarding is not completed, the customer may be prevented from progressing through steps that depend on registration or document validation.

To guide the end customer, follow the process documented in Onboarding and document submission via link.

What to guide in your flow

• Inform the customer that document submission is a mandatory step for any Asaas account.
• Direct the customer to the onboarding flow indicated by Asaas.
• Monitor the completion of the process before considering the subaccount ready to operate.
• Review invalid or pending documents according to the instructions presented in the onboarding flow.

Can a BaaS subaccount access Asaas?

A BaaS subaccount does not need direct access to Asaas. Operations must take place through the system or application developed by the parent account.

This model allows the parent account to control the end customer experience and centralize the integration with Asaas. In practice, your system should display the necessary actions for the customer, while the root account manages the operational points that depend on Asaas, such as requests to the account manager.

Responsibilities in the BaaS flow

Implementation considerations

• Do not rely on direct subaccount access to Asaas to complete the end customer journey.
• Include messages in your system to explain when the customer needs to complete onboarding.
• Handle pending states — such as documents not yet submitted or a limit request under review — before unlocking operational steps in your product.
• Keep the team responsible for the root account aligned with the account manager for requests that are not completed directly through the API.