The payment reality of marketplaces
A marketplace runs two payment operations that have to work together: collecting from many buyers across markets and methods, and paying out to many sellers, each with their own market, currency and payout preference. Split settlement — the buyer pays one amount, the platform keeps a share, the seller receives the rest — has to happen correctly on every single transaction. Getting it right in aggregate, at the end of the month, isn't enough.
Seller onboarding adds friction most marketplaces underestimate: every seller needs to be payable before they can transact, across whatever market they're in. And refunds touch both sides at once — reversing a buyer's payment usually means reversing or adjusting what a seller was paid, which is harder to get right the more the two sides are handled by different systems that don't talk to each other.
Buyers don't care that your seller payouts run on a different system. They just want their refund.
How CyberPay helps
Four capabilities, built around the two-sided problem every marketplace runs into: collecting from buyers everywhere, paying out to sellers everywhere, and keeping both reconciled as the platform scales. Each capability addresses a specific point where buyer collection and seller payout usually drift apart on separate systems as a marketplace scales.
Collect in local methods per market
Buyers pay using the methods their own market prefers, rather than a single global default that leaves some buyers unable to check out at all.
Mass payouts to sellers worldwide
Sellers are paid out on a schedule or on demand, across a wide range of markets and methods, without processing each payout as an individual manual transaction.
Refunds and transaction queries on the same integration
Refunds and Query-Transactions run on the same platform used to collect and pay out, so a refund that touches both a buyer and a seller is handled as one event, not two separate ones.
Unified reconciliation of both sides
Buyer collection and seller payout reconcile together, so split settlement is visible per transaction rather than inferred from two reports that rarely line up.
Methods and markets
A marketplace needs buyer-side acceptance and seller-side payout to work together, market by market:
- Cards, Apple Pay, Google Pay and local methods — for buyer payments, by market.
- Mass seller payouts — scheduled or on demand, across markets and methods.
- Split settlement and refunds — handled on the same integration as collection.
- Local-currency payouts — sellers paid in their own currency where supported.
CyberPay covers 73 markets across 6 regions — see the full coverage map.
Buyer collection and seller payout reconcile together, whichever markets either side sits in, so the platform's own take is visible transaction by transaction rather than reconstructed at month end.
Integration
A marketplace can collect from buyers through the Hosted Cashier, or the Direct API to keep checkout on its own pages. Buyer pay-ins and seller payouts run on the same integration, with Refunds and Query-Transactions keeping both sides reconciled. Build against the sandbox before moving sellers to live payouts.
Use cases
Three ways marketplaces use CyberPay to keep buyer collection and seller payout reconciled on one platform instead of two disconnected systems. Each marketplace type splits and pays differently, but all three need buyer collection and seller payout to reconcile as one system.
A goods marketplace paying sellers
A marketplace selling physical or digital goods from many sellers collects from buyers in local methods and pays sellers out on a schedule, with split settlement visible on every transaction rather than calculated after the fact.
A services marketplace paying providers
A marketplace connecting buyers with service providers collects payment upfront or on completion and pays providers out in their own market and currency, reconciled against the original booking.
A rental or booking marketplace
A marketplace booking rentals or reservations collects from guests and pays hosts or operators out after the stay or booking completes, with refunds for cancellations handled on both sides at once.
Frequently asked questions
What payment methods do you support for marketplace buyers?
Cards, Apple Pay, Google Pay and local methods by market, so buyers aren't limited to a single global default. Method coverage is added market by market as your buyer base grows, rather than fixed at a single global default.
How do seller payouts work?
Sellers are paid out on a schedule or on demand, across the methods and markets they're in, on the same platform used to collect from buyers.
How is split settlement handled?
Each transaction's split between platform and seller is calculated and reconciled at the transaction level, not inferred from separate collection and payout reports. That calculation runs the same way whether the platform takes a flat fee or a variable commission.
What happens with refunds?
Refunds run on the same integration as collection and payout, so a refund that affects both a buyer and a seller is handled as one event.
What does seller onboarding involve?
Talk to us about your seller base and markets — payout routes are set up so sellers are payable as soon as they're onboarded.
Ready to pay buyers in and sellers out?
One integration for buyer collection, seller payouts and split settlement, reconciled together.