Split every marketplace payment between your platform and its vendors

Collect your platform fee from every marketplace sale, while Wallet Marketplace has the payment processor pay the rest to the vendor. Wallet also onboards each vendor, schedules their payouts, and can have the processor hold a vendor's share until delivery.

Get early accessView all products

Split payments for two-sided platforms

A two-sided platform needs a payment flow in which a buyer pays, the platform keeps its fee, and the vendor receives the rest. Wallet Marketplace provides that flow. During onboarding, each vendor provides their identity documents and payout details. The payment processor can then hold a vendor's share until the buyer confirms delivery, after which the vendor receives it on the payout schedule that you set. Your team sets up the fee, the holds, and the payouts from the Wallet dashboard, so your developers write no payment code.

Split every marketplace sale between your platform and the vendor

Your team sets the platform fee and verifies each vendor, after which Wallet splits every purchase. The processor holds each vendor's share until delivery and then pays it on the vendor's payout schedule.

Fees, onboarding, holds, payouts, and disputes

Configurable platform fee splits

Your marketplace can charge a flat percentage, a percentage plus a fixed fee, or a fee that changes by category, vendor tier, or sale size. If your developers hardcode one fee model, they will have to rebuild it whenever your business changes how it charges.

You can set your platform fee as a percentage, a fixed amount, or both, with different rates by product category, vendor tier, or transaction type. When a buyer pays $100 and your platform fee is 15%, the processor pays $85 to the vendor and $15 to your platform. Wallet calculates the split before the charge, so the processor settles both shares in one transaction.

Vendor onboarding and verification illustration

Vendor onboarding and verification

Before you pay out to a vendor, you will need their identity verification, their tax information, and the details of their payout account. If your team collects those by email, a typo or a missing document can slip into your compliance records. A vendor who struggles to sign up may also choose another platform.

Send each vendor a guided onboarding flow that asks for their business details, identity verification, tax identification number, and payout account. Wallet adjusts the flow to the vendor's jurisdiction, so a vendor in Ghana sees different requirements from a vendor in the US. The vendor dashboard shows the verification status of each vendor, so your team knows who is approved, pending, or blocked.

Delivery-based payout holds

If the processor pays the vendor as soon as the buyer pays, the vendor has the money before the buyer has the product. A hold with no end date, however, can keep a vendor waiting for money that they earn. The right length of hold will depend on the product, how far you trust the vendor, and how long delivery takes.

Wallet Marketplace can have the payment processor hold the vendor's share of a sale until the condition that you choose for its release: the buyer confirms delivery, a set period ends, or your team approves the sale after a review. You can set a different hold for each marketplace category, so a category that needs more buyer protection can have a longer hold than the rest.

Scheduled vendor payouts

Your vendors will want to know when the processor pays them. A food delivery app may pay restaurants daily, while a services marketplace pays its providers monthly. If your developers build payout schedules for each vendor or category themselves, they will have to write that payout system from scratch.

You set a daily, weekly, biweekly, or monthly payout schedule for each vendor, each category, or the whole marketplace, which Wallet passes to the processor that pays the vendors. Each vendor can see their next payout date, the amount pending, and the sales behind it. Every payout report lists the transactions that the payout includes, so that the vendor can reconcile it.

Dispute and refund handling illustration

Dispute and refund handling

A marketplace dispute involves the buyer, the vendor, and your platform. When you refund a buyer, you will also have to deduct that refund from the vendor's next payout. If your team tracks disputes in email threads and spreadsheets, someone can refund the buyer and forget to adjust that payout.

When a buyer disputes a sale, Wallet Marketplace sends the dispute to the vendor for a response and to your platform for review. For a full refund, the processor returns the buyer's payment and Wallet deducts it from the vendor's payout. For a partial refund, Wallet divides the adjustment between the platform fee and the vendor's share in the proportions that you set. Wallet records every action on a dispute in an audit trail.

What changes for your vendors and your team

Launch split payments from the dashboard

Your team configures fee splits, onboarding, holds, and payout schedules in the Wallet dashboard, so your engineers can spend their time on the marketplace itself.

Payouts that vendors can plan around

The vendor dashboard lists the date of each vendor's next payout and the sales that it covers, so vendors can answer their own questions about payment timing.

Buyer protection through delivery holds

When you require delivery confirmation, the processor holds the vendor's share until the buyer confirms it, so the processor pays the vendor only after the buyer has the order.

Every dispute in one workflow

Wallet keeps the buyer's complaint, the vendor's response, and your platform's decision in one dispute workflow and calculates how each refund changes the platform fee and the vendor's share.

Marketplaces that split each sale through Wallet

A craft marketplace pays 200 artisan vendors after each sale

An online craft marketplace takes a 15% platform fee on every sale. When a buyer pays $80 for a handmade item, Wallet Marketplace splits the payment, so the processor pays $12 to the platform and holds $68 for the vendor until the buyer confirms delivery. The vendor dashboard shows pending payouts, completed sales, and the next payout date.

Result

The marketplace splits every sale with its 200 vendors through Wallet, which deducts the 15% fee each time. Each artisan completes onboarding in one guided form, so the marketplace team stops exchanging emails to collect vendor details.

A home-services platform holds each booking until the job is done

A home-services platform connects cleaners, plumbers, and electricians with homeowners and takes 2,000 bookings a month, with a 20% fee on each. The processor holds the provider's share of each payment until the homeowner confirms that the job is complete. Service providers complete the verification flow for their own region when they join, then receive a weekly payout with a breakdown of each booking.

Result

Homeowners book knowing that the provider receives the money only after the job is done. The platform's finance team reconciles all 2,000 monthly bookings from the payout reports, so it stops matching each payment to a booking by hand.

A home-services platform holds each booking until the job is done

50 instructors share course revenue 70/30 with the platform

A course platform hosts 50 instructors. Each course has a set price, of which the platform keeps 30% while the instructor earns 70%. Students enroll and pay through the platform's checkout. Each month, the processor pays every instructor, while Wallet sends each one a breakdown of enrollments, refunds, and net earnings. When a student complains, Wallet sends the dispute to the instructor for a response before the platform decides on a refund.

Result

Wallet calculates every instructor's 70% share and payout, so the platform team stops reconciling instructor earnings by hand. The team follows the earnings of all 50 instructors across every course from one dashboard.

50 instructors share course revenue 70/30 with the platform

Every food order splits three ways between restaurant, driver, and platform

A food delivery app charges the customer the menu price plus a delivery fee. Wallet Marketplace splits each payment three ways, so the restaurant receives the menu price minus a 12% platform fee, the driver receives the delivery fee, and the platform keeps its 12%. Restaurants receive daily payouts, while drivers receive a payout after each batch of deliveries. When a customer cancels an order, Wallet deducts the refund from the restaurant, the driver, or both, depending on when the customer cancels.

Result

The app's operations team sets up the three-way split once, after which Wallet applies it to every order. Restaurants can check their daily revenue reports, while drivers see each batch payout as the processor sends it.

Every food order splits three ways between restaurant, driver, and platform

Explore more of Wallet

Billing

Wallet Billing invoices your clients and bills your subscribers on schedule, including retries for failed payments.

Learn more

Collections

Your team can build branded payment pages in Wallet Collections for school fees, donations, and event tickets.

Learn more

Tax

Wallet Tax applies each jurisdiction's rate to every charge and stores an audit record for your filing.

Learn more
View all Wallet features

Split each sale between your platform and its vendors

Set your platform fee, onboard vendors, and schedule payouts from Wallet Marketplace, while a regulated payment processor holds and pays out each vendor's share.

Get early accessView all products