starter.wiki

Payments

Marketplace Payments

Choose the connected-account, funds-routing, split-payment, balance, payout, dispute, and platform-liability model.

Recommendation

Choose the funds-flow and liability model before the platform provider.

Developer-platform, enterprise-platform, and wallet-oriented routes expose different account, payment, payout, and loss boundaries.12

For: Marketplaces and platforms moving money among multiple parties

Main trade-off

Marketplace payment platforms accelerate regulated onboarding and money movement while creating deep coupling around accounts, KYC/KYB, charge types, balances, payouts, disputes, reserves, data, and migration.123

Three marketplace-payment routes

The correct route follows platform geography, account model, charge type, payout, loss, and operational ownership.

  1. Platform and account model

    Define platform role, sellers, service providers, connected accounts, KYC/KYB, country coverage, and control.1

  2. Funds flow

    Model charge type, destination, split, platform fee, balances, reserves, refunds, disputes, chargebacks, and negative balances.12

  3. Payout and reporting

    Verify payout destinations, schedules, FX, tax reporting, reconciliation, statements, support, and account closure.1

  4. Liability and cost

    Assign losses and compliance duties, then model processing, account, payout, FX, dispute, reserve, support, and contract costs.1

Marketplace payment routes

All routes require product-, country-, account-, and contract-specific evidence.

An API-led software platform route fits

Evaluate Stripe Connect.

Connect provides connected-account and charge models for software platforms.

Verify: Verify account control, countries, charge type, liability, payouts, tax, data, and Connect-specific pricing.1

Enterprise platform and acquiring operations are justified

Evaluate Adyen for Platforms.

Adyen for Platforms fits organizations operating a larger global commerce boundary.

Verify: Do not inherit claims from Adyen Payments; verify platform product, geography, accounts, funds flow, liability, and contract.2

Wallet and platform infrastructure fits the market

Evaluate Mangopay.

Mangopay provides a platform payments route centered on account, wallet, and payout infrastructure.

Verify: Verify supported countries, user types, KYC, funds safeguarding, payouts, fees, data, and migration.3

Boundary: Marketplace Payments owns multi-party accounts and funds flow. Direct Payments, Merchant of Record, Identity Verification, and Payment Fraud Prevention remain separate decisions.

What actually differs

Account control, funds routing, liability, geography, payout, and contract structure determine fit.

Accounts
Onboarding, KYC/KYB, platform control, data, and account closure differ.13
Funds flow
Charge types, splits, destination, balances, reserves, refunds, and disputes allocate responsibility differently.12
Payouts
Countries, methods, timing, FX, fees, statements, and failed payouts are provider-specific.12
Liability
Loss, chargeback, compliance, tax reporting, support, and reserve responsibilities depend on the exact model.13

Official resources

Verify current product scope, eligibility, pricing, policy, data, payout, and contractual boundaries in first-party material before implementation.

DocumentationAdyen for Platforms

Sources

Official product and policy sources supporting the bounded routes on this page.

  1. 1
    How Stripe Connect works

    Stripe · Accessed Official

  2. 2
    Adyen for Platforms

    Adyen · Accessed Official

  3. 3
    Mangopay documentation

    Mangopay · Accessed Official