Split payments allow one customer transaction to be allocated between two or more recipients.
A business might use split-payment functionality to deduct a commission, allocate revenue between different parties, pay service providers, distribute funds between connected accounts or manage more complex multi-party transactions.
The exact payment flow depends on the payment provider, acquiring setup and integration. Businesses should understand who receives the customer payment, how the split is calculated, when each party is paid and how refunds, chargebacks and processing fees are handled.
Split payments are not the same as instalment payments. Instalments divide what the customer pays over time; split payments divide the proceeds of a transaction between different recipients.
What are split payments?
Split payments allow a single transaction to be divided between two or more recipients according to predetermined rules.
For example, a customer makes a £100 payment.
The payment instructions could allocate:
- £80 to the business providing the underlying service;
- £15 to another participating business; and
- £5 as a platform or service fee.
Alternatively, the transaction might be divided using percentage-based commissions, fixed charges or different rules for individual recipients.
This allocation can be automated within the payment infrastructure rather than the business receiving the entire payment first and manually transferring money afterwards.
How do split payments work?
The exact process varies between payment providers, but a typical split-payment flow involves several stages.
1. The customer makes one payment
The customer pays through a website, app, booking system, software platform or other checkout.
From their perspective, this can look like a standard card transaction.
2. The transaction is authorised
The payment gateway passes the transaction through the relevant payment infrastructure for authorisation.
The customer's card issuer approves or declines the transaction in the normal way.
3. The payment system receives the split instructions
The integration tells the payment provider how the transaction should be allocated.
The instructions might specify:
- a fixed amount for each recipient;
- a percentage commission;
- several different recipients;
- different rules depending on the product or service;
- transaction-specific fees; or
- which party pays the processing charges.
This is one reason payment API integration can be important for more complex split-payment setups.
4. The transaction is allocated
Once the payment is processed, the provider applies the agreed allocation rules.
Depending on the setup, the money may be attributed to connected accounts, balances or individual recipients.
This does not necessarily mean that each recipient immediately receives money into its bank account.
Allocation and payout are separate parts of the payment process.
5. Payouts are made
Each recipient receives its funds according to the agreed settlement or payout schedule.
That could include:
- daily payouts;
- weekly payouts;
- scheduled payouts;
- payouts after a specified delay; or
- event-triggered payouts.
The available options depend on the provider and the underlying account structure.
Find Suitable Payment Providers
Split payments are not the same as instalments
The term “split payment” is sometimes used to describe several different payment arrangements, but these should be separated.
Multi-party split payments
One customer payment is divided between different recipients.
Instalment payments
One customer pays for a purchase over several payment dates.
Deposit and balance payments
The customer pays part of the cost now and the remainder later.
Recurring payments
A customer is charged repeatedly under an ongoing billing arrangement.
Multiple-card payments
Two or more customers or cards contribute towards the same purchase.
A payment provider may support several of these functions, but they are technically and commercially different requirements.
What can split-payment rules control?
Split-payment technology can support more than simply dividing a transaction in two.
Depending on the provider, businesses may be able to define rules around:
Fixed commissions
A set amount is deducted from every transaction.
For example, a £3 service charge could be allocated to one party and the remainder to another.
Percentage commissions
A business might retain 10% of a payment and allocate the remaining 90% elsewhere.
Different recipient rules
Different parties may operate on different commercial terms.
One recipient might attract a 10% commission while another attracts 15%.
Multiple recipients
Some payment structures need to allocate one customer transaction between more than two parties.
The number of recipients a provider can support should therefore be established during the technical assessment.
Processing fees
The payment setup may also determine who absorbs card-processing charges and other transaction costs.
This can materially affect the amount ultimately received by each party.
Where are split payments used?
Split-payment functionality can be relevant to several different business models.
Examples include:
- software platforms;
- booking systems;
- marketplaces;
- franchises;
- travel businesses;
- professional-service platforms;
- multi-location businesses;
- commission-based business models; and
- businesses coordinating several service providers.
A marketplace is one application of split-payment technology, but marketplace payments normally involve a broader set of questions around seller onboarding, multi-vendor transactions, compliance, payout structures and the relationship between the platform, sellers and the payment provider.
If you specifically operate a multi-seller platform, read our dedicated Marketplace Payment Gateways guide.
Split payment APIs and integrations
For more complex payment models, split instructions may be passed to the payment provider through an API.
The business's system may need to tell the payment infrastructure:
- how much has been paid;
- which parties should receive funds;
- how much commission should be deducted;
- which account or balance receives each allocation;
- when a transaction should be captured;
- how refunds should be divided; and
- which information should be returned for reconciliation.
Businesses with bespoke software should establish what the API can control before choosing the underlying payment provider.
Changing provider later can become more difficult where payment logic is deeply embedded into a platform's own systems.
Our Payment API Integration guide explains the wider technical considerations when connecting payment infrastructure with business software.
Split payments and embedded payments
Split-payment functionality can also form part of a wider embedded payments model.
For example, a software business may integrate payment acceptance directly into its platform while also controlling commission rules, recipient onboarding, reporting and payout functionality.
The important distinction is that split payments describe how funds are allocated, while embedded payments describe a broader model in which payment functionality becomes part of the software or platform experience.
What happens with refunds?
Refund handling is particularly important where the original payment has already been divided.
For example, if a £100 transaction was divided between two recipients and the customer later receives a £40 refund, the payment system needs rules for determining where that £40 comes from.
Businesses should establish:
- whether refunds reverse the original split;
- whether commissions are returned;
- whether processing charges are refundable;
- how partial refunds are handled;
- what happens if one recipient no longer has sufficient funds; and
- how refunds appear in reporting.
These processes can vary between providers and should be understood before the payment flow is built.
What happens with chargebacks?
The same principle applies to chargebacks and disputes.
Businesses should understand which party carries the financial responsibility if a customer disputes a payment.
Depending on the commercial and payment structure, the disputed amount might be taken from:
- the underlying seller or service provider;
- the platform;
- a connected balance;
- a reserve; or
- another agreed account.
The contract and technical implementation should make this clear before processing begins.
Settlement and reconciliation
Splitting money successfully is only one part of the requirement.
The business also needs to understand what happened to each transaction afterwards.
Useful reporting can include:
- original transaction amount;
- individual recipient allocations;
- commission deducted;
- payment-processing fees;
- refund adjustments;
- chargeback adjustments;
- recipient balances;
- payout amounts;
- payout dates; and
- transaction references.
Good reconciliation becomes increasingly important as transaction volumes and the number of recipients increase.
Do split payments create regulatory considerations?
Potentially.
The regulatory position depends on how the business model and movement of funds are structured.
The Financial Conduct Authority notes that businesses such as online marketplaces and other companies that bring buyers and sellers together may need to consider whether they are providing payment services where customer money is received before being passed to another party.
Businesses should therefore understand:
- who receives the customer's payment;
- who provides the underlying goods or services;
- who controls the funds;
- who is responsible for refunds;
- who carries chargeback liability;
- which party contracts with the customer; and
- which regulated payment provider sits behind the transaction.
Using a payment provider that supports multi-party payment flows can help structure the payment process, but businesses should still establish the regulatory and contractual model before building the technical integration.
How much do split payments cost?
There is no single standard price for split-payment processing.
Potential costs can include:
- card-processing fees;
- gateway fees;
- connected-account charges;
- payout fees;
- transaction-allocation fees;
- international-card charges;
- foreign exchange;
- refund charges;
- chargeback fees;
- platform fees;
- setup or integration costs; and
- monthly charges.
Businesses should therefore compare the complete cost of the proposed payment flow rather than only comparing the advertised transaction percentage.
For a wider explanation of online payment costs, read our Payment Gateway Fees guide.
What should you compare between split-payment providers?
Before approaching providers, document exactly how you need the transaction to work.
Start by answering:
- Who makes the payment?
- Who provides the product or service?
- How many recipients can be included in one transaction?
- How should the transaction be divided?
- Does the business deduct commission?
- Who pays the processing costs?
- When should each recipient receive their funds?
- Who manages refunds?
- Who carries chargeback liability?
- Which countries and currencies are involved?
- What reporting is required?
- What software or API needs to connect to the payment provider?
You can then compare providers on:
- split-payment functionality;
- API capability;
- integration requirements;
- settlement and payout options;
- reporting;
- refund handling;
- chargeback processes;
- international capability;
- payment methods;
- acceptance criteria;
- support; and
- total processing cost.
Find Suitable Payment Providers
Choosing a split-payment solution
The starting point should be the payment flow, not the provider name.
Map what happens from the moment the customer pays through to the point each recipient receives its money.
That makes it easier to identify whether you need simple transaction allocation, more sophisticated multi-party payment infrastructure or a wider platform-payment solution.
For a broader explanation of gateways, integrations and online payment infrastructure, visit our Payment Gateways guide.
If you operate a marketplace or multi-seller platform specifically, read our Marketplace Payment Gateways guide.
Sources & References
About Merchant Advice Service
Merchant Advice Service (MAS) provides independent information, comparison and provider-matching support for UK businesses looking for payment services.
We help businesses understand their payment requirements before introducing them to providers that may be suitable. MAS does not provide payment processing services directly.
Disclosure: Merchant Advice Service may receive commission from payment providers following a successful introduction. This does not increase the price paid by the merchant and does not determine which providers are included in our editorial guidance.
