One checkout, many payouts,
split correctly before anyone asks
A marketplace takes one payment from a buyer and owes pieces of it to several other parties, a seller, a delivery partner, your own commission, and that math has to be right every single time, not just most of the time. We build the ledger that tracks who owes what, the payout schedule, and the reconciliation that catches the one transaction that does not add up.
What it is
Split payments and payouts is the layer that sits between a marketplace’s checkout and its sellers’ bank accounts: it decides, for every order, how much of the buyer’s payment belongs to the seller, how much is your commission, and when that seller actually gets paid. Get the ledger wrong and sellers either get paid the wrong amount or get paid before a return window closes, both of which are expensive to unwind after the fact. We build this as an explicit ledger, not a derived number computed fresh every time someone asks.
When you need it (and when you do not)
You need this the moment your platform takes one payment that belongs, in part, to someone else: a marketplace with multiple sellers, a platform connecting service providers to clients, an affiliate or partner program that shares revenue per transaction. It becomes essential once manual payout calculation in a spreadsheet starts producing disputes, which tends to happen once you cross a few dozen active sellers.
You do not need a custom build if every transaction belongs entirely to you and nobody downstream needs a cut; a standard payment gateway integration covers that case without a ledger. It is also not worth building before you have real sellers or partners to pay, since the commission and hold rules are much easier to design against actual transaction patterns than guessed ones.
How we build it
The ledger lives in PostgreSQL as an explicit record: every order creates entries for what the buyer paid, what the platform takes, and what each other party is owed, computed once at order time from your commission rules and never recalculated silently later. Where Stripe Connect fits (most markets with reachable bank rails), we use its account and transfer model directly; where it does not reach a seller’s country, we integrate a local payout provider or bank transfer process and route the same ledger logic to it. Holds work the same way regardless of provider: a payout due date is set, and a dispute or return pushes that date back or reduces the amount, with the reason logged against the order.
Sellers see their own statement: what they earned, what was held and why, and when the next payout lands, so support is not the first place a seller goes to find out whether they got paid correctly. Every payout run produces a reconciliation report matching the money that left the platform’s account to the ledger entries it was meant to cover.
What to watch
Payout provider choice affects which countries you can actually reach and how fast money arrives; we confirm your seller geography before committing to a provider rather than assuming Stripe Connect covers it, since it does not everywhere. Commission rule changes mid-flight (a new seller tier, a promotional rate) need to apply going forward without rewriting history, which is why rules are versioned, not hardcoded into the ledger logic itself. Running cost includes the payout provider’s transfer fees, which we do not control and which vary by destination country.
Price and timeline
| Option | Price | What it covers | Timeline |
|---|---|---|---|
| MVP | from $2,500 | One payout provider, standard commission rule, scheduled payouts | 3 to 5 weeks |
| Production | from $6,500 | Multiple payout rails, tiered commissions, hold-and-release workflow, seller statements | 6 to 10 weeks |
Related
This usually follows payment gateway integration and pairs with fraud prevention for checkout so disputed charges are caught before a payout goes out, and with refunds and chargeback handling for the reverse flow. It sits inside the development and e-commerce services. The margin-guard and multi-party ledger logic here is close to what runs in the ProBay AI agent team and digital goods marketplace automation case studies.
Ready to stop reconciling seller payouts by hand? Get in touch and describe how your commission currently works.
FAQ
How much does a split-payment and payout system cost?
From $2,500 for a straightforward buyer-to-seller split with a configurable commission; multiple payout currencies or more than two parties per order add time.
How long does it take to build?
3 to 5 weeks, including a test run of payouts on real or sandbox transactions before go-live.
Do you use Stripe Connect or build payouts from scratch?
Stripe Connect where your sellers and markets support it; for markets where it does not reach, we integrate a local transfer or payout provider and keep the same ledger logic underneath.
Who owns the ledger and the payout schedule?
You. The ledger lives in your own database, and payout timing and commission rules are set by you, not defaulted by us.
What happens when a buyer disputes or returns an order after payout?
Payouts for an order can be held until a return or dispute window closes, and any already-paid amount is tracked for recovery against the seller's next payout, a rule we agree with you before building it.