Payments in Marketplaces: Escrow and Payouts Explained

By Brian Tr · Updated Oct 6, 2026

A normal online store takes money from a customer and keeps it. A marketplace takes money from a customer and, a little later, gives most of it to someone else. That one difference, money that passes through the platform on its way to a seller, creates almost every payments problem a marketplace has. Who holds the money? For how long? Who pays when the buyer asks for a refund after the seller has already been paid? And does moving other people's money mean the platform needs a license?

This article is a reference on how that flow works. It covers the pieces of a marketplace payment, the three common ways to build it, what escrow actually means, how real platforms time their payouts, who bears refunds and disputes, and the regulatory questions to bring to a lawyer. Everything here is general information from primary sources. It is not legal advice, and payment policies change often, so check each platform's current page before relying on a detail.

We won't cover checkout design, payment method mix or card-decline recovery. That is the single-merchant side, and it's in payment processing strategy. We're also leaving take rate to its own article. In one sentence: the percentage a marketplace keeps from each transaction is covered in marketplace take rate, and payments is the machinery that collects it.

The money flow in a marketplace transaction

Strip away the vendor names and a marketplace payment has five stages.

1. Pay-in. The buyer pays, by card, wallet or bank transfer. Money leaves the buyer and lands somewhere controlled by the platform or its payment provider.
2. Hold. The funds sit for some period. It might be seconds, or it might be until a service is delivered.
3. Split. The platform decides how the amount divides: the seller's share, the platform's fee, taxes, sometimes a third party such as a delivery courier.
4. Payout. The seller's share moves to their bank account, card or wallet, on a schedule.
5. Reversal. If there's a refund or a dispute, some of that money has to move backward.

Every design choice in marketplace payments is a choice about the order and timing of those stages. Pay out immediately and sellers are happy, but you bear the risk if the buyer disputes. Hold funds longer and buyers are protected, but sellers wait, and a long wait can push good sellers to other platforms. Our seller onboarding article covers how sellers are brought on; payments is where that onboarding either holds up or breaks.

Three ways to build the flow

Most marketplaces don't move money themselves. They sit on top of a payments provider. The provider documentation describes the options, and they differ mainly in who is the business of record, whose balance takes the loss, and how much the platform has to build.

Model 1: Direct charges (seller as the merchant)

The charge is created on the seller's own account. Stripe's Connect documentation describes this as payments made directly to a connected account, where the customer is often unaware of the platform, and says refunds and chargebacks reduce the connected account's balance. The platform earns by taking an application fee. Stripe positions this for software platforms such as storefront builders, not for branded marketplaces.

Model 2: Destination charges (platform as the front)

The charge is created on the platform, and part of it transfers to the seller's account. Per Stripe's documentation on Connect charges, this is best suited to marketplaces such as home rental or ride-hailing. The payment appears in the platform's balance, the part that stays is the platform's fee, and refunds and chargebacks reduce the platform's balance. In short, the buyer is dealing with the platform, so the platform carries the money risk.

Model 3: Separate charges and transfers (platform holds, then routes)

The platform charges the buyer first and moves money to sellers later, as a separate step. The same Stripe page says this suits cases where a payment must be split across several parties, where the seller isn't known at the time of the charge, or where funds need to be held before transfer. It gives a delivery order split between the store and the courier, and a cleaning job paid before a cleaner is assigned. The platform's balance is debited for fees, refunds and chargebacks, and the platform has to watch that balance when transfers can exceed incoming payments.

Other providers describe similar structures in their own terms. Adyen's documentation for its marketplace model says the platform can accept payments on behalf of its users, hold funds until payout, and have Adyen verify sellers before paying them out, with the platform's brand known to customers. PayPal's multiparty documentation describes a delayed disbursement option for holding funds from a buyer before disbursing to a seller, to give the platform time for additional vetting. Its docs say funds disburse automatically after 28 days and that the integration requires being an approved partner. For the Adyen design, see Adyen's marketplace documentation; for the PayPal one, see PayPal's delay disbursement guide.

One more concept belongs here: merchant of record. It means the business named on the transaction, the one the buyer's card statement and the card networks treat as the seller. Stripe's on_behalf_of option, for instance, makes the connected account the business of record for a payment, which changes the statement descriptor, the settlement country and the fee structure. Who is merchant of record affects who answers a chargeback and what the buyer sees on their statement, so decide it on purpose, not by default.

