Marketplace seller payouts across borders: rails, timing and checks

A marketplace earns its fee on the sale but keeps its sellers on the payout. A seller in Almaty, Monterrey or São Paulo does not care how elegant the checkout is if the money arrives late, in the wrong currency or minus an unexplained deduction. Cross-border marketplaces add a layer on top: the buyer, the platform and the seller can be in three different countries, each with its own rails, currency and tax rules.

This article covers the design decisions behind seller payouts: how money moves from the buyer to the seller, how long to hold it, which rails to use, which currency to pay in, what tax reporting applies and how to deal with payouts that fail. Why payouts are harder than payments in general, and how to tier seller verification, are covered in why payouts are harder than payments and customer verification tiers and payouts. We link to them rather than repeat them.

How does money get from the buyer to the seller?

There are three basic models, and every later decision depends on which one you choose. Stripe’s Connect documentation is a useful reference because it names them clearly.

Model	How it works	Who carries refunds and disputes	Fits
Direct to seller	The payment is made to the seller’s account; the platform takes a fee	The seller	Software platforms where buyers deal with the seller
Split at payment	The platform takes the payment and passes the seller’s share on immediately	The platform, which recovers from the seller	One seller per order
Collect, then pay out	The platform takes the payment and pays sellers later, in separate transfers	The platform, which recovers from the seller	Multi-seller baskets, holds, unknown seller at payment time

Stripe describes its separate charges and transfers model as suited to cases where one payment is split between several parties, the charge is created before the seller is known, or funds must move before the payment completes. Adyen’s platform documentation shows the split model in practice: split instructions can be sent at authorization, at capture or with a refund, and any amount not assigned to a seller’s balance account is booked to the platform’s own account.

The model also decides who pays when a buyer asks for money back. Stripe’s documentation says that for destination charges and separate charges and transfers, refunds and chargebacks are debited from the platform, which then reverses the transfer to recover the amount from the seller. For destination charges, if the seller’s balance is too low, a refund that also tries to reverse the transfer returns an error instead of waiting. So the more you pay out early, the more you carry.

How long should a marketplace hold seller funds?

Long enough to cover the risks you actually carry, and no longer than your provider and your seller terms allow. Holds protect against non-delivery, returns and chargebacks. They also delay the money sellers are waiting for.

Providers set the outer limits. Stripe’s documentation on manual payouts says platforms must pay out held funds within 90 days in most countries, within 2 years for businesses in the United States and within 10 days in Thailand. For automatic payouts, Stripe lets a platform that owns fraud and dispute liability delay availability by up to 31 days. Stripe also notes that escrow has a precise legal meaning and that it does not provide escrow services, while still recommending delayed payouts when a delivery is late or a refund is likely.

Practical hold rules for a cross-border marketplace:

• Release on events, not only on dates. Confirmed delivery, the end of the return window or a completed service are better triggers than a fixed number of days.
• Hold longer for new sellers. A new account with no history carries more risk than a seller with a year of clean orders. A rolling reserve on a share of each payout is a softer alternative to a full hold.
• Write the hold into the seller terms. A seller who knows the rule complains less than one who discovers it.

Which rails can carry seller payouts?

Most cross-border marketplaces use a mix, chosen per seller country and seller type.

Rail	Examples	Strengths	Limits
Local bank transfer	SPEI in Mexico, Pix in Brazil	Cheap, final, familiar to business sellers	Needs correct account data in the seller’s name
Card payout	Visa Direct, Mastercard Send	Fast to individuals with only a card	Card and issuer must be eligible; provider coverage varies
Wallet	Local wallets and super apps	Reaches sellers without bank accounts	Wallet limits and verification levels

Local bank rails are the default where they are fast. Banco de México describes SPEI as a real-time settlement system it administers, operating since 13 August 2004 and available 24/7. Pix plays the same role in Brazil. For a seller, a payout to their own account on a domestic instant rail is usually the best experience available.

Card payouts suit individual sellers, creators and gig workers. Visa says Visa Direct reaches more than 18 billion eligible cards, accounts and digital wallets in more than 195 countries and territories and more than 150 currencies, with availability depending on the receiving institution. Eligibility is not universal: Checkout.com’s documentation says card schemes assign each business a code for its line of business, region and use case, which determines the payout types it can send, and that it offers card payouts only to businesses incorporated in the EEA, Singapore, the UAE, the UK or the US.

