Asaas Split on Pluga

Create charges with Split in Asaas through a Pluga automation, without building your own integration.

The source tool can be Google Sheets or another system compatible with the chosen automation template.

Before you begin

Have:

• an active Asaas account;
• a Pluga account;
• a source tool for the charge data;
• access to the Asaas account that will create the charges;
• the recipients and the split rule defined;
• the recipients' walletIds, when used in the template.

Split can use a fixed amount or a percentage. The percentage is calculated on the net value of the charge (netValue).

If you need to retrieve an account's identifier, see Retrieve WalletId.

How it works

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Prepare the data"] --> B["Configure the trigger"]
    B --> C["Connect Asaas"]
    C --> D["Map the charge"]
    D --> E["Configure the Split"]
    E --> F["Finish the automation"]
    F --> G["Create test charge"]
    G --> H["Validate the transfers"]

    classDef inicio fill:#DBEAFE,stroke:#2563EB,color:#1E3A8A,stroke-width:3px
    classDef validacao fill:#E0F2FE,stroke:#0284C7,color:#0C4A6E,stroke-width:2px
    classDef sucesso fill:#DCFCE7,stroke:#16A34A,color:#14532D,stroke-width:3px

    class A inicio
    class B,C,D,E,F,G validacao
    class H sucesso

    linkStyle default stroke:#94A3B8,stroke-width:2px

1. Prepare the data

Organize the information needed to create the charge and configure the Split.

When using a spreadsheet as the source, put each piece of information in its own column.

2. Configure the trigger

In the Pluga dashboard:

1. create a new automation;
2. choose the source tool, such as Google Sheets;
3. select the spreadsheet or resource that contains the data;
4. choose the template that creates a charge in Asaas;
5. define when the automation should run.

Configure the trigger to fire only after all the required data has been filled in.

For example, a control column can start the creation of the charge only when it receives a specific value, such as Yes.

3. Connect Asaas

Select Asaas as the destination tool and choose the charge creation action.

Connect the account following the authentication flow presented by Pluga.

4. Map the charge

Associate the data from the source tool with the fields used by the Pluga template.

Review in particular:

• customer;
• amount;
• due date;
• payment method;
• description;
• sale reference, when used.

The available fields depend on the selected automation.

5. Configure the Split

Enable Payment Split in the charge configuration.

Choose how to identify the recipients according to the options available in the template:

• already registered subaccounts; or
• walletId.

Then define the transfer by:

• fixed amount;
• percentage.

Fixed amount

Defines an exact amount for the recipient.

Example:

Net value of the charge: R$ 100.00
Fixed split for partner: R$ 25.00
Amount transferred to partner: R$ 25.00
Remaining balance for the issuing account: R$ 75.00

Percentage

The percentage is applied to the netValue.

Example:

Net value of the charge: R$ 100.00
Split for partner: 30%
Amount transferred to partner: R$ 30.00
Remaining balance for the issuing account: R$ 70.00

For percentage-only Splits, the sum cannot exceed 100%. The configured values must also respect the net value available in the charge.

See the complete rules in Payment Split.

6. Define the recipients

Confirm that each walletId belongs to the account that should receive the transfer.

You only need to configure as recipients the accounts that will receive part of the amount. The remaining net balance stays in the account that created the charge.

7. Finish and test

Before activating the automation:

1. review the mapped fields;
2. check the recipients;
3. validate the amounts or percentages;
4. confirm the trigger;
5. run a test with controlled data.

Then finish the automation in Pluga.

Expected result

Pluga should create the charge in Asaas with the Split configuration defined in the automation.

After the charge is received, Asaas calculates the netValue and processes the transfers according to the configured rules.

Avoid duplicates

If the source allows it, keep control fields to record the result of the automation.

For example:

Before reprocessing a row or event:

• check the automation history in Pluga;
• confirm whether the charge has already been created;
• use the order ID or external reference for reconciliation.

Track the Splits

For manual validation, check the paid and received Splits directly in the Asaas interface:

Check Splits through the interface.

For automated tracking, use Webhooks instead of recurring API queries.

The event:

PAYMENT_SPLIT_DONE

is sent when a specific Split is settled. If a charge has more than one Split, each settlement may generate its own event.

See the Events for payments.

Refunds

When a charge with Split is refunded, the related transfers are also refunded.

Take this behavior into account when reconciling the issuing account, the recipients, and the source tool.

Common errors

Next steps

• Learn the Payment Split rules
• Check paid and received Splits
• Retrieve an account's walletId
• See the payment events
• See the Pluga FAQ