Use a computer

For full performance and fluidity, please open Pay Engineers on a desktop or laptop. On mobile, the experience is limited — especially authenticated sections and advanced tools after login.

Payment infrastructure Must read

Marketplace split payments without losing your licence narrative

Escrow, seller KYC and settlement timing are the three pillars of compliant platform payments. We explain how sub-merchant profiles, dispute freezes and transparent T&Cs keep marketplaces from quietly drifting into unlicensed money transmission.

Jul 8, 2026 5 min 3,968 0

Marketplaces rarely set out to become payment institutions. They set out to connect buyers and sellers, and payments feel like plumbing — until a regulator points out that routing funds from a buyer, holding them briefly, and forwarding a share to a seller is precisely the activity that money transmission and payment services regulation was written to capture. Platforms that treat sellers as "just another payout destination" often discover this too late.

The regulatory trap

Most jurisdictions carve out limited exemptions for commercial agents and platforms that never take title to funds, but those exemptions are narrower than founders assume, and they typically depend on transparent terms, clear escrow-like handling, and defensible commission logic. Once a platform starts offering "instant payouts", advancing funds against future sales, or blending commissions in ways sellers cannot audit, the commercial agent argument weakens fast.

The safer, more durable pattern is transparent escrow: funds are clearly held on behalf of a named beneficiary, beneficial ownership is documented through proper KYC, and settlement timing is predictable and disclosed. This is not just a legal nicety — it fundamentally changes how your product must be engineered.

Sub-merchant profiles and KYC gating

Technically, compliant split payments require a sub-merchant (or sub-account) model where each seller has a distinct profile with its own risk tier, its own KYC/KYB status, and its own payout eligibility. Payouts must be gated by that status — a seller who has not completed identity verification, or whose verification has lapsed, should simply be unable to receive funds, enforced at the ledger level, not by a manual process someone might forget to run.

Commission ledgers

Every split — platform fee, payment processing fee, tax withholding where applicable — needs its own typed posting in the ledger, attributable back to the original transaction. Sellers should be able to see, transaction by transaction, exactly how their payout figure was constructed. Ambiguous commission calculations are one of the most common sources of seller disputes and support escalations.

Dispute freezes and reserve logic

When a buyer disputes a transaction, the platform needs a mechanism to freeze the relevant portion of a seller's balance pending resolution, without freezing unrelated funds. This requires the ledger to track holds at the transaction level, not just at the account level, and requires a case management workflow that ties disputes back to specific journal entries.

Reserve policies — holding back a percentage of new sellers' payouts for a defined window — should be encoded as explicit, auditable rules rather than ad hoc interventions, both for fairness to sellers and for defensibility if challenged.

Choosing your infrastructure

Whether you embed a specialised platform-payments provider such as Mangopay, Lemonway or Adyen for Platforms, or build a custom stack on top of a licensed partner, the product narrative must match the licence story precisely. A pitch deck that says "instant seller payouts" while your underlying licence exemption depends on holding funds only briefly and predictably is a mismatch that regulators, banking partners and auditors will eventually notice.

An operational checklist

  • Document beneficial ownership and KYC status for every seller before enabling payouts.
  • Gate payout eligibility by verification status at the ledger layer, not by manual review.
  • Give every commission and fee its own traceable posting back to the source transaction.
  • Build transaction-level holds so disputes freeze only the affected funds.
  • Align your public T&Cs on settlement timing with what your licence exemption actually permits.
  • Review your commercial agent or escrow narrative with counsel whenever payout features change.

Where platforms get caught out

The most frequent failure is a mismatch between marketing promises and back-end reality: growth teams promise faster payouts to win sellers, while the underlying licensing arrangement was designed around slower, predictable settlement. That gap is invisible until a regulator, banking partner or auditor asks to see the money flow end to end.

Your payout speed is a compliance decision before it is a product decision.

Working with legal counsel throughout the build

Marketplace payment features tend to evolve quickly — a new payout speed tier, a new financing product advancing funds against future sales, a new cross-border seller cohort — and each of these changes the regulatory analysis underpinning your commercial agent or escrow exemption. Treat legal review as a recurring checkpoint tied to the product roadmap, not a one-time sign-off obtained before initial launch and never revisited.

Engineering teams should flag any new payout-related feature to legal before building it, specifically because the exemption analysis is sensitive to exactly the kind of detail that only becomes clear once a feature is scoped technically — how funds are held, for how long, and under what conditions they can be advanced or withheld.

Key takeaways

  • Commercial agent exemptions depend on transparency and predictable settlement — not marketing convenience.
  • Sub-merchant KYC status should gate payouts automatically at the ledger level.
  • Commission ledgers must be traceable to the transaction level for sellers and auditors alike.
  • Dispute freezes need transaction-level holds, not blunt account-wide restrictions.
  • Keep your public payout promises aligned with the licensing narrative underneath them.

Comments

0 comments

Sign in to leave a comment.

Anmelden

No comments yet. Be the first to comment.

Keep reading

Related articles

More content that may interest you

View all posts
Featured
Payment infrastructure

What a modern payment processor actually contains

Beyond "accepting cards": the modules, data flows and operational surfaces that define a production-grade processor. We break down the acquiring core, risk engine, ledger, settlement pipeline and partner connectivity layers most roadmaps forget about until launch is already running late.

17/07/2026 5 min 4,209 0
Featured
Payment infrastructure

Payment gateway vs payment processor: choosing the right layer

A practical decision framework for fintech founders deciding what to build, buy or white-label. We unpack where gateways end and processors begin, why the distinction gets blurry in real products, and how hybrid architectures let you keep optionality while you scale.

14/07/2026 5 min 4,553 0
Payment infrastructure

Designing ledgers for wallets and stored-value products

Double-entry fundamentals, hold states and why "just a balance column" fails under audit. A deep dive into account typing, journal design and the reconciliation guarantees regulators and auditors expect from any product that stores customer value.

11/07/2026 5 min 4,458 0