If you sell anything online through a platform that handles the payments for you, there is a clause you have probably never read closely: the one that lets the platform hold your money. It might be a rolling reserve, a delay before your first payout, a hold triggered by a refund or a chargeback, or a freeze while someone reviews your account.
This keeps coming up across the communities we follow, and the stories have a pattern. A new seller gets the first client payment and the account is flagged within minutes. A creator has a small sale charged back and the whole balance is locked. Someone requests a withdrawal and the account is restricted right after. A seller doing serious monthly volume decides to move everything to a different provider after a hold. A small company finds it cannot refund its own customers because the funds it would refund from are frozen. Freelancers complain about fees and week-long holds with only automated support to talk to. And from the operator side, a marketplace owner explained that paying vendors instantly means refunds land on the owner, so someone has to hold something.
A payments consultant pointed at the uneasy part: plenty of merchants flagged by an automated check may never get a human second look at all.
We want to keep this conversation away from the appeal and suspension stories, which are their own topic. This one is about the mechanics: is holding seller money a reasonable cost of doing business, or a risk sellers should refuse to carry? We see three camps.
Camp 1: holds are the price of instant onboarding
Platforms that let anyone sign up and get paid within a day are taking on fraud and refund risk that a traditional merchant account would have screened out with paperwork. Reserves and first-payout delays are how they price that risk. Without them, the easy sign-up would not exist.
People in this camp say: read the terms, expect a hold early on, keep a cash buffer, and treat the platform as a convenience you pay for in delay rather than in fees alone.
Camp 2: holds are fine, invisible holds are not
This camp accepts that someone has to cover chargebacks and refunds. The objection is to how it is done. The rules are vague, the triggers are automated, the duration is unknown and the person who can explain it is hard to reach.
They would accept a reserve if the platform said up front: this percentage, for this long, released on this schedule, triggered by these events. A predictable hold is a cost you can plan around. An unpredictable one is a risk to payroll, refunds and delivery promises you already made.
Camp 3: never let one platform hold all of it
The third camp says the problem is concentration. If one provider holds your checkout, your balance and your customer list, any hold becomes an existential event.
Their answer is structural: get your own merchant account once volume justifies it, keep a second processor ready, sell through your own site where you control the checkout, and keep enough of a float that a frozen balance is an inconvenience, not a crisis. They accept more paperwork and responsibility in return for fewer surprises.
The grey areas
Who is the merchant of record? When the platform is the seller of record, it carries tax and liability and is likely to hold more. When you are, you carry more risk and paperwork but usually see fewer surprise holds. Neither is free.
Services versus products. Service work, where delivery happens weeks after payment, looks riskier to automated systems than a digital download. Agencies and freelancers often hit holds that product sellers never see.
Marketplaces in the middle. If you run a marketplace, you are on both sides. Pay vendors instantly and you eat refunds. Hold their money and you become the platform they complain about. Most operators end up with a short hold tied to the delivery or dispute window, and the honesty of how that is explained matters as much as the number.
Small chargebacks with big consequences. A single disputed small sale should not freeze a whole balance, but to a risk model a new account with a chargeback looks the same as fraud. Whether that is a bug or a feature depends on which side of the dashboard you sit.
Where we lean
We build marketplace and checkout tools, so we see this from both sides. Our lean is between camps 2 and 3: holds tied to a clear delivery or dispute window are reasonable, and the schedule should be written down where sellers can see it before they sign up. Past a certain size, a business should not have its whole balance and customer list in one place it does not control. That is one view, and the people who have lived through a frozen payout know the trade-offs better than we do.
Your turn
- Have you had a payout held or a reserve applied? What triggered it, and how long did it last?
- Which camp are you in: holds are fair, holds are fine if they are predictable, or never let one platform hold all of it?
- If you run a marketplace, how long do you hold vendor payouts, and how do you explain it to them?
- At what point did it make sense for you to get your own merchant account or a second processor?
Top comments (0)