Using split without API

Choose a no-code integration to configure Asaas payment split through a plugin or connector.

Use Split without developing your own integration

Split is processed by the Asaas API, but you can configure it through plugins and automation platforms without developing your own integration.

Choose the option according to the system used in your operation.

Choose the integration

ScenarioOption
Your store uses WooCommerceSplit in WooCommerce
You want to create automations between Asaas, spreadsheets and other systemsSplit in Pluga
You use Make scenarios and modulesMake/Integromat
You need direct control over payloads and business rulesPayment Split via API

Before you start

Regardless of the tool chosen:

  • recipients must have Asaas accounts;
  • define which accounts will receive part of the amount;
  • define the split rule allowed by the integration used;
  • configure the split before creating the charge that should have a Split.

Depending on the tool, the recipient may be provided by walletId or selected from the available subaccounts.

📘

Important

Using a plugin or automation platform does not change the Payment Split rules.

Calculation rules, net amount, recipients and other behaviors still follow the Asaas definitions.

See the Payment Split rules.

WooCommerce

Use this option when charges are created by the Asaas Plugin for WooCommerce.

The Split configuration is done in the WooCommerce dashboard and applied to the charges created by the plugin according to the configured rule.

Configure Split in WooCommerce.

Pluga

Use Pluga when you want to create charges with Split from automations connected to spreadsheets or other systems.

The automation can work with registered subaccounts or walletId, depending on the configured flow.

Configure Split in Pluga.

Make

Make lets you create scenarios that execute operations in Asaas, including charges with Split.

Depending on the flow, you can use modules available in the integration or calls to the Asaas API.

See the Make integration.

When to use the API directly

Prefer your own integration when you need:

  • custom rules to define recipients or amounts;
  • direct control over the creation and update of charges;
  • Split features not available in the chosen tool;
  • your own handling of validations, errors and reconciliation.

In this case, follow the guide for the corresponding charge type:

Validate the configuration

After configuring the integration, create a test charge and confirm:

  1. whether the Split was applied to the charge;
  2. whether the recipients are correct;
  3. whether the amounts match the configured rule.

You can track paid and received Splits in the Asaas application.

View Splits through the interface.

Next steps


Did this page help you?