Engagements - Marketplace app development: a two-sided platform with payouts, search, and disputes
A marketplace is two products welded together with a payments and trust layer in the middle, and that middle is where most marketplaces stall. Seller onboarding and verification, commission splits, holds until delivery, search that actually matches, and disputes between two strangers you now have to mediate in code. This is custom marketplace development as one outcome: a senior engineer takes on the whole two-sided system for a month or more, shipping weekly increments you review and merge, rather than handing you a shortlist of contractors and a scoping problem.
- Marketplace founders
- Two-sided platforms
- Seed-stage
What you'll have at launch
A working two-sided marketplace: vendor onboarding and payouts through Stripe Connect, buyer and seller flows, search and discovery that matches supply to demand, and a dispute path with an admin behind it.
- Seller onboarding that ends in a payable account: application, Stripe Connect identity verification, and the first listing published — with payouts blocked until verification clears.
- Stripe Connect wired for real: split payments, commission take-rate, holds until delivery, refunds, and payout schedules on your launch market's currency.
- Both sides working — a seller dashboard for listings, orders, and earnings, and a buyer flow for search, checkout, and order tracking.
- Search and discovery that ranks by relevance, price, and availability, with listing-quality rules that keep thin and duplicate listings out of the results.
- A dispute path with an admin behind it: buyer opens a case, seller responds, you resolve, and Stripe refunds or releases the held funds.
How we build it
A build runs 8–12 weeks typical, shipped week by week in increments you review and merge.
Weeks 1–2 · Marketplace model & seller onboarding
We model buyers, sellers, listings, orders, and money, then build seller onboarding on top: application, Stripe Connect account creation, identity and bank verification, and the states an unverified seller can and can't reach. Onboarding first, because a marketplace with no payable supply has nothing to sell.
Weeks 3–4 · Payments, commission & payouts
Split payments, commission and take-rate logic, holds until delivery, refunds, and payout schedules go in, exercised end to end in Stripe test mode with the failure cases: a declined charge after a hold, a refund on a paid-out order, a seller who never finishes verification. Payments are the part that's expensive to retrofit once real money moves.
Weeks 5–6 · Seller side & listing quality
The seller dashboard ships: listing creation with required fields and photos, inventory or availability, the order pipeline, earnings, and payout history. Listing quality rules — required attributes, duplicate detection, a moderation state before a listing goes public — get built here rather than bolted on after the catalog fills with junk.
Weeks 7–8 · Buyer side, search & discovery
Browse, search, filters and facets, relevance ranking, category and location pages, checkout, and order tracking. We tune ranking against your real listings during the build, since bad matching is what quietly kills marketplace conversion — buyers don't complain, they just leave.
Weeks 9–10 · Messaging, disputes & admin moderation
Two-party messaging with spam and abuse controls, the dispute and refund flow, and the internal admin console you run the market from: moderation queue, seller verification review, order lookup, manual refunds and releases, and account suspension.
Weeks 11–12 · Trust, launch & handoff
A trust-and-safety pass adds fraud flags, verified-seller badges, and a review system that resists gaming; then a launch pass on notifications, empty states, and seeded supply, a walkthrough of the Connect flows and admin tools, and it goes live in your repo and cloud account.
What's included
- Buyer and seller onboarding: sign-up, invite, seller application, Stripe Connect hosted identity and bank verification, and the gating that keeps unverified vendors out of checkout.
- Stripe Connect payments: split payments, commission and take-rate logic, escrow-style holds until delivery, refunds, payout schedules, and the webhook handling that keeps your database and Stripe agreeing.
- Seller dashboards — listing management, order pipeline, earnings, and payout history — plus the matching buyer-side search, checkout, and order tracking.
- Search and discovery: filters and facets, relevance ranking by price, distance, and availability, plus listing-quality rules — required attributes, duplicate detection, and a moderation state before publish.
- A dispute and refund flow: buyer opens a case, uploads evidence, seller responds, an admin resolves, and Stripe handles the refund or the release of held funds.
- Two-party messaging with abuse and spam controls, plus lifecycle notification emails — new order, message, payout sent, dispute opened — so deals don't go cold.
- An admin and trust-and-safety console: moderation queue, verification review, fraud flags, verified-seller badges, order lookup, manual refunds, suspensions, and a review system that resists gaming.
What a build like this looks like
Scopes we've shaped this engagement around. Yours is one of them, or close enough that week one settles it.
- Services marketplace with bookings and payouts. Providers list availability, buyers book and pay, and the money sits until the job is done. The build covers provider onboarding and verification, calendar and slot logic, the hold-and-release flow through Connect, and the dispute path for a job that didn't happen the way it was booked.
- Rental or equipment marketplace. Listings have dates, deposits, and condition disputes. This shapes the build around availability search, deposit holds and returns, late and damage handling, and the messaging thread that becomes evidence when the two sides disagree.
- B2B vendor marketplace with approvals. Your buyers are companies, so vendor onboarding needs review before a vendor goes live, orders need quotes or purchase approval, and invoicing sits alongside card checkout. The admin side carries more weight here than the consumer polish does.
- Marketplace MVP that has to reach first transactions. You need the smallest system that can take real money from a real buyer to a real seller. We cut breadth — one category, one country, one currency — and keep the full money and trust path intact, because that's the part you can't fake in front of your first hundred users.
Stack
- Next.js
- Express
- PostgreSQL
- Stripe Connect
How this build lowers your risk
- The money path is built and tested before the polish. Onboarding, splits, holds, refunds, and payouts go in during the first month and get exercised in Stripe test mode against the ugly cases — a refund after payout, a seller who abandons verification, a webhook that arrives twice. Retrofitting the payments layer under a live marketplace is the most expensive rework there is.
- Honest framing on what Stripe decides, not us. Verification requirements, payout timing, and the platform's exposure to chargebacks and negative seller balances are set by Stripe's terms and your account's risk profile, not by your code. We build to those rules, surface them in your admin, and tell you where they bite. We're not your compliance or licensing advisor, and we don't claim a partner badge we don't hold.
- Scope control you can see week by week. Every marketplace feature ships twice, once per side, so scope creep costs double here. Each week ends with a deployed increment on a live URL and a named next milestone, and we sequence by whichever side is blocking your launch — supply usually — so a feature that isn't landing gets redirected in week two, not on launch day.
- One senior engineer, flat monthly, no lump-sum quote. The person who wired your Connect flow in week two is the one fixing it in week ten, so context never resets on a hand-off. It runs on the flat monthly subscription, with multiple plans available — pay for the active weeks, reprioritize when supply and demand shift, pause between phases, and keep everything in your repo and cloud account as it's built.
Is this the right build for you?
A good fit when
- You're building a two-sided marketplace platform where money moves between buyers and sellers, and the payments and trust layer is the part that scares you.
- You want one senior engineer owning the whole marketplace for a month or more, shipping weekly increments, not a rotating pod or a contractor shortlist.
- You have a plan for supply — sellers you can recruit or already have — so the marketplace has something to match buyers against at launch.
- You'd rather launch one category in one country with the full money path working than five categories with payouts half-wired.
Not a fit when
- You want a marketplace live next week from a template. Sharetribe, Arcadier, or a WooCommerce multi-vendor plugin is cheaper and faster when your model fits what they already do — custom marketplace development pays off when it doesn't.
- You need native iOS and Android marketplace apps on day one. This build ships a responsive web platform with an API that a mobile app can sit on later; the native apps are their own engagement.
- You want a handful of small tickets or a single screen. A build is a month-plus engagement by design, not a fix shop.
- The hard part is logistics, warehousing, or field operations rather than software; the platform can't solve a supply problem it doesn't touch.
How it runs on the subscription
A marketplace ships every feature twice and lives or dies on its payments layer, so it runs as a build — the board dedicated to the platform, shipping onboarding, payouts, both sides, and search in weekly increments. We match the monthly plan to the workload, with most marketplaces landing in eight to twelve weeks. Founder-led, so the person who wired the Connect flow is the one fixing it later; reprioritize which side ships first whenever supply and demand shift. After launch the same subscription keeps handling the trust, fraud, and payout work a live marketplace generates.
Frequently asked questions
- Do you build the Stripe Connect payments and payouts?
- Yes — Connect is the anchor of this build. Seller onboarding and identity verification, split payments, commission and take-rate logic, escrow-style holds until delivery, refunds, payout schedules, and the webhook handling behind them are all core scope. It's built first because the payments layer is the most expensive part to retrofit once you have real money moving.
- How does seller onboarding and verification work?
- Sellers apply, then go through Stripe's hosted Connect onboarding for identity and bank details. Your platform holds the application state, gates what an unverified seller can do — usually draft listings but no checkout and no payouts — and shows your admin who's stuck and why. What documents Stripe asks for and how long verification takes are Stripe's rules and vary by country and business type; we build to them rather than promising around them.
- Can you build both the buyer and seller sides?
- Yes, both — that's what makes it marketplace app development rather than a single app. A marketplace ships every feature twice, so we sequence by whichever side is blocking your launch and build them out in weekly increments, letting you reprioritize as the balance of supply and demand shifts.
- Can you handle search, discovery, and listing quality?
- Yes. Search with filters and facets, relevance ranking by price, distance, and availability, and category or location browse pages are part of the build, and so are the listing-quality rules underneath them: required attributes, photo minimums, duplicate detection, and a moderation state before a listing goes public. We tune ranking against your real listings during the engagement, since bad matching is what quietly kills marketplace conversion.
- What about fraud, disputes, and moderation?
- The build includes a dispute and refund flow (case, evidence, seller response, admin resolution, then a Stripe refund or a release of held funds) plus the admin console behind it: a moderation queue, verification review, fraud flags, verified-seller badges, suspensions, and a review system that resists gaming. Trust work never fully ends, so the same subscription keeps handling it after launch.
- What's intentionally out of scope for a marketplace MVP?
- Native iOS and Android apps, multi-country and multi-currency payouts beyond your launch market, machine-learning fraud scoring and recommendation engines, promoted listings and ad inventory, shipping-label and logistics integrations, and full localisation. Each is real work that gets easier to specify once you've seen a few hundred real transactions, so they go on the board after launch rather than delaying it. The full money and trust path is never what we cut.
- Custom marketplace development or an off-the-shelf platform?
- If your model fits a template — standard listings, standard commission, standard checkout — Sharetribe, Arcadier, or a multi-vendor plugin will be live sooner and cost less, and we'll say so. Custom pays off when the matching logic, the money flow, or the trust rules are the product: staged payouts, unusual pricing, verification your category requires, or a data model those platforms can't bend to. That's the conversation week one settles.
- Who carries the risk on chargebacks and negative balances?
- On most Connect setups the platform does, which is why the build surfaces it: holds until delivery, refund rules that don't strand you after a payout, seller balance visibility, and admin controls to pause payouts on a suspicious account. The exact liability comes from your Stripe agreement and the account type you run, so we build the controls and you make the policy call with Stripe.
- How long does a marketplace take to build?
- Most land in eight to twelve weeks — longer than a single-sided product because you're building two sides plus the payments and trust layer between them. It runs on the flat monthly subscription, so you pay for the active weeks rather than a fixed project total, and can pause between phases.
Got a project? Let's ship it.
3 spots open. Tell us what you need shipped. We'll agree how the work will run and give each active item a clear target. Larger requests stay visible while smaller subtasks move toward done.