Introduction - Escrow Account

The Escrow Account is an Asaas feature that allows funds received by a subaccount to be temporarily held until specific release conditions are met.

During the retention period, the funds remain blocked and are not available in the subaccount balance. Once released, either automatically or through an action performed by the platform, the funds become part of the available balance.

This model is used to provide an additional layer of security for transactions in which the payment must remain on hold until a service is completed, a product is delivered, or another business condition is fulfilled.

When to use

The Escrow Account is recommended for platforms that need to control when received funds become available to their users.

Common scenarios include:

• marketplaces that want to release funds only after delivery has been confirmed;
• service platforms that wait until a service has been completed before releasing the payment;
• operations that require a guarantee period before funds become available;
• White Label solutions that need to control the financial flow between the platform and its subaccounts.

In all of these cases, the funds remain blocked for the period configured for the subaccount.

How it works

A typical Escrow Account flow follows the steps below:

Enable the Escrow Account for the subaccount
↓
Receive payments normally
↓
Received funds remain blocked
↓
Monitor the guarantee status
↓
Release automatically upon expiration
or perform a manual release
↓
Funds become available in the subaccount balance

Each of these steps has its own specific rules, detailed in the pages of this section.

Prerequisites

Before using the Escrow Account through the API, make sure that:

• the feature is available for your account;
• the subaccounts have been properly created on the platform;
• the Escrow Account has been enabled individually for each subaccount that will use the feature.

Until the feature is enabled for a subaccount, received funds will continue to be made available normally, without retention.

Important rules

Before implementing your integration, consider the following business rules:

• only payments received after the Escrow Account has been enabled are submitted to the retention flow;
• the retention period is configured individually for each subaccount;
• funds can be released automatically or manually;
• when the Escrow Account is disabled for a subaccount, all funds still under guarantee will be released;
• while funds are in the process of being released, the feature cannot be re-enabled for that subaccount.

These behaviors directly impact the financial flow of the integration and should be taken into account during implementation.

Operational impact

When a payment is received by a subaccount with the Escrow Account enabled, the funds are not immediately added to the available balance.

During the retention period:

• the funds remain blocked;
• the guarantee can be queried through the API;
• the platform's financial reconciliation should consider that the payment has been received, but the funds are not yet available for use.

Only after the guarantee is released do the funds become part of the subaccount's available balance.

Feature pricing

The Escrow Account is subject to recurring billing.

The cost consists of:

• a R$ 99.90 monthly fee for the main account;
• an additional R$ 9.90 for each subaccount with the feature enabled.

The fee is charged automatically through a debit from your Asaas account.

If desired, the platform can configure the monthly fee for subaccounts to be charged directly to them.

For up-to-date pricing information and commercial conditions, refer to the Asaas pricing page or contact your account manager.

Next steps

After understanding how the Escrow Account works, the recommended next topics are:

• Configuring the Escrow Account for subaccounts;
• Monthly fee charged per configured subaccount;
• Funds under Escrow Account guarantee;
• Releasing funds under guarantee;
• Disabling the Escrow Account.