---
title: "Split payments automatically"
description: "Split payments automatically when processing through stores."
url: "https://docs.adyen.com/platforms/automatic-split-configuration"
source_url: "https://docs.adyen.com/platforms/automatic-split-configuration.md"
canonical: "https://docs.adyen.com/platforms/automatic-split-configuration"
last_modified: "2026-06-01T15:33:15+02:00"
language: "en"
---

# Split payments automatically

Split payments automatically when processing through stores.

[View source](/platforms/automatic-split-configuration.md)

If you process your users' transactions through [stores](/platforms/onboard-users/onboarding-steps), you can configure the store to automatically apply your billing logic. For example, you can deduct your platform's commission and the transaction fees, or choose how to book potential chargebacks. By configuring your stores to apply billing logic automatically, you eliminate the need to send split instructions for every transaction, capture, refund, or chargeback.

For Adyen to automatically apply the split instructions, you need to:

1. [Create a split configuration profile](/platforms/automatic-split-configuration/create-split-configuration#create-split-configuration) that contains the conditions that determine whether to split a payment, and the instructions on how to split the payment (split logic).\
   You can create and manage your split configuration profiles and rules in your [Customer Area](https://ca-test.adyen.com/), or using the [Management API](https://docs.adyen.com/api-explorer/Management/latest/overview).
2. [Link the profile to your user's store](/platforms/automatic-split-configuration/create-split-configuration#link-profile-to-store) when you create or update the store.

By default, all transaction amounts and fees are booked to your platform's liable balance account, which can make reconciliation harder for your platform and users. We recommend that you either create split configuration profiles, or send the split instructions with every payment-related request. You can also override a profile, when necessary, by specifying split instructions in your individual payment requests.

## Split configuration profiles

A split configuration profile contains at least one **rule**. A rule consists of conditions and instructions on how to split transactions. If a transaction meets all conditions of the rule, we book the funds and fees to the balance account that you specify when you link the profile to a store.

If a profile contains multiple rules that apply to the transaction, we use the split instructions from the rule that is the highest in the [rule hierarchy](#rule-hierarchy).

### Conditions

The conditions define *if* a transaction is split according to the split instructions. If a transaction meets **all** the conditions of the rule, then the split instructions are applied.

| Condition           | Required                                                                                                      | Description                                                                                                                                                                                                                                                                                                                                                                              |
| ------------------- | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Currency            | ![Required](/user/pages/reuse/image-library/01.icons/required/required.svg?decoding=auto\&fetchpriority=auto) | Defines whether the rule applies to a specific currency, or all currencies.                                                                                                                                                                                                                                                                                                              |
| Payment method      | ![Required](/user/pages/reuse/image-library/01.icons/required/required.svg?decoding=auto\&fetchpriority=auto) | Defines whether the rule applies to a specific payment method, or all payment methods associated with the store. You can define different rules for [payment method variants](/development-resources/paymentmethodvariant/) as well.                                                                                                                                                     |
| Card region         |                                                                                                               | Defines whether the rule applies to transactions processed through a store that's registered in the same country/region where the card was issued, in a different country/region, or all transactions regardless of the processing and issuing location. List of regions:- US
- Canada
- Europe
- APAC
- LATAMThis condition is in pilot phase, and not yet available for all platforms. |
| Funding source      | ![Required](/user/pages/reuse/image-library/01.icons/required/required.svg?decoding=auto\&fetchpriority=auto) | Defines whether the rule applies to a specific type of card, or all card types.                                                                                                                                                                                                                                                                                                          |
| Shopper interaction | ![Required](/user/pages/reuse/image-library/01.icons/required/required.svg?decoding=auto\&fetchpriority=auto) | Defines whether the rule applies to a specific sales channel, or all channels.                                                                                                                                                                                                                                                                                                           |

### Split logic

The split logic is a set of instructions that determine *how* we split a transaction: the amounts we book to your liable balance account and to your user's balance account, and how they appear in the webhooks and reports.

| Split instruction          | Required                                                                                                      | Description                                                                                                                                                                                                                                                                                                                                                                                  |
| -------------------------- | ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Commission                 | ![Required](/user/pages/reuse/image-library/01.icons/required/required.svg?decoding=auto\&fetchpriority=auto) | Defines the amount to book to your liable balance account as your platform's [commission](#commission) on the transaction. It can be a fixed amount (specified in minor units), a percentage (specified in basis points), or both.                                                                                                                                                           |
| Transaction fees           | ![Required](/user/pages/reuse/image-library/01.icons/required/required.svg?decoding=auto\&fetchpriority=auto) | Defines where to book the [transaction fees](/platforms/online-payments/transaction-fees). We can book the fees either to your liable balance account or your user's balance account, together or separately.                                                                                                                                                                                |
| Additional commission      |                                                                                                               | Defines whether we book an additional commission to your user's balance account.                                                                                                                                                                                                                                                                                                             |
| Refund                     |                                                                                                               | Defines where to book the refund amount.                                                                                                                                                                                                                                                                                                                                                     |
| Refund cost allocation     |                                                                                                               | Defines where to book the fees associated with refunds.                                                                                                                                                                                                                                                                                                                                      |
| Chargeback                 |                                                                                                               | Defines where to book the chargeback amount.                                                                                                                                                                                                                                                                                                                                                 |
| Chargeback cost allocation |                                                                                                               | Defines where to book the fees associated with chargebacks.                                                                                                                                                                                                                                                                                                                                  |
| Remainder                  |                                                                                                               | Defines where to book the leftover amount (after currency conversion).                                                                                                                                                                                                                                                                                                                       |
| Surcharge                  |                                                                                                               | Defines where to book surcharges.                                                                                                                                                                                                                                                                                                                                                            |
| Tip                        |                                                                                                               | Defines where to book tips.                                                                                                                                                                                                                                                                                                                                                                  |
| DCC Markup                 |                                                                                                               | Only for in-person payments. Defines how to book the [markup paid by the customer for Dynamic Currency Conversion](/platforms/in-person-payments/dynamic-currency-conversion/#dcc-markup), after deducting Adyen's share. You can determine how to split the markup amount between your platform and your user. This split logic is in pilot phase, and not yet available for all platforms. |

When a transaction meets **all** conditions of the rule, Adyen applies the corresponding split logic.

We recommend that you always include a catch-all rule (set all conditions to **ANY**) in your profile. Without one, any transaction that doesn't match a specific rule will be booked to your liable balance account by default.

Adyen evaluates all transactions processed through the store, based on the rules in the store's split configuration profile. In case you need to split a specific transaction differently, you can send transaction-specific split instructions in the payment, capture, or refund request. Any split instruction that you send in a request overrides the automatic split.

## Rule hierarchy

If a split configuration profile has multiple rules, and more than one rule applies to the transaction, Adyen determines which rule to apply based on priority and granularity.

The priority of rules is:

1. Currency
2. Payment method or [payment method variant](/development-resources/paymentmethodvariant/), like **visa** or **visasignature**
3. Card region
4. Funding source
5. Shopper interaction

The granularity of a rule refers to how specific the rule is, for example:

* Whether the rule is for one currency in particular or for any currency.
* Whether the rule is for Visa payments with a payment method variant of **visasignature**, or for Visa payments in general with a payment method variant of **visa**.

Within each priority, a rule that is more granular (more specific) takes precedence over a general rule.

### Examples

Here are some example scenarios based on the following split rules:

| Rule | Currency | Payment method | Card region   | Funding source | Shopper interaction | Commission    |
| ---- | -------- | -------------- | ------------- | -------------- | ------------------- | ------------- |
| 1    | USD      | Any            | Any           | Any            | Any                 | USD 3.00 + 1% |
| 2    | Any      | visasignature  | International | Any            | Ecommerce           | USD 2.50 + 1% |
| 3    | USD      | visa           | Domestic      | Any            | Any                 | USD 2.00 + 1% |
| 4    | CAD      | mc             | Any           | Any            | POS                 | USD 1.40 + 1% |
| 5    | USD      | Any            | Any           | credit         | Any                 | USD 1.50 + 1% |

**Scenario 1: In-person payment in USD using American Express credit card issued in the US**

* Rule 4 doesn't apply, because the currency (**CAD**) is different.
* Rule 3 doesn't apply, because the payment method (**visa**) is different.
* Rule 2 doesn't apply, because the payment method (**visasignature**) and shopper interaction (**Ecommerce**) are different.
* Out of the rules that do apply, rule 5 has a higher priority than rule 1 because of the funding source (**credit**).

Adyen applies **rule 5** to split the transaction, and sends USD 1.50 + 1% to your liable balance account.

**Scenario 2: Ecommerce payment in USD using a Visa debit card issued in the US**

* Rule 4 doesn't apply, because the currency (**CAD**), payment method (**mc**), and shopper interaction (**POS**) are different.
* Rule 2 doesn't apply, because the payment method (**visasignature**) and the card region (**international**) are different.
* Rule 5 doesn't apply, because the funding source (**credit**) is different.
* Out of the rules that do apply, rule 3 has a higher priority than rule 1 because of the payment method (**visa**).

Adyen applies **rule 3** to split the transaction, and sends USD 2.00 + 1% to your liable balance account.

**Scenario 3: Ecommerce payment in USD using Mastercard credit card issued in the US**

* Rule 4 doesn't apply, because the currency (**CAD**) and shopper interaction (**POS**) are different.
* Rule 2 doesn't apply, because the payment method (**visasignature**) and the card region (**international**) are different.
* Rule 3 doesn't apply, because the payment method (**visa**) is different.
* Out of the rules that do apply, rule 5 has a higher priority than rule 1 because of the payment method (**mc**).

Adyen applies **rule 5** to split the transaction, and sends USD 1.50 + 1% to your liable balance account.

**Scenario 4: In-person payment in CAD in the US, using Mastercard issued in Canada**

* Rules 1, 3, and 5 do not apply, because of the currency (**USD**).
* Rule 2 doesn't apply, because of the shopper interaction (**Ecommerce**).

Adyen applies **rule 4** to split the transaction, and sends USD 1.40 + 1% to your liable balance account.

## Rounding split amounts

When Adyen splits funds automatically between balance accounts, we use half-to-even rounding logic to minimize bias toward rounding up or down too often. This logic also ensures that there are more balanced financial transactions over time.

Half-to-even rounding logic means that we look to the left of the last digit in the transaction:

* If the value is even, we round down.
* If the value is odd, we round up.

Because transaction amounts are rounded to two decimal places every time, this makes reconciliation easier.

The following examples show Adyen's rounding logic for automatic splits:

* **Rounding down:** The split amount is EUR 0.38725. The last digit is 5, so we look at the preceding digit, which is 2. Because it is **even**, we round down, to EUR 0.38.
* **Rounding up:** The split amount is EUR 0.38775. The last digit is 5, so we look at the preceding digit, which is 7. Because it’s **odd**, we round up, to EUR 0.39.

## Commission

With each payment you accept on behalf of your users, you can charge them a commission. A commission can either be a fixed amount (fixed fee), a percentage of the payment amount (variable fee), or both.

By default, the variable fee is calculated as a percentage of the total payment amount, which includes the tip and the surcharge paid by the customer. However, if you do not want to charge a commission on the tip and/or surcharge, you can exclude these from the commission calculation.

To configure your preferred commission calculation logic, reach out to our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other). Choose between the following options:

* Include the tip and the surcharge in the commission calculation (default).
* Only include the tip in the commission calculation.
* Only include the surcharge in the commission calculation.
* Exclude the tip and the surcharge from the commission calculation.

This means that we calculate all variable **Commission** and **Additional commission** fees defined in your split configuration profiles according to your chosen commission calculation logic.

### Example commission calculation

Consider the following example, where the customer buys goods worth USD 100.00 from your user. You charge both a fixed and a variable fee on the payment as your platform's commission.

| Price      | Tip       | Surcharge | Payment amount | Fixed fee | Variable fee             |
| ---------- | --------- | --------- | -------------- | --------- | ------------------------ |
| USD 100.00 | USD 10.00 | USD 1.00  | USD 111.00     | USD 5.00  | 5% of the payment amount |

The following table shows how we calculate the variable fee based on the logic you choose, and the total amount that is booked to your user. For each of these cases, the total amount paid by the customer is USD 111.00.

| Commission logic          | Amount on which you charge a commission | Fixed fee | Variable fee | Commission | Amount booked to user |
| ------------------------- | --------------------------------------- | --------- | ------------ | ---------- | --------------------- |
| Include tip and surcharge | USD 111.00                              | USD 5.00  | USD 5.55     | USD 10.55  | USD 100.45            |
| Tip only                  | USD 110.00                              | USD 5.00  | USD 5.50     | USD 10.50  | USD 100.50            |
| Surcharge only            | USD 101.00                              | USD 5.00  | USD 5.05     | USD 10.05  | USD 100.95            |
| Exclude tip and surcharge | USD 100.00                              | USD 5.00  | USD 5.00     | USD 10.00  | USD 101.00            |

## Captures

When you capture a payment that meets all the conditions of an automatic split rule, we book the funds according to the split logic of that rule. If the capture amount differs from the original authorization amount, we recalculate the split amounts, and apply the split instructions to the captured amount.

## Next steps

[required](/platforms/automatic-split-configuration/create-split-configuration)

[Create split configuration profiles](/platforms/automatic-split-configuration/create-split-configuration)

[Create a split configuration profile and link it to a store.](/platforms/automatic-split-configuration/create-split-configuration)
