Payment splitting in WooCommerce
Payment Split allows you to automatically divide the amount received in a sale among different Asaas wallets.
When this functionality is configured, every charge created by the Asaas Plugin will follow the defined split rule, without the need to perform individual configurations for each order.
When to use
Use Payment Split when your operation involves the automatic sharing of received amounts, for example:
- marketplaces;
- franchises;
- commercial partners;
- seller commissioning;
- operations with revenue sharing.
How it works
After purchase confirmation:
- the customer makes the payment normally through the WooCommerce checkout;
- the Asaas Plugin creates the charge in Asaas;
- Asaas automatically applies the configured Split rule;
- each wallet receives its respective share of the amount according to the configuration performed.
This process happens automatically during charge creation.
Configuring Split
The configuration can be performed in the options of each payment method made available by the Asaas Plugin.
Simply access:
WooCommerce > Settings > Payments
Then, select one of the Asaas payment methods and locate the Split section.
In this area, it is possible to define how the charge amounts will be distributed among the participating wallets.
Global configurationAlthough the Split option is available in the payment method settings, the applied rule is global.
This means that all charges created by the Plugin will use the defined configuration.
Important rules
Before enabling Payment Split, consider the following rules:
- Split is automatically applied when the charge is created;
- the configuration applies to all new charges generated by the Plugin;
- changes to the configuration affect only charges created after the change;
- existing charges are not changed.
Operational impact
After enabling Split:
- the amounts are automatically distributed among the configured wallets;
- it is not necessary to perform manual divisions after payment;
- every sale made using the Asaas Plugin will follow this configuration.
For this reason, it is important to carefully validate the configuration before making the store available in production.
AttentionSince the configuration is automatically applied to all new charges, an incorrect configuration may impact the entire financial operation of the store.
Always perform tests in the Sandbox environment before using Split in production.
Best practices
Recommendations
- validate the configuration in Sandbox before publishing the store;
- confirm whether all participating wallets are correctly configured;
- review the distribution of amounts after the first sales;
- whenever changing the configuration, perform a new test purchase;
- monitor the first settlements to ensure that the split occurred as expected.
Related content
Continue the configurationSee also:
- Initial settings
- Payment methods
- Charge methods
- Subscriptions in WooCommerce
- Webhooks
- Common errors