Seller accounts and KYC

A seller who gets paid out needs a verified identity. Providers split this work differently. In Stripe's legacy account types, Standard and Express accounts have Stripe do onboarding and identity collection, while Custom accounts leave it to the platform or Stripe. Stripe also notes that your choice of account type determines the platform's liability for fraud, abuse, negative balances and identity verification. Read the detail on Stripe's connected account types, and note that the page marks these as legacy types, with newer account configurations replacing them for new platforms.

For a marketplace, the key point is that identity checks, known as KYC for individuals and KYB for businesses, are a payments requirement as well as a trust measure. The provider usually needs them before it will release funds to the seller. A seller who can't finish verification can list items but can't be paid, which is a conversion problem inside your onboarding flow. That's why we treat it in seller onboarding and not only here.

Escrow and held funds

"Escrow" gets used loosely. In marketplace practice it means the platform or its provider holds the buyer's money in a neutral position until a condition is met, then releases it. The condition varies by marketplace:

• Delivery or check-in. Money releases a set time after a stay begins or goods arrive.
• Milestone approval. Money releases when the buyer accepts a deliverable.
• Time-out. Money releases automatically if the buyer doesn't object within a review window.

Upwork shows the milestone version clearly. Its help page on fixed-price payment protection says project funds, formerly called escrow, are deposited by the client before work begins and act as a neutral holding place. Clients release payment when they approve the work or after the review period ends, and the page says submitting work through the designated button starts a 14-day countdown for automatic payment. It also states that if a milestone isn't funded in advance, Upwork can't help recover payment later. Hourly work is protected differently: according to Upwork's hourly protection page, freelancers must log time with the tracker, with related activity and memos, among other conditions.

The pattern worth copying is that release is tied to evidence the platform can see: a funded milestone, a submitted deliverable, a tracked hour.

A caution on the word itself. Calling a held balance "escrow" may suggest a legal arrangement, such as a third-party escrow agent or segregated account, that your setup doesn't have. Upwork's own page now says "project funds." How the funds are held, and by whom, is a question for your provider and counsel.

Payout timing on real platforms

Payout timing is a product decision, not just a back-office setting. These examples come from each platform's own help pages.

Three platforms, three clocks: a stay milestone, a calendar the seller picks, and buyer approval.

At the provider level, defaults can be changed. Stripe's page on payouts to connected accounts says charges made for a connected account accumulate in its balance and are paid out on a daily rolling basis by default, and that a platform can schedule automatic payouts, make manual payouts, or retain funds in its platform balance for destination charges and separate charges and transfers. The default is a starting point. The schedule you actually set is your payments policy.

Airbnb's note about review is the useful part for builders. The page says transactions may be reviewed before they're sent, for example to prevent fraud, and that funds can be delayed or paused. Newer or riskier sellers waiting longer is a normal pattern. A good policy says so in writing, in advance, so a delay never reads as a surprise.

Refunds and disputes: who pays

The most important question to settle early is what happens when money has to go back.

Refunds and chargebacks follow the model you picked. In Stripe's description, under direct charges, refunds and chargebacks come out of the connected account's balance. Under destination charges and separate charges and transfers, the platform's balance is debited, and the platform can try to recover funds from the seller by reversing the transfer. Stripe's page adds that if you use Express or Custom legacy accounts, the platform is responsible for disputes and fraud.

Two practical consequences follow.

• If you pay sellers fast, you are lending them the buyer's money. When a dispute lands after payout and the seller's balance is empty, the platform absorbs the loss. Holding funds longer, or keeping a reserve, is how platforms reduce that exposure.
• The refund policy has to match the payout policy. A 30-day return window is hard to honor if sellers are paid on day two and have no balance to refund from. Decide the two together.

Seller protection and buyer protection rules also decide who wins a disputed case. PayPal's page tells platforms to inform sellers of its seller protection policy so they know the cases that invalidate it, such as shipping to an address other than the one in the transaction confirmation. Publish whatever rules you set in plain terms.

Payments as a revenue line

A platform that processes the payment may also earn a processing margin on top of its commission. We're not covering rates or provider pricing here. For how this sits alongside the commission, see marketplace revenue models. For optional paid services built on top of the transaction, see value-added services.

