Create a split configuration profile for all payments processed through your user's store.
You can create a split configuration profile to automatically evaluate and split transactions processed through your user's store. The rules you set in the profile define how and/or to which balance account to book the following:
The payment amount and all types of transaction fees associated with the payment
Your platform's commission and additional commission to your user's balance account
The refund amount and associated fees
The chargeback amount and associated fees
The leftover amount after currency conversion
Surcharges
Gratuity (tips)
You can associate the split configuration profile you create with one of your user's balance accounts when you link the profile to a store. All amounts and fees that you want to book to your user are booked to the same balance account. The split instructions that you don't include in the profile or API request are booked to your platform's liable balance account by default.
If you want to create and manage split configuration profiles through API calls, your Management API credential must have the Management API - SplitConfiguration read and writerole.
If you want to create and manage split configuration profiles in your Customer Area, ask our Support Team to enable the Manage new split configuration settings role for your admin user. The admin user can afterwards grant this role to other users.
Step 1: Create a split configuration profile
You can create a split configuration profile in your Customer Area, or by using the Management API. When you create the profile, you must create its first rule at the same time.
Set the payment conditions for the split configuration profile.
The split logic defined in the rule will apply to all payments that meet all of the conditions set in this step.
Shopper interaction: Apply the split logic to transactions made through a specific sales channel, or all channels.
Payment method: Apply the split logic to transactions made through a specific payment method, or all payment methods associated with the store.
Currency: Apply the split logic to transactions made in a specific currency, or any currency.
Funding source: Apply the split logic to payments initiated by credit cards, debit cards, or both.
Select Next: Split logic.
Configure the split logic to apply to all transactions that meet the previously defined conditions. These split items can be booked either to your liable balance account or your user's balance account.
Commission: Define how to book your platform's commission fee for payments. It can be a fixed amount, a percentage of the payment, or both.
Payment fee: Select the balance account to which you want to book the transaction fees incurred by the transaction.
Chargeback: Select the balance account to which you want to book a potential chargeback. It can be your liable balance account, your user's balance account, or you can split the chargeback amount between balance accounts, according to the split ratio of the original payment.
Tip: Select the balance account to which you want to book potential gratuities.
Surcharge: Select the balance account to which you want to book the surcharges.
(Optional) Configure an additional commission.
You can define an additional fee as a commission for your user. This can be a fixed amount (specified in minor units), a percentage (specified in basis points), or both. The specified amount and/or percentage is booked directly to your user's balance account.
Select Create profile.
The new configuration profile will have a UUID next to its description in the Split configuration profiles list. Take note of this, because you'll need use it later to apply the profile to your user's store.
After a split configuration profile is created, you can add multiple rules to it.
To create a split configuration profile, make a POST /merchants/{merchantId}/splitConfigurations request, specifying your merchantId in the path. In the body of the request, send the description field and rules array.
In the rules array, include the following parameters for each rule:
Define an additional fee as a commission for your user, booked directly to your user's balance account. This can be a fixed amount, a percentage, or both.
Based on which optional parameters you include in the splitLogic object, you can define to which balance account to book:
The different types of transaction fees associated with the payment.
Potential refunds, chargebacks, and their associated fees.
The amount left over after currency conversion for online payments.
The tips and surcharges for in-person payments.
You can define any or all of these parameters in the splitLogic object of the split configuration profile.
Transaction fees
To book the transaction fees associated with the payment to different balance accounts, you must include at least one the following parameters in the splitLogic object:
Define to which balance account to book the Scheme fees associated with the payment.
For example, to create a split configuration profile that books the Interchange and Scheme fees to the user's balance account, and every other fee to your platform's liable balance account, send the following request:
ruleId: the unique identifier of the split configuration rule.
splitLogicId: the unique identifier of the split instructions that are applied when the predefined conditions are met.
You will need these IDs when you want to change the details of the split configuration profile.
Refunds and chargebacks
To define the split instructions for potential refunds, chargebacks, and the fees incurred by them, you can include the following parameters in the splitLogic object.
Define the refund logic. You can book the entire refund amount to your platform's liable balance account, your user's balance account, or split the refund amount between the balance accounts specified in the original payment (with the same split ratio).
Define the chargeback logic. You can book the entire disputed amount to your platform's liable balance account, your user's balance account, or split the disputed amount between the balance accounts specified in the original payment (with the same split ratio).
ruleId: The unique identifier of the split configuration rule.
splitLogicId: The unique identifier of the split instructions that are applied when the predefined conditions are met.
You will need these IDs when you want to change the details of the split configuration profile.
Example: Create a split configuration profile
In the following example, we create a split configuration profile with a catch-all rule that splits all payments processed through the store automatically:
All transaction fees and chargeback amounts and fees are deducted from your liable balance account.
The refund amount is deducted according to the original payment's split ratio (divided between your liable balance account and your user's balance account).
The fees associated with the refund are booked to your user's balance account.
Tips and the remainder amount (left over after currency conversion) are booked to your user's balance account.
Your platform's commission (in the default currency) is set at EUR 0.10 + 1%, booked to your liable balance account.
An additional commission is set at EUR 0.05 + 0.5%, booked to your user's balance account.
ruleId: The unique identifier of the split configuration rule.
splitLogicId: The unique identifier of the split logic that is applied when the conditions of the rule are met.
You will need these IDs when you want to change the details of the split configuration profile.
Step 2: Link the profile to a store
You must link the split configuration profile to user's store using the Management API. You have two options:
Create a new store with the split configuration profile by making a POST /stores request. Use this option when your user does not have an existing store.
Update an existing store with the split configuration profile, by making a PATCH /stores/{storeId} request. Use this option if you have already created a store for your user and want to apply a split configuration profile to this store.
In the body of either request, include the splitConfiguration object with the following parameters:
balanceAccountId: the unique identifier of the balance account to which the split amounts and fees must be booked, depending on the defined splitLogic.
The following example shows how you can apply a split configuration profile to all payments processed through an existing store.
The response contains the full store details, including the split configuration profile information.
After the store is successfully updated, Adyen starts evaluating every transaction processed through the store and applies the split instructions of the rule with the highest priority condition.
