Introduction

Currently, Asaas has two types of subaccounts:

• Standard Subaccounts (non-White Label)
• White Label Subaccounts

Both types of subaccounts are created through the same endpoint:

POST /api/v3/accounts
See the complete reference for this endpoint

However, the activation and document submission process differs between them. This document describes the detailed account approval flow for both formats, including the submission of mandatory documents and the correct use of the endpoints.

Approval Flow – Standard Subaccount

Summary: Standard (non-White Label) subaccounts have access to the Asaas interface. After the account is created, the account holder receives an email to reset their password and proceeds with document submission directly through the interface.

Flow:
Create the Subaccount
→ Endpoint: POST /accounts
→ The account is created and validated with the Federal Revenue Service.

Email Reception
→ The account holder automatically receives an email to reset their password and access the Asaas dashboard.

Password Reset
→ The account holder resets their password and logs into the Asaas interface.

Document Submission
→ Mandatory documents are submitted directly through the Asaas interface.
→ Usually required:

• Selfie photo
• Photo of the Identification Document

Review and Approval
→ The Asaas compliance team reviews the submitted documents.
→ Account approved.

Approval Flow – White Label Subaccount

Summary: White Label subaccounts do not have access to the Asaas interface. The entire document submission process is carried out via API or through an external link (onboardingUrl), depending on the document type.

Flow:
Create the Subaccount
→ Endpoint: POST /accounts
→ The account is created and validation with the Federal Revenue Service begins.

Wait 15 Seconds
→ Important: wait at least 15 seconds after account creation before checking for documents.
→ Reason: to ensure that validation and data retrieval from the Federal Revenue Service have been completed.
→ If this waiting time is not respected, the response may incorrectly indicate that non-mandatory documents should be submitted.

Check Pending Documents
→ Endpoint: GET /myAccount/documents
→ Checks which documents need to be submitted.
See the complete reference for this endpoint

Analyze Response
→ By default, for Individuals and Legal Entities (except Associations):

• Selfie photo
• Photo of the Identification Document

→ For Associations:

• In addition to the above documents, Minutes of Election.

Check onboardingUrl Attribute
→ If present in the document object:
✅ Document must be submitted via the external link (onboardingUrl).
❌ Submission via API (POST) will not be accepted.

→ If not present:
✅ Document must be submitted via API:
→ Endpoint: POST /myAccount/documents/{id}
See the complete reference for this endpoint

Document Submission

• With onboardingUrl: external link, white-label experience without Asaas branding.
• Without onboardingUrl: submission via API.

Review and Approval
→ The Asaas compliance team reviews the submitted documents.
→ Account approved.

🚧

Important

The onboardingUrl attribute strictly determines the document submission method.
Never attempt to send via API a document that has an onboardingUrl.
→ The submission will be rejected.

In White Label subaccounts, the onboardingUrl is a link with no Asaas branding, ensuring the full white-label experience.

❗

Attention:

Always respect the minimum 15-second timeout after creating the account before checking for pending documents.

This flow ensures that the activation and document submission process is carried out correctly and appropriately for the subaccount type (Standard or White Label), avoiding common errors and ensuring regulatory compliance.