Regulation: where moving money gets legal

This section describes what a few primary texts say, not how they apply to your business. Whether your flow of funds is regulated depends on facts and jurisdiction. Get advice from a lawyer who handles payments before you launch, or before you move away from a provider's standard setup.

United States

Federal rules define a money transmitter. The text of 31 CFR 1010.100 says "money transmission services" means accepting currency, funds or other value that substitutes for currency from one person and transmitting it to another location or person by any means. It adds that whether a person is a money transmitter is a matter of facts and circumstances, and carves out, among others, a person that only acts as a payment processor to facilitate the purchase of a good or service through a clearance and settlement system by agreement with the creditor or seller. FinCEN's own MSB definition page lists money transmitter among the categories of money services business. A marketplace that receives a buyer's funds and sends them on to a seller is the kind of arrangement those facts are applied to, so ask counsel how your own flow is characterized. State money transmitter licensing is a separate layer that varies by state, and we haven't sourced it here, so raise it with counsel.

European Union

Under the second Payment Services Directive, there's an exclusion for payments through a commercial agent. Article 3(b) of Directive (EU) 2015/2366 excludes payment transactions from the payer to the payee through a commercial agent authorised via an agreement to negotiate or conclude the sale or purchase of goods or services on behalf of only the payer or only the payee. The same text's recital 11 says some Member States had let e-commerce platforms acting for both buyers and sellers use the exclusion without a real margin to negotiate or conclude the sale, and calls that beyond the intended scope. The key phrase is "only the payer or only the payee." A platform acting for both sides is the situation the recital addresses.

Singapore and Malaysia

Singapore's Payment Services Act 2019 is, in the Monetary Authority of Singapore's words, a framework for regulating payment systems and payment service providers, and its statute text on Singapore Statutes Online has a licensing part and defines services such as account issuance and merchant acquisition by reference to its First Schedule. MAS's Payment Services Act page lists money-changing, standard payment institution and major payment institution licences. Whether a given marketplace flow is a regulated service is for the licensing guidelines and counsel to answer.

In Malaysia, Bank Negara Malaysia's legal framework page says a person wishing to offer merchant acquiring services must be registered with the bank, and that issuers of designated payment instruments must obtain approval.

The common thread across all four: the text turns on what the platform does with the money, not on what the platform calls itself.

A short decision checklist

These are reasoning, not data.

1. Decide who the buyer is dealing with. That drives merchant of record and who bears disputes.
2. Pick the hold rule before the payout rule. What event releases the money, and what's the longest wait?
3. Match refund policy to payout timing. Avoid paying out faster than you can reverse.
4. Put verification before payout, not after. Collect KYC and KYB at onboarding so the first sale can actually be paid.
5. Publish the schedule and the review rules. Sellers accept a delay they knew about.
6. Take legal advice on structure before launch. Using a provider helps, but it doesn't remove your own obligations.

If your operation matches buyers and sellers by hand and controls the payment end to end, a managed marketplace changes the risk picture, since the operator is closer to the transaction. For the wider model, see what is a marketplace business.

Key Facts: Marketplace Payments

• Stripe's Connect documentation says that with destination charges, refunds and chargebacks reduce the platform's balance, while with direct charges they reduce the connected account's balance.
• Stripe says charges for a connected account accumulate in its balance and are paid out daily on a rolling basis by default, and that platforms can change the schedule.
• PayPal's delayed disbursement for marketplaces lets a platform hold funds from a buyer before disbursing to a seller, with automatic release after 28 days.
• Airbnb's help page says that for most home stays of 27 nights or less, the payout is initiated by the end of the business day after scheduled check-in, and that reviews can delay funds up to 45 days after check-in.
• Upwork's fixed-price protection uses project funds, formerly escrow, deposited before work begins, with automatic payment 14 days after work is submitted.
• The EU's PSD2 Article 3(b) excludes commercial agents acting for only the payer or only the payee.

Related Reading

• Marketplace Take Rate
• Marketplace Revenue Models
• Value-Added Services in Marketplaces
• Seller Onboarding for Marketplaces
• Managed Marketplace
• What Is a Marketplace Business?
• Payment Processing Strategy