Understand Asaas BaaS

Asaas BaaS lets you offer financial services to your customers directly through your website or app.

Through the API, you can create subaccounts so that each customer has an individual account, carries out financial operations, and manages their own payments.

When to use it

Use BaaS when you want to provide financial services within your own platform's experience.

In this model:

• subaccounts are created through the API;
• each customer has an individual account;
• operations are carried out through your website or app;
• the integrator develops the screens and management flows;
• the customer does not need to access the Asaas dashboard.

Available features

With BaaS, your platform can offer features such as:

• charges via Pix, bank slip (boleto), and card;
• payment booklets and subscriptions;
• payment links;
• receivables anticipation;
• invoice issuance;
• bill payment;
• anti-fraud protection;
• other services available through the API.

Feature availability may vary according to the operation's configuration.

Standard subaccount and BaaS

In BaaS, the integrator is responsible for developing the screens, controls, and journeys used by their customers.

The account's communication and experience must follow the model defined during the operation's implementation.

Before implementing

The BaaS model is subject to the rules for disclosing and identifying Asaas as the service provider institution, as set forth in Joint Resolution No. 16/17.

New accounts may also go through an initial regulatory evaluation period before using the services through the API.

To test account creation in Sandbox, see How to set up your account in the Sandbox.

Next steps

• Set up BaaS in the Sandbox
• Create a subaccount
• Check the API reference