Multi-vendor · pay-in / split / pay-out

Marketplace payment solutions — one pay-in, many pay-outs, one API.

topropay handles the full multi-vendor flow: collect from the buyer through every supported method, split per seller against the marketplace's commission rules, optionally hold funds during a settlement window, and pay out to each seller through the rail they prefer.

Book a marketplace review Read the API docs
Buyer topropay · split + hold Seller A Seller B Seller C Seller D one chain · one ledger · per-seller payout rail
Buyer · split · seller A–N · all in one chain.
1 pay-in
buyer charge across cards, wallets, BNPL and bank rails
N splits
per-seller share computed at capture or settlement
N pay-outs
to seller bank account, card or stablecoin
1 ledger
across pay-in, split, hold and pay-out

Key benefits

Why operators pick this marketplace gateway shape

Four properties that show up the moment seller onboarding, splits and payouts stop living in three separate vendors and become primitives on one platform.

  1. 01

    Onboard sellers without re-integrating

    Sellers onboard through topropay's KYB flow against the marketplace's sub-merchant model. New seller, new commerce flow — no per-seller integration on the marketplace's side.

  2. 02

    Split per seller, not per order

    Splits are computed per line item against per-seller commission rules; the platform produces N seller-level transactions from one buyer charge, all tied to the same buyer authorisation.

  3. 03

    Hold funds while orders settle

    Configurable hold windows let the marketplace release funds only after fulfilment or dispute window. Operator-side controls handle release, partial release and clawback.

  4. 04

    Pay out the way each seller prefers

    Payouts to SEPA / ACH bank accounts, push-to-card via Visa Direct / Mastercard Send (through partner connectivity) or stablecoin via licensed partner gateways — chosen per seller.

How marketplace payment processing works

From one buyer charge to N seller payouts in five steps

What happens between the buyer's tap and the row in each seller's bank account — and where topropay sits inside the chain.

  1. 01

    Buyer pays once on the storefront

    The buyer pays one amount through the marketplace's checkout — card, wallet, BNPL or bank rail. The whole authorisation is built and routed through the marketplace's connected acquirer panel.

  2. 02

    Order splits computed per seller

    The platform computes per-line-item splits using the marketplace's commission rules. Each split row identifies the seller, gross amount, commission, fees and net amount.

  3. 03

    Funds optionally held

    If the marketplace runs a hold window (escrow-style), funds sit in the platform's held-funds ledger until the marketplace's release condition fires.

  4. 04

    Payouts dispatched

    On release, the platform initiates payouts to each seller through the seller's chosen rail — SEPA, ACH, Faster Payments, push-to-card or stablecoin. Each payout fires a signed webhook.

  5. 05

    Reconciliation across the lifecycle

    Reconciliation ties the original buyer authorisation, each per-seller split, the hold-and-release events and the outbound payouts together as one chain in the ledger.

Main use cases

Where this marketplace payment platform earns its keep

Six recurring marketplace shapes — physical goods, services, creators, B2B procurement, travel and cross-border — each with a different release-and-payout policy on top of the same platform primitives.

  • Goods

    Multi-vendor physical-goods marketplaces

    Marketplace gateway flows for physical goods — buyer pays per cart, splits per vendor, payouts on delivery confirmation.

  • Service

    Service-marketplace bookings

    Booking platforms (lessons, services, rentals) split per provider, with hold windows tuned to the cancellation policy.

  • Creator

    Creator and content platforms

    Recurring subscriptions or one-off purchases split per creator; payouts on a fixed cadence rather than per-transaction.

  • B2B

    B2B procurement marketplaces

    B2B marketplaces split per supplier with longer hold windows and net-30 / net-60 payout cadences against the buyer-side card or invoice.

  • Travel

    Travel and ticketing marketplaces

    OTA-style flows with auth-only at booking, capture at fulfilment, splits to the supplier on capture and refund-side reversal of the split if the booking cancels.

  • Cross

    Cross-border marketplaces

    Buyer in one currency, seller in another — the platform handles per-side currency on settlement; payouts go out in the seller's preferred currency.

Platform features

Capabilities behind the online marketplace payment solutions

Twelve capabilities split between pay-in / split-engine and hold / pay-out / finance — each one a platform primitive rather than a bolt-on.

