Marketplaces · Payments

Money flows shape a marketplace more than founders expect. Here is how split payments work and what to decide early.

If you are building a marketplace, the product idea is only half the challenge. The other half is money: how a buyer pays, how your platform takes its fee, how the seller gets the rest and what happens when something goes wrong. Founders often leave this to the end, and then discover that payments shape the whole design.

This guide explains the main ways marketplace payments work, the decisions you must make and the pitfalls, in plain language. It is general information, not financial or legal advice.

The basic flow

  1. A buyer pays for an order, booking or service.
  2. The payment is held, split or routed.
  3. Your platform takes a commission or fee.
  4. The seller receives the remainder, on a schedule.
  5. If there is a refund or dispute, the money moves back.

Three common models

ModelHow it worksConsiderations
Direct to sellerBuyer pays the seller, and you charge sellers separately, for example a subscription or listing feeSimple, but you lose visibility into transactions and have little control over the experience
Split payment through a payment providerThe buyer pays once, and the provider splits the funds between seller and platformThe usual route. The provider handles much of the regulatory complexity
Platform holds the fundsYou collect everything and pay sellers yourselfOften creates regulatory obligations, so seek advice before attempting this
Be careful about holding other people’s money. In many jurisdictions, taking and holding funds on behalf of others can require authorisation or licences. Most marketplaces avoid this by using a payment provider’s marketplace product, which is designed for the purpose.

Decisions to make

  • Fees: commission percentage, fixed fees or both, and who pays them.
  • Seller onboarding: the provider usually verifies sellers’ identity and bank details, which takes time and must be part of the sign-up flow.
  • Payout timing: immediately, after delivery or on a schedule.
  • Refunds and disputes: who decides, how quickly and who bears the cost.
  • Cancellation rules: especially for bookings and services.
  • Taxes and invoicing: who is responsible for what varies by country, so take advice.
  • Currencies and countries: not all providers support all countries for buyers or sellers.

Check provider support early

Payment providers differ in the countries, currencies and business types they support. Before you design the product, confirm that your chosen provider supports both your buyers and your sellers where they actually are. Discovering a gap after the build is expensive.

Build trust into the flow

  • Show clearly what the buyer pays and what the seller receives.
  • Confirm every payment and payout by email.
  • Give sellers a dashboard of earnings and payout status.
  • Make dispute and refund rules visible before people buy.
  • Keep a full record of every transaction for support and accounting.

Start simple

A first version often works with a straightforward split-payment setup, a small number of sellers and manual handling of the occasional dispute. Add automation as you learn how people actually use the marketplace. See how to validate before you build and what to cut before you build.

Cost and first step

Builds start at $3,500, with the final quote based on the scope in your PRD, and typical launches take 2 to 6 weeks. The best first step is a Discovery Sprint: a $345 plan covering scope, user flows, architecture and cost, delivered within 24 hours and credited toward the build. See our cost guide for what moves the price. Payment provider fees are separate and depend on the provider and your volume.

Frequently asked questions

Can a Bubble.io app run a marketplace?

Yes, many marketplaces are built this way. The payment provider’s marketplace features handle splitting and payouts, while the app handles the rest.

How do sellers get paid?

Usually through payouts from the provider to their bank accounts, on a schedule you choose within the provider’s rules.

What about refunds?

Design clear rules and make sure the system can reverse or adjust payments cleanly.

Do I need legal advice?

For anything involving money, yes. Take advice on regulation and tax in the countries you operate in.

Planning a marketplace?

Email us what is being bought and sold and where your buyers and sellers are. We will help you scope the product and the payment flow.

Email info@sasolutionspk.com

Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions

Simple Automation Solutions

Business Process Automation, Technology Consulting for Businesses, IT Solutions for Digital Transformation and Enterprise System Modernization, Web Applications Development, Mobile Applications Development, MVP Development