Skip to content

Reference stack

Launch marketplace payouts

A marketplace money-movement stack covering payee onboarding, collection, ledgering, splitting, payouts, tax data and reconciliation.

MarketplacesCreator platformsGig-economy products

Intended audience and markets

Audience

MarketplacesCreator platformsGig-economy products

Markets

Global

Infrastructure layers

01

Collection and merchant payments

Required

Collect funds from buyers or business customers.

Selection criteria

  • Merchant-of-record model
  • Supported payment methods
  • Reserves and chargebacks
02

Payee onboarding and KYB

Required

Verify sellers, businesses and beneficial owners.

Selection criteria

  • Individual and business coverage
  • Ongoing screening
  • Payout eligibility controls
03

Ledger and fund allocation

Required

Track seller balances, fees, reserves and refunds.

Selection criteria

  • Double-entry ledger
  • Split-payment support
  • Negative balance and reserve handling
04

Payouts and FX

Required

Pay recipients through local bank or wallet rails.

Selection criteria

  • Country and currency coverage
  • Recipient fees and timing
  • Returns and name matching
05

Fraud and monitoring

Required

Detect seller, account and transaction abuse.

Selection criteria

  • Account takeover and mule risk
  • Transaction monitoring
  • Case workflow

Implementation sequence

  • Collection and merchant payments
  • Payee onboarding and KYB
  • Ledger and fund allocation
  • Payouts and FX
  • Fraud and monitoring

Regulatory considerations

  • Marketplace funds flows may require payment-service authorisation or a licensed platform-payments structure.
  • Seller onboarding and reserve rules should match the merchant and payout model.

Technical considerations

  • Separate buyer payment state, seller balance and payout state.
  • Build reserve, refund and negative-balance logic before scaling.

Questions to ask providers

  • Which legal entity contracts for each service and in which jurisdictions?
  • Which responsibilities remain with the product operator rather than the provider?
  • What are the implementation, approval, testing and migration timelines?
  • How are incidents, exits, data portability and business continuity handled?
  • Who is merchant of record and who owes the seller?

What this stack does not cover

  • Tax calculation and local employment classification are outside this stack.

Related stacks

Reviewed on 2026-07-07.

Provider options are examples of infrastructure roles, not endorsements or a guarantee of suitability, availability or regulatory compliance. Confirm requirements for your product with each provider and qualified advisers.