Wallets matter in markets such as Central Asia and parts of Africa, where many small sellers live in their wallet app. Treat each wallet as its own rail, with its own limits and checks.

Which currency should sellers be paid in?

The seller’s own currency, on a domestic rail, wherever possible. A Mexican seller paid in US dollars to a foreign account pays conversion and receiving fees the platform never sees, and blames the platform for the shortfall.

That is harder than it sounds outside the largest markets. Stripe’s documentation says its self-serve cross-border payouts let platforms in the US, UK, EEA, Canada or Switzerland pay connected accounts in their local currencies only within those regions, and that it does not support self-serve cross-border payouts to other countries. A marketplace with sellers in Kazakhstan, Georgia, Egypt or Peru therefore usually needs local payout providers for those countries, each paying in local currency, alongside its main provider.

Three decisions follow:

1. Where conversion happens. At the platform, at the payout provider or at the seller’s bank. Choose one and show the rate.
2. Which currency the seller’s balance is held in. A balance held in the seller’s currency avoids converting twice when refunds come back.
3. Who bears the cost. Put payout and conversion fees in the seller terms, line by line.

What tax reporting applies to seller payouts?

In the EU and the UK, platforms report what they pay sellers. The European Commission says DAC7 entered into force on 1 January 2023 and places the reporting obligation on the platforms themselves. It covers the sale of goods, personal services, rental of immovable property and rental of any mode of transport, whether cross-border or domestic. Platforms report personal identification for EU-resident sellers and financial information including the total consideration paid or credited to each seller, and must carry out due diligence to check that information. Platforms based outside the EU register in one member state and report no later than 31 January of the following year.

The UK runs similar rules. HMRC says platforms need not report sellers who receive EUR 2,000 or less, approximately GBP 1,700, for fewer than 30 sales of goods in a year, and that this exception does not apply to services, transport rental or property rental.

For payout design, the point is that seller identity, tax number, payout account and total payouts per year all need to live in one record. If they are spread across a sign-up tool, a payout provider’s portal and a spreadsheet, the January report becomes a project.

How should failed seller payouts be handled?

By cause, and never by blind resending. A failed payout is usually one of three things:

• Bad data: wrong account number, a name that does not match, a closed account. Ask the seller to fix it, verify the new account, then send again.
• Provider or rail problem: an outage, a timeout, an unsupported card. Wait for the final status of the first attempt, then send through another eligible provider.
• A hold or check: a compliance review or a verification gap. Tell the seller what is needed and by when.

Our article on why payouts are harder than payments lists the failure codes providers return and explains why some failures arrive days later. For a marketplace the extra rule is ledger discipline: a failed payout returns money to the seller’s balance, not to the platform, and the seller should see it there.

Worked example: holds and cash flow

Example figures, for illustration only.

A marketplace processes USD 3 million a month in sales for sellers in Mexico, Brazil and Kazakhstan, and keeps a 10% commission. It compares paying sellers 2 days after payment with paying 14 days after confirmed delivery, which on average is 21 days after payment.

	Pay at 2 days	Pay at 21 days
Seller funds paid out per month	USD 2.7 million	USD 2.7 million
Seller funds held at any time (approx.)	USD 180,000	USD 1.89 million
Refunds after payout, at 3% of sales	USD 90,000 recovered from sellers	Mostly deducted before payout

The longer hold leaves the platform holding about USD 1.9 million of sellers’ money, which must stay within its provider’s limits and seller terms, but most refunds are settled before the seller is paid. The short hold keeps sellers happy and leaves the platform chasing USD 90,000 a month in recoveries. Many marketplaces land in between: short holds for established sellers, longer ones for new accounts.

What are the common mistakes?

• Choosing the split model first and discovering later that refunds and disputes land on the platform.
• Holding funds longer than the provider allows, or longer than the seller terms say.
• Paying sellers in a foreign currency because it was the easiest route, not the cheapest for them.
• Collecting tax and identity data in a different system from payout data.
• Resending a payout whose first attempt has not yet reached a final status.

How does Omno handle seller payouts?

In Omno, seller payouts to local methods can be sent from your backend through Direct Link, using the same API as payments, with no Omno interface shown to the seller. Eligibility rules by country, method, customer group and customer verification level decide which providers can pay each seller, so a seller in Mexico can be paid through a provider with SPEI coverage while another provider handles payments. The final status of every payout reaches your back office by webhook, and the routing-decision log records which provider handled it. Your marketplace keeps the seller ledger and hold rules; the payouts page covers the payout settings.