A marketplace does not need an ordinary checkout alone. It must accept a buyer’s payment, identify the seller, calculate the platform fee, handle refunds and disputes, and pay the right party at the right time. That combination makes the payment architecture a product decision, not a plugin choice.
Short answer: shortlist providers by the complete money flow. A low headline fee is irrelevant if seller onboarding fails, payouts cannot be reconciled or the provider does not support your countries and business model.
What a marketplace payment stack must do
- onboard and verify sellers with the required KYC or KYB checks;
- accept the buyer’s payment in the right currencies and methods;
- split the amount between seller proceeds, platform commission and fees;
- schedule payouts, including reserves or delayed settlement when needed;
- support refunds, partial refunds, cancellations and chargeback evidence;
- provide a ledger and reports that finance can reconcile with orders.
If the platform receives and controls funds for other parties, the regulatory analysis can change by country. Use a licensed provider’s marketplace product where it fits, and obtain legal advice for the proposed flow.
Provider models to compare
| Model | How money moves | Typical fit | Main question |
|---|---|---|---|
| Platform collects first | Buyer pays the platform, then the platform pays sellers | Simple early prototype with limited markets | Does the platform need a licence or safeguarding structure? |
| Provider split settlement | Licensed provider divides funds between connected parties | Most multi-vendor marketplaces | Can it support seller countries, refunds and reserves? |
| Direct seller payments | Buyer pays each seller; platform invoices its commission | Platforms that do not need to control the checkout | Can the user experience and reporting remain coherent? |
How to compare marketplace gateways
- Seller coverage. List seller countries, entity types, currencies and payout destinations before contacting providers.
- Onboarding. Check hosted versus embedded onboarding, verification time, rejected sellers, beneficial-owner checks and the data your platform must store.
- Settlement. Confirm destination charges, separate charges, split rules, reserves, payout timing and negative balances.
- Risk operations. Ask who handles fraud tools, disputes, chargebacks, refunds and evidence collection.
- Reconciliation. Request sample reports and map payment IDs to orders, commissions, refunds and seller balances.
- Integration. Check webhooks, idempotency, sandbox coverage, API limits and how account status changes are delivered.
- Commercial terms. Compare transaction fees, payout fees, currency conversion, reserves, minimums and support—not only the card rate.
Questions to ask before choosing a provider
- Can one buyer order from multiple sellers in one checkout?
- Can the provider delay or split a payout after delivery or a return window?
- Who is responsible for the seller relationship and chargeback evidence?
- Can the platform collect a commission without manually moving funds?
- What happens when a seller fails verification after an order is placed?
- Can finance export a seller-level ledger and reconcile it with the CRM or ERP?
A practical pilot plan
Do not start by integrating ten providers. Choose one or two candidates and run a narrow pilot with a test buyer, two seller accounts, a refund, a failed payment, a delayed payout and a simulated dispute. Measure how much manual work remains after the API succeeds.
The pilot should also test the non-technical experience: seller emails, compliance questions, support escalation and the explanation shown when a payout is delayed. Those details often decide whether a marketplace can scale.
Frequently asked questions
Does every marketplace need its own payment licence?
Not necessarily. The answer depends on the flow, countries, contracts and provider model. A licensed provider’s marketplace product may reduce the need for the platform to handle regulated payment activity, but it does not remove the need for a proper legal and compliance analysis.
Are split payments the same as escrow?
No. Split payments allocate a transaction between parties. Escrow or delayed settlement adds rules about when funds are held and released. Confirm the exact product and legal treatment with the provider.
Which is more important: price or approval rate?
For a growing marketplace, successful seller onboarding, payment approval, reliable payouts and clean reconciliation usually matter more than a small difference in the published transaction fee.
CrystalCore designs marketplace payment flows, selects PSPs and integrates seller onboarding and payouts. See our marketplace development service, payment gateway service and the related guide on marketplace split payments.