A marketplace has to do three things with one payment: take the buyer’s money, keep its own commission, and pay the seller. Ordinary card acceptance does none of this. It puts the whole amount into one account and leaves the rest to you and a spreadsheet.
Marketplace split payments and escrow exist to close that gap. Here is how the money actually divides, when it should wait, who carries the risk of a dispute, and what has to be in place before any of it works.
What the payment flow has to do
Strip the marketing away and a marketplace flow has four obligations.
- Accept one payment from a buyer who sees a single price and a single charge on the statement.
- Divide it between the seller, the platform commission and anything else the model requires.
- Hold the seller’s share until the deal is actually completed, if the model needs that.
- Pay the seller out on schedule, to whatever destination was agreed.
Doing this by hand works up to a few dozen sellers and then stops. What is needed is a payment processing setup where the split is a property of the transaction rather than a monthly reconciliation task.
Split payments: how the money divides
In a split, the division happens at the moment of the transaction, not afterwards. One buyer payment produces several settlement records: the seller’s share, the platform’s commission, and, where relevant, a separate line for delivery or tax.
Two consequences follow, and both matter more than they sound.
Reconciliation stops being manual. Every payment already knows who it belongs to, so month-end is a report rather than an investigation.
The platform never holds money it does not own. The seller’s share is attributed from the start, which is a very different position to hold in a conversation with a provider than “everything lands with us and we distribute it”.
Escrow: when the money waits
Escrow means the seller’s share is held until the condition is met — delivery confirmed, service rendered, return window closed. The buyer’s money has left their card; the seller does not have it yet.
It is worth the friction where the deal has a delivery gap: physical goods shipped over days, services performed later, or high average tickets where a single bad transaction hurts. It is unnecessary friction where fulfilment is instant.
The practical benefit is dispute prevention. A buyer who can see that funds are held until delivery goes to support rather than to the bank — and a refund costs 50 EUR while a chargeback costs 100 EUR and damages the ratio that decides your terms.
Who carries the risk of a dispute
This is the question providers ask first, and the answer decides both your terms and your reserve.
In card schemes a dispute is raised against the merchant of record — the entity the buyer paid. For most marketplace models that is the platform, not the seller. So when a seller ships nothing, it is the platform’s dispute ratio that suffers and the platform’s reserve that grows.
That is why seller onboarding is a payment question, not an administrative one: who you let sell determines what you pay. Sellers with no history, no verified identity or no delivery record produce disputes, and the cost lands on the platform. The merchant account terms are set with exactly this in mind.
If sellers are charged on a schedule rather than one purchase at a time, the assessment changes with it — recurring revenue is looked at separately, and that is covered in our piece on merchant accounts for subscription businesses.
Paying sellers out
The payout side is a separate mechanism, and it is where marketplaces usually underestimate the work. Sellers want different destinations, different currencies and different schedules, and each route has its own price.
Card payouts cost 4% plus 1.00 EUR per transaction with us; transfers and other routes are priced separately, and mass payouts — including to crypto addresses — run as a batch rather than one by one. What each route costs is on the pricing page.
The mechanics themselves — schedules, destinations, batching — sit under payouts. Worth deciding early: a weekly batch and a daily one produce very different support loads.
What to have ready before connecting
- A clear description of who sells on the platform. Vertical, average ticket, delivery time. This drives the assessment more than turnover does.
- Seller onboarding rules. What you verify and what you refuse. A platform with no rules is priced as a platform with the worst possible sellers.
- A published dispute and refund policy that a buyer can find before paying, not after.
- Your own settlement setup. Acceptance and holding are separate services, priced separately — what the acceptance side costs is broken down in our piece on what card acceptance costs.
Terms
A marketplace collects disputes from other people’s sales, so the ratio is the number to watch from day one. The thresholds the card schemes monitor are in our piece on VAMP guidelines for high-risk merchants.
In short
A marketplace does not need “payment acceptance”. It needs a flow that divides one payment correctly, holds the seller’s share while the deal is open, and pays out on schedule — with the understanding that the platform, not the seller, usually carries the dispute. Get seller onboarding right and the payment terms follow.