Split payments. Pay sellers. Stay in control.
Two-sided marketplaces have to clear money between buyer, platform, and seller — sometimes in different currencies, sometimes with funds on hold, always with a clean audit trail. Paytone gives that flow a first-class home.
Three things a single PSP rarely handles well.
Marketplaces don't just process payments — they hold money, split it, and move it back out. Most off-the-shelf payment stacks were not designed for that.
Multi-party flow
A single transaction touches the buyer, the platform fee, the seller, sometimes a tax authority, sometimes a third-party logistics partner. Each leg has its own timing, its own currency, and its own failure mode.
Hold and release
Funds often need to sit on the platform until delivery, completion, or a dispute window passes. That requires either operating your own ledger or routing through a provider that exposes hold accounts as a primitive.
Compliance weight
The moment you hold and route third-party funds, your regulatory profile changes. KYC on sellers, AML on flows, and clear segregation of platform fees from seller balances become non-negotiable.
Marketplace primitives, not a workaround.
Each capability is exposed as a clean API surface — not a feature flag bolted onto a single-merchant PSP.
Split payments
Define the buyer charge once, then split the captured amount across platform fee, seller, and any partner shares at capture time.
Multi-party flows
Model buyer, platform, seller, and partner as distinct accounts with their own balances, payouts, and reporting.
Seller payouts
Schedule, on-demand, or rolling payouts to bank, card, or wallet — domestic and cross-border, with per-seller currency preferences.
Escrow patterns
Hold funds against delivery, milestone, or dispute windows. Release manually, programmatically, or on schedule.
KYC for sellers
Onboarding flows for individual and business sellers, with document capture, verification, and ongoing monitoring hooks.
Dispute handling
A unified workflow for chargebacks, refunds, and platform-side disputes — with evidence collection and seller communication built in.
A complete marketplace flow, end to end.
From the buyer charge to the seller payout, every step is a first-class object in the API — with consistent IDs, webhooks, and reporting attached.
You can adopt only what you need today. Many platforms start with split payments and add escrow or KYC as they mature into a regulated marketplace operator.
- Payment in
- Cards, wallets, bank transfers, and local APMs collected from the buyer with full 3-D Secure 2 support.
- Hold & escrow
- Funds parked in segregated platform accounts with configurable release windows and triggers.
- Fees
- Platform fees captured atomically with the buyer charge or computed on split — flat, percentage, or hybrid.
- Payout
- Scheduled, instant, or on-demand transfers to seller bank, card, or wallet in domestic or cross-border currencies.
- Refunds
- Full or partial refunds with automatic reversal of platform fee and seller share — or platform-absorbed at your choice.
- Dispute
- Chargeback evidence packs, seller notification, and configurable liability allocation between platform and seller.
Methods that fit marketplace flows.
A short list that covers most marketplace volume — both the inbound charge and the outbound payout.
Card payments
The default rail for buyer charges, with tokenization and chargeback workflows ready for split flows.
ExplorePayouts
Send seller balances to bank, card, or wallet across borders — with the same control plane that handles your inbound.
ExploreBank transfers
Lower-cost rails for high-ticket marketplace categories where card fees compress seller margins.
ExploreLocal APMs
The methods locals expect when they buy or get paid — Pix in Brazil, iDEAL in NL, OXXO in Mexico, and dozens more.
ExploreRun your marketplace flow on real primitives.
Tell us how your buyer-seller-platform money flow works today, and we'll come back with a target architecture that simplifies it without compromising on compliance.