How to hold funds in a marketplace: escrow vs auth-hold vs delayed capture

You run a two-sided marketplace. The buyer pays upfront; the seller gets paid a week later, once the order’s confirmed and the dispute window’s closed. Simple to describe — but between “buyer paid” and “seller paid” sits a real question that trips up almost every platform: where does that money actually live for those seven days, and who’s allowed to touch it?

Hold it wrong and you get one of two failures. Either you never really controlled the money — it landed in the seller’s account and you’re chasing a clawback when a buyer disputes — or you held it so long the mechanism expired underneath you and the payment vanished. Here’s the honest read on the three ways to hold buyer funds, when each one fits, and the part everyone gets excited about and wrong: earning on the balance.

Three ways to hold: escrow, auth-hold, delayed capture

They sound interchangeable. They aren’t. Each holds money for a different length of time and puts it in a different place.

Authorization hold (auth-hold). The money never moves. When a card is authorized, the buyer’s bank reserves the amount and earmarks it — the buyer can’t spend it elsewhere, but it hasn’t left their account and it isn’t yours. You then have a window to capture it. The catch: that window is short. On most cards an authorization is only good for about seven days before the bank releases it automatically. Auth-holds are perfect for “confirm now, bill on dispatch” — a few hours or days. They are the wrong tool for a settlement window that runs weeks.

Delayed capture (authorize now, capture later). Same first step — authorize — but you deliberately postpone the capture until you’re ready to actually take the money. It’s the clean way to say “hold the buyer’s commitment, but don’t bill until the seller ships.” You’re still living inside the authorization’s lifespan, so the same expiry pressure applies; some processors offer extended authorizations that stretch the hold (Stripe, for example, can push eligible card authorizations toward roughly 30 days), but this is card-network-dependent and not a general-purpose vault. Delayed capture is a billing-timing tool, not a treasury one.

Escrow (hold-until-release). This is the one built for a settlement window. The money is actually collected and held in a segregated account, and released only when a rule is satisfied — delivery confirmed, inspection passed, the cancellation window expired. Unlike an auth-hold, it survives for as long as your rules need, because the funds are genuinely held rather than merely earmarked on a card. This is what most marketplaces mean when they say “we hold buyer funds until delivery.”

One more limit worth knowing if you’re on Stripe Connect: it’s a rail, not a custodian. Set connected accounts to manual payouts and Stripe holds the seller’s balance until you release it — but only up to a maximum of about 90 days, after which it pays out on its own. (Stripe also runs its own risk reserves, often on a rolling ~90-day basis, against refunds and chargebacks.) Fine for a seven-day window. Not a place to warehouse money indefinitely — and not designed to be.

The quick decision:

Need to hold for hours to ~a week?   → auth-hold / delayed capture
Need to hold for a settlement window
(days to weeks), release on a rule?  → escrow / managed account
Need to hold beyond ~90 days?        → neither Connect nor a card
                                       auth — that's a treasury question

The 7-day settlement window (and the interest question)

Your exact case: buyers pay upfront, sellers get paid after 7 days. That’s an escrow-style hold — the money is collected, parked, and released on day seven (or on delivery, whichever your rule says). The clean way to run it is a managed, safeguarded account: the funds sit segregated during the window, and a release rule pays each seller out at the end of it.

Now the question everyone asks: can we earn interest on that balance while it sits?

Here’s the honest read. That money is not yours. During the window it’s client money — the buyer’s until you release it, owed to the seller when you do. At an FCA-authorised e-money institution, client funds must be safeguarded: held segregated from the firm’s own money and, by rule, not lent out the way a bank lends deposits. Safeguarding is a protection mechanism, not deposit insurance — it means the money is ring-fenced so it can be returned to whoever owns it if the provider fails (we wrote a whole plain-English guide on where your money actually sits).

So “park the float and earn yield” runs straight into a wall of nuance: whether any return can be earned on safeguarded balances at all, and — crucially — who is entitled to keep it, are regulated questions with real constraints. It is not a dial you turn up. Anyone quoting you a headline rate on held marketplace funds is quietly skipping the part that decides whether it’s even permissible, and whose it is. Treat earning-on-the-balance as a conversation for your provider and your regulator, not a marketing bullet — the honest answer depends entirely on your structure.

What you can nail down cleanly: the money is held safely, segregated, and released exactly on your rule. That’s the part that should never be fuzzy.

Where Fynex fits

Fynex is the layer that runs this hold end to end — without pretending to be a bank.

Client funds are held safeguarded at an FCA-authorised e-money institution: segregated from everyone’s operating money for the length of your settlement window. You define the release as a rule, not a cron job someone babysits — hold for seven days, release on delivery confirmation, return on cancellation. When the window closes, the split runs as lines you defined — seller payout, your commission, any partner cut — and each leg is paid over the cheapest compliant rail, then reconciled straight back to the original order in Xero or QuickBooks. Auto-invoicing, agentic collections and cash forecasting sit on the same picture, so the held balance isn’t a black box you reconcile at month-end.

And because anything that actually moves money is gated behind human approval, “release the funds” is a decision you confirm, not something that fires unseen. Fynex is PCI DSS Level 1 and can act as Merchant of Record where that’s the right structure.

The frame we keep coming back to: accounts hold money, rails move it, Fynex is the layer that thinks. The holding is safeguarded; the release is a rule; the payout is optimised; the books are already done. What we won’t do is dress up the float as a yield product — because the honest version of that answer is “it’s client money, and it’s complicated.”

Choosing your hold model

Match the mechanism to the clock, and be honest about whose money it is:

• Seconds to a week, decide-then-bill → auth-hold or delayed capture. Cheap, native to your processor, but it expires — don’t lean on it for a real settlement window.
• Days to weeks, release on a rule → escrow in a managed, safeguarded account. This is the marketplace default when sellers are paid after the buyer.
• On Stripe Connect → fine for short holds, but remember the ~90-day ceiling on manual payouts and Stripe’s own reserves. It’s a rail with a hold feature, not a treasury.
• Tempted by yield on the balance? → slow down. It’s client money, it’s safeguarded, and whether you can earn on it — and keep it — is a regulated question, not a feature toggle.

Get the hold right and the rest of your marketplace gets quieter: fewer clawbacks, cleaner disputes, sellers paid on time, and books that reconcile themselves. That’s the whole point of holding money well — it’s not about squeezing the float, it’s about the money being exactly where it should be, exactly when it’s owed.