GLOSSARY
Split payment
A split payment divides a single transaction between multiple recipients automatically at the point of payment, for example a marketplace sale where the seller, the platform and possibly a delivery partner each receive their correct share without a manual transfer afterward.
Why it matters
It is what makes a multi-vendor marketplace operationally viable at any real scale. Without it, someone has to manually calculate and transfer each party's share after every single transaction, which does not scale past a handful of sales a day and introduces constant risk of human error. It also matters for trust and retention on the vendor side specifically: vendors who see their share arrive correctly and on schedule treat the marketplace as a serious channel, while unreliable splitting drives them toward other platforms. It also has to account for currency conversion correctly when parties are in different countries, since a naive split calculated before conversion can produce a materially different result than one calculated after.
What goes wrong when it's handled badly
A checkout built for a single seller and later adapted for multiple vendors without genuine split-payment logic usually ends up with a workaround, one party receiving the full amount and manually paying the others, which is slow, error-prone and a trust problem if a payout is late or wrong. Stripe Connect and similar tools exist specifically to handle this correctly rather than as a workaround. A concrete example is a platform fee calculated correctly at the point of sale but not adjusted when a partial refund is later issued, leaving the platform having taken a fee on revenue that was actually returned to the customer. Logging every split calculation against its specific transaction, rather than only storing the final totals, is what makes a disputed split auditable and correctable rather than a guessing exercise. Reconciling calculated splits against actual bank transfers on a regular schedule is what catches a silent calculation error before it compounds across many transactions.