Pay-in & splits

  • Unified API across methods

    One REST contract for card, wallet, BNPL, ACH, SEPA, PIX and crypto on the pay-in side.

  • Per-line-item splits

    Splits computed per line item using marketplace commission rules; tied back to the same buyer authorisation.

  • Smart routing & cascading

    Per-transaction scoring on BIN, scheme, currency, country pair and risk across the connected acquirer panel.

  • PCI L1 vault

    Card data captures into the platform vault before any acquirer sees it; PAN never lands in marketplace systems.

  • Network tokens

    VTS / MDES tokens by default for card; scheme updaters keep saved cards alive across re-issuance.

  • Selective 3DS2 / SCA

    EMV 3DS2 challenges fire selectively per PSD2 exemption logic on the pay-in side.

Hold, pay-out & finance

  • Held-funds ledger

    Configurable hold windows with operator-side release, partial release and clawback events logged for audit.

  • Seller onboarding (KYB)

    Per-seller KYB and sanctions screening against the marketplace's sub-merchant model; new sellers onboard without marketplace re-integration.

  • Multi-rail payouts

    SEPA, ACH, Faster Payments, push-to-card via Visa Direct / Mastercard Send, and stablecoin via licensed partner gateways.

  • Payout scheduling

    Per-transaction, per-cycle (daily / weekly / monthly) or release-on-condition payout cadences per seller.

  • One reconciliation ledger

    Pay-in, splits, holds, releases and payouts tied to the same buyer authorisation chain in one feed.

  • Operator-side controls

    Refunds, releases, clawbacks and reversals require justification and log every event with actor identity, reason and timestamp.

Industry relevance

marketplace payment system fit for licensed operators in EU, UK, APAC and LATAM

topropay's marketplace posture targets licensed marketplace operators across Europe, the UK, APAC and LATAM — physical goods, services and content marketplaces, B2B procurement, travel and ticketing, and cross-border operators with sellers in multiple currencies. Marketplaces operating in adult content, unlicensed gambling and other grey-market verticals are out of scope regardless of marketplace shape.

Fits
  • Multi-vendor physical-goods commerce
  • Service and booking platforms
  • Creator / content marketplaces
  • B2B procurement marketplaces
  • Travel and ticketing OTAs
Doesn't fit
  • Adult-content marketplaces
  • Unlicensed gambling marketplaces
  • Grey-market or unregulated financial flows

Trust & compliance

Compliance posture across marketplace payment processors

One audited environment for the orchestration layer plus per-seller KYB at onboarding. Sellers inherit the relevant posture under the marketplace's sub-merchant model without carrying separate certifications themselves.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sellers inherit the posture under the marketplace's sub-merchant model.
Sub-merchant model
Sellers onboard as sub-merchants under the marketplace; the marketplace doesn't need a payment-institution licence to operate the flow.
AML / sanctions screening
Per-seller KYB at onboarding plus ongoing sanctions screening; AML monitoring tuned per marketplace vertical and seller mix.
SCA / PSD2 on pay-in
Selective 3DS2 keeps approval high in Europe without skipping the SCA bar on the buyer-side authorisation.
Scheme programme posture
Per-acquirer position vs Visa (VDMP / VAMP / VFMP) and Mastercard (ECP / EFMP) programme thresholds surfaced in the dashboard.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of marketplace shape.

Ready to unify pay-in and pay-out

Bring your marketplace onto a unified pay-in, split and pay-out API.

A 30-minute marketplace review covers seller-onboarding KYB, commission and split rules, the held-funds policy, the seller-payout rails for your geographies, and a sandbox you can test against before any commercial commitment.

Book a marketplace review Read the API docs

Frequently asked

Buyer questions about marketplace payment solutions on topropay

