{"title":"Split payments automatically","category":"default","creationDate":1776961628,"content":"

If you process your users' transactions through stores<\/a>, 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. This means that you do not need to send split instructions for every payment, capture, refund, or chargeback.<\/p>\n

For Adyen to automatically apply the split instructions, you need to:<\/p>\n

    \n
  1. Create a split configuration profile<\/a> that contains the conditions that determine whether to split a payment, and the instructions on how to split the payment (split logic).
    \nYou can create and manage your split configuration profiles and rules in your     Customer Area<\/a>, or using the Management API<\/a>.<\/li>\n
  2. Link the profile to your user's store<\/a> when you create or update the store.<\/li>\n<\/ol>\n

    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.<\/p>\n

    Split configuration profiles<\/h2>\n

    A split configuration profile contains at least one rule<\/strong>. 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.<\/p>\n

    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<\/a>.<\/p>\n

    Conditions<\/h3>\n

    The conditions define if<\/em> a transaction is split according to the split instructions. If a transaction meets all<\/strong> the conditions of the rule, then the split instructions are applied.<\/p>\n\n\n\n\n\n\n\n\n\n
    Condition<\/th>\nRequired<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
    Currency<\/td>\n\"Required\"<\/span><\/td>\nDefines whether the rule applies to a specific currency, or all currencies.<\/td>\n<\/tr>\n
    Payment method<\/td>\n\"Required\"<\/span><\/td>\nDefines 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<\/a> as well.<\/td>\n<\/tr>\n
    Card region<\/td>\n<\/td>\nDefines 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 transaction regardless of the processing and issuing location.
    List of regions:
    • US<\/li>
    • Canada<\/li>
    • Europe<\/li>
    • APAC<\/li>
    • LATAM<\/li><\/ul>
      This condition is in pilot phase, and not yet available for all platforms.<\/div><\/td>\n<\/tr>\n
    Funding source<\/td>\n\"Required\"<\/span><\/td>\nDefines whether the rule applies to a specific type of card, or all card types.<\/td>\n<\/tr>\n
    Shopper interaction<\/td>\n\"Required\"<\/span><\/td>\nDefines whether the rule applies to a specific sales channel, or all channels.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Split logic<\/h3>\n

    The split logic is a set of instructions that determine how<\/em> 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.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Split instruction<\/th>\nRequired<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
    Commission<\/td>\n\"Required\"<\/span><\/td>\nDefines the amount to book to your liable balance account as your platform's commission<\/a> on the transaction. It can be a fixed amount (specified in minor units), a percentage (specified in basis points), or both.<\/td>\n<\/tr>\n
    Transaction fees<\/td>\n\"Required\"<\/span><\/td>\nDefines where to book the transaction fees<\/a>. We can book the fees either to your liable balance account or your user's balance account, together or separately.<\/td>\n<\/tr>\n
    Additional commission<\/td>\n<\/td>\nDefines whether we book an additional commission to your user's balance account.<\/td>\n<\/tr>\n
    Refund<\/td>\n<\/td>\nDefines where to book the refund amount.<\/td>\n<\/tr>\n
    Refund cost allocation<\/td>\n<\/td>\nDefines where to book the fees associated with refunds.<\/td>\n<\/tr>\n
    Chargeback<\/td>\n<\/td>\nDefines where to book the chargeback amount.<\/td>\n<\/tr>\n
    Chargeback cost allocation<\/td>\n<\/td>\nDefines where to book the fees associated with chargebacks.<\/td>\n<\/tr>\n
    Remainder<\/td>\n<\/td>\nDefines where to book the leftover amount (after currency conversion).<\/td>\n<\/tr>\n
    Surcharge<\/td>\n<\/td>\nDefines where to book surcharges.<\/td>\n<\/tr>\n
    Tip<\/td>\n<\/td>\nDefines where to book tips.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    When a transaction meets all<\/strong> conditions of the rule, Adyen applies the corresponding split logic.<\/p>\n

    We recommend that you always include a catch-all rule (set all conditions to ANY<\/strong><\/span>) in your profile, because if none of the rules apply to the transaction, then all funds are booked to your liable balance account by default.<\/p>\n

    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.<\/p>\n

    Rule hierarchy<\/h2>\n

    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.<\/p>\n

    The priority of rules is:<\/p>\n

      \n
    1. Currency<\/li>\n
    2. Payment method or payment method variant<\/a>, like visa<\/strong><\/span> or visasignature<\/strong><\/span><\/li>\n
    3. Card region<\/li>\n
    4. Funding source<\/li>\n
    5. Shopper interaction<\/li>\n<\/ol>\n

      The granularity of a rule refers to how specific the rule is, for example:<\/p>\n