Creating Asaas BaaS sub-accounts

⚠️

Important

Asaas's BaaS model (formerly "White Label"), for providing banking services to third parties (Banking As a Service) is now subject to the mandatory disclosure and identification of Asaas as the Service Provider Institution, as indicated by Joint Resolution No. 16/17. Additionally, new accounts initially integrate into the regulatory evaluation period for API Services.

With Asaas BaaS enabled your client will not need to have access to our system and will not receive any type of communication from Asaas, with you being responsible in this case for making the desired resources from our API documentation available within your integrated system, ensuring only compliance with the Borrower company rules.

The process to get started with subaccount creation in the BaaS model is summarized in the following steps:

• Request to your account manager to enable this functionality
• Creation of the Asaas subaccount with Webhooks being configured
• Submission of subaccount Documentation, through onboarding with document submission via link
• Check subaccount registration status

🚧

Attention

The BaaS format needs to be previously aligned and implemented by your account manager. Creating Asaas accounts using the methods listed below without a prior definition of the authorized format operation will result in the creation of subaccounts outside this structure.

In Sandbox, to test, simply check here in this section how to configure in the sandbox account.

Creating the subaccount with Webhooks being configured

POST /v3/accounts
Check the complete reference for this endpoint

{
    "name": "Subaccount created via API",
    "email": "[email protected]",
    "cpfCnpj": "66625514000140",
    "birthDate": "1994-05-16",
    "companyType": "MEI",
    "phone": "11 32300606",
    "mobilePhone": "11 988451155",
    "address": "Av. Rolf Wiest",
    "addressNumber": "277",
    "complement": "Room 502",
    "province": "Bom Retiro",
    "postalCode": "89223005",
    "webhooks": [
        {
            "name": "Webhook for charges",
            "url": "http://meusite.com/webhook/payments",
            "email": "[email protected]",
            "sendType": "SEQUENTIALLY",
            "interrupted": false,
            "enabled": true,
            "apiVersion": 3,
            "authToken": "5tLxsL6uoN",
            "events": ["PAYMENT_CREATED", "PAYMENT_UPDATED", "PAYMENT_CONFIRMED", "PAYMENT_RECEIVED"]
        }
    ]
}

It is extremely important that Webhooks are configured from the start in BaaS subaccounts to ensure that no account creation or update events are lost, also avoiding the need for secondary requests to configure these methods.

Details about the available events for Webhooks can be found in the Webhook integration guide.

Regulatory evaluation period - What is it?

The Regulatory evaluation period is a mandatory stage, offered by Asaas so that you have all the support to use our API following all the rules set by the Central Bank, through Joint Resolution No. 16/17. This period begins from the first subaccount creation via API.

Limits during the period:

• Maximum of 10 subaccounts from different holders.
• Maximum of R$ 2,000.00 issued in charges per subaccount.
• Duration of up to 60 calendar days from the first subaccount created.

📘

Important

• After reaching any limit (quantity, amount, or deadline), the creation of new subaccounts and additional issuance of charges, subscriptions, payment links, will be automatically blocked until the completion of the regulatory evaluation process (checklists/documentation).
• In the new regulatory scenario, at each point of contact with your end customer (own screens, receipts, onboarding, contracts), it is mandatory to display the brand, links, and responsibility texts of Asaas. Consult the Asaas compliance Playbook for details, it will be created and sent exclusively to you by our support team. Click here and check the complete operation.