Skip to content

Build

How to Build a Payment Gateway for a Marketplace

A marketplace payment looks simple to the buyer: one cart, one card, one confirmation. Behind it, the money has to reach several sellers, minus the marketplace's fee, at the right time and in the right currency, with a clear answer to who pays when an order is refunded or disputed.

That's what a payment gateway for a marketplace has to handle on top of an ordinary gateway. This page covers the flows marketplaces need, the regulatory question every marketplace meets early, the build steps and what to look for in marketplace payment software.

The flows a marketplace payment system needs

Ordinary merchant payments have one payer and one payee. Marketplaces have one payer and several payees, and that changes almost every flow.

Flow What it means for a marketplace
Split payments One order is divided among several sellers and the marketplace fee
Delayed payouts Seller funds wait until delivery or a return window ends
Seller onboarding Each seller is verified before it can receive money
Refunds The refund comes back from the right seller, sometimes after payout
Chargebacks The dispute lands on the marketplace, which recovers it from the seller
Multi-currency payouts Sellers in different countries get paid in their own currency
Reserves New sellers settle behind a holdback until they build a record

Refunds and chargebacks after payout are the hardest cases. A marketplace that has already paid the seller needs reserves or a recovery process, or the loss stays with it.

The regulatory question every marketplace meets

A marketplace that collects buyers' money and passes it on to sellers is moving other people's funds. In many countries that's a regulated payment service, and the marketplace either needs a license or has to structure payments so a licensed party holds the funds.

In the EU, the payment services rules exclude some commercial agents acting for one side of a sale, but a marketplace acting for both buyers and sellers usually can't rely on that. Check the rules with a lawyer in each country before choosing a model.

The common routes are a license of your own, a payment facilitator registration under a sponsor acquirer, or a licensed partner that holds the funds while your software runs the flows.

How to build a payment gateway for a marketplace, step by step

The order below keeps regulation ahead of code, because the model you can legally run decides what the software must do.

  1. Map the money flow: who pays, who holds funds, when sellers are paid and how refunds come back.
  2. Settle the regulatory model in each country, from license to partner.
  3. Pick acquirers or a partner that supports split payments and payouts in your markets.
  4. Build or license seller onboarding with KYB and KYC checks through an API.
  5. Build the split, hold and payout logic, with reserves for new sellers.
  6. Design refund and chargeback handling, including recovery from sellers after payout.
  7. Add reporting for sellers and for your finance team, with every split traceable.

Steps 5 and 6 carry most of the marketplace-specific work. They're also the part where a ready platform saves the most time.

How much a marketplace payment build costs

Building the payment layer yourself means building a gateway and a marketplace-specific back office. On public US wage data, even a one-year build by a small team is a seven-figure project before licenses and acquirer fees.

For many marketplaces, payments are a means, not the product. The build cost usually only makes sense when the marketplace operates at very large volume or sells its payment platform to others.

Best payment gateway software for marketplace platforms: what to check

Marketplace platforms differ from ordinary gateways in a few specific features. Test each one on a demo with a sample order split between two sellers.

  • splitting one payment among several sellers and the marketplace fee
  • holding seller funds and releasing them on a trigger, such as delivery
  • seller onboarding through an API, inside the marketplace's own sign-up flow
  • refunds and chargebacks traced back to the right seller after payout
  • payouts in sellers' own currencies, with fees shown line by line

The fourth item separates serious marketplace platforms from the rest. Ask to see a refund on an order whose seller has already been paid.

Marketplace payments on our platform

Our gateway supports split payments and payouts across several sellers and providers. Seller onboarding, risk scoring, monitoring and settlements run in the merchant management system and are available through the API, and settlements can apply fees, rolling reserves and holdbacks per seller.

The checkout and the seller dashboard carry your brand. We provide the software and don't hold funds, so the money moves under your license or your partner's.

Questions

How much money do I need to build my own payment gateway for a marketplace?

Budget for the team first. At US median wages with benefits, seven engineers cost about $1.3 million a year, before licenses, acquirer fees and compliance. Licensing the payment layer replaces that with a vendor's fees.

Does a marketplace need a payment license?

Often, if it collects buyers' money and pays it on to sellers. The alternatives are a payment facilitator setup under a sponsor acquirer or a licensed partner that holds the funds.

How do refunds work after a seller has been paid?

The marketplace recovers the amount from the seller, from a reserve or from the seller's next payout, depending on the rules it set. Payment software should trace every refund to the right seller automatically.

What is split payment in a marketplace?

One customer payment divided among several sellers and the marketplace's own fee, each share settled to the right party.

See marketplace flows on a live platform

Bring a sample order with two sellers, and we'll run it through splitting, holds and payouts on our platform.