Definitions, gateway / processor framing, split mechanics, held-funds policy and the practicalities of running a multi-vendor marketplace through one platform.

  1. 01

    What do marketplace payment solutions on topropay actually cover?

    marketplace payment solutions on topropay cover the full multi-vendor flow: collect from the buyer (cards, wallets, BNPL, bank rails), split per seller using the marketplace's commission rules, optionally hold funds during a settlement window, pay out to each seller through their preferred rail, and tie the whole chain together in one reconciliation ledger. Seller KYB and the sub-merchant model are built in.

  2. 02

    Is the platform a marketplace gateway or a full processor?

    topropay is both — a marketplace gateway in front of multiple connected acquirers, plus the platform that handles seller onboarding, splits, held funds and payouts. The 'gateway' role is one face of a wider orchestration product.

  3. 03

    How does marketplace payment processing differ from single-merchant processing?

    marketplace payment processing differs from single-merchant processing in three places: (1) sellers onboard as sub-merchants under the marketplace's master record, with per-seller KYB; (2) one buyer authorisation produces N seller-level split rows; (3) funds may sit in a held-funds ledger before payout, rather than settling directly to a single merchant bank account.

  4. 04

    Can topropay be described as a marketplace payment gateway?

    Yes. marketplace payment gateway describes the inbound pay-in role topropay fills — the unified API exposes one authorise endpoint that handles card, wallet, BNPL and bank rails, and the gateway-side routing fans the authorisation across the connected acquirer panel before the marketplace logic (splits, holds) kicks in.

  5. 05

    Is topropay a viable payment gateway for marketplace flows specifically?

    Yes. payment gateway for marketplace flows is a primary use-case — the sub-merchant model, splits, held funds and multi-rail payouts are platform primitives rather than bolt-ons. Marketplaces in physical goods, services, content, B2B, travel and cross-border patterns all use the same set of primitives, configured differently.

  6. 06

    Is there a separate marketplace payment platform product?

    There isn't a separate marketplace payment platform product on topropay — the marketplace-specific primitives (sub-merchants, splits, held funds, multi-rail payouts) are part of the unified platform. The marketplace toggles them on per sub-merchant; a single tenancy can mix marketplace and non-marketplace merchants.

  7. 07

    How do online marketplace payment solutions handle cross-border flows?

    online marketplace payment solutions for cross-border flows on topropay handle buyer-side currency through the local acquirer panel for the buyer's country, and seller-side currency on the payout side through the seller's chosen rail. Each side settles in its own currency; FX is at the payout rail's mid-market rate plus a configurable spread.

  8. 08

    How is payment gateway marketplace acceptance different from regular acceptance?

    payment gateway marketplace acceptance differs from regular acceptance in the structure of the authorisation lifecycle. A regular acceptance ends at capture and settlement to one bank account; marketplace acceptance continues through per-seller splits, hold windows and seller-side payouts — and reconciliation needs to tie the whole chain together end-to-end.

  9. 09

    What is the best payment gateway for marketplace flows?

    The 'best payment gateway for marketplace' depends on the marketplace's scale, geography mix and seller-payout requirements. topropay's pitch is that the gateway role is one face of a wider orchestration platform — splits, held funds, multi-rail payouts and seller KYB live behind the same contract, so the marketplace integrates once rather than stitching together separate pay-in and pay-out vendors.

  10. 10

    How does the wider marketplace payment system fit together?

    The wider marketplace payment system on topropay is a chain: gateway / vault → smart routing → connected acquirer → settlement → split engine → held-funds ledger → payout rail → seller account. The marketplace integrates against the API; topropay operates the chain on the platform side.

  11. 11

    Does the platform work as a multi vendor marketplace payment gateway?

    Yes. multi vendor marketplace payment gateway is the default deployment shape — one marketplace, many sellers each onboarded as sub-merchants. Per-seller commission rules, per-seller payout schedules and per-seller payout rails are dashboard-configurable; the merchant doesn't fork the integration per seller.

  12. 12

    Which marketplace payment processors does topropay work with?

    marketplace payment processors on the pay-in side are the connected acquirers in the panel — selected per region the marketplace operates in. On the pay-out side, processors include local bank-rail providers (SEPA, ACH, Faster Payments), Visa Direct / Mastercard Send partners, and licensed partner crypto gateways. The marketplace doesn't pick them individually — they're surfaced as routing / payout options.

  13. 13

    Is this a marketplace platform payment gateway suitable for high-volume operators?

    Yes. marketplace platform payment gateway capacity on topropay scales with the connected acquirer panel; horizontal-routing across multiple acquirers means no single processor is the bottleneck. High-volume marketplaces typically run with 3+ acquirers per region for routing diversity and chargeback-programme resilience.

  14. 14

    Does the platform handle disputes and chargebacks at the marketplace level?

    Disputes route through the unified dispute queue; the marketplace decides whether to push the dispute to the seller, absorb it, or split the loss per the marketplace's terms. Chargeback reversals to the buyer can be netted against the seller's payouts or held-funds balance per the marketplace's rules.

  15. 15

    What about refunds when the marketplace already paid out to the seller?

    Refunds against a payout already disbursed clawback from the seller's next payout cycle, or directly from their held-funds balance if available. The clawback event is logged with actor, reason and timestamp; the marketplace can also override the clawback and absorb the refund itself per its terms with the seller.

Related

Related on the topropay platform