Plan for the week your payouts stop.

The week it happens

Picture a composite store, not a real one. A small homeware brand gets mentioned in a newsletter on a Thursday. Orders triple over the weekend. On Tuesday the owner opens the payments dashboard and sees that the payout she was expecting is smaller than it should be, and a note says part of her balance is being held. The orders still need packing. The supplier still needs paying on Friday.

Nothing illegal happened, and the provider isn't being unreasonable from where it sits. A sudden change looks like risk. If those orders turn into refunds or chargebacks, the provider is on the hook, so it keeps some money back until it's comfortable. Stripe's documentation says so plainly: "Sometimes, Stripe might create a reserve balance on your behalf to ensure that your Stripe account can cover any expected incoming refunds or disputes." Other providers have their own versions.

You can't always stop this happening. What you can control is how ready you are. A payout hold is a cash-flow problem first and a software problem second, and most of the preparation is deciding things in advance. Think of it as a set of rungs. Most stores only need the first three.

Rung one: know what your provider is looking at

Providers don't publish their exact rules, but holds usually follow something they can see from their side. Volume that jumps well beyond your normal pattern. A rise in refunds or disputes. A long gap between taking payment and delivering, as with preorders or made-to-order goods. Business details that don't match what the account says you sell. A change of bank account or owner at the same moment as a spike.

So start by reading your own account the way the provider does:

• Are your business description, products and website in the account still accurate?
• Is the bank account current, and are the people listed as owners still the right ones?
• Do you know your refund and dispute levels over the last few months, roughly?
• Do you know where in the dashboard a hold or review would show up, and who would see the email?

That last one sounds trivial. It isn't. Notices go to whoever set up the account years ago, and some of those inboxes are no longer read by anyone.

Rung two: tell them before they notice

If you know a spike is coming, say so. A product launch, a big wholesale order paid by card, a sale you're promoting heavily, a preorder that won't ship for six weeks. Most providers have a support route for exactly this, and an account that has explained itself in advance looks very different from one that suddenly behaves strangely.

Preorders deserve special care. The longer the gap between payment and delivery, the more refund risk the provider is carrying. If your shop takes payment long before it ships, check how your provider treats that, and look at whether authorizing now and capturing later suits you better. Our note on naming auth, capture and settle before checkout ships goes into those choices.

Keep your evidence tidy too. If a provider asks for proof of delivery, supplier invoices or your refund policy, you want to send it the same day, not spend a week finding it.

Rung three: a cushion and a plan for customers

The real damage of a hold is timing. Money you've earned arrives weeks later than you planned. A cushion, whether that's cash in the bank, an unused credit line or a minimum balance kept in the payment account, turns a crisis into an inconvenience. Decide how many weeks of payouts you could live without, and work toward that.

Then decide what you'd do in the first week, before you're in it:

• Who calls the provider, and what do they send?
• Which payments get made on time no matter what (staff, key suppliers), and which can wait?
• Does anything change for customers? Usually nothing should. But if a hold lasts and you're short on stock money, decide in advance whether you'd pause preorders or slow a promotion rather than miss promised ship dates.

And when you do talk to the provider, ask one question above all: what would end this? A date, a document, a drop in disputes, a delivery confirmation for the preorders? A specific answer turns an open-ended wait into a task list, and gives you something to plan your cash around.

Write it on a page and keep it with your other business documents. The point is that nobody has to invent the plan while panicking.

Rung four: a second way to get paid

For a business that depends on online sales, a second payment provider is worth considering. Not to split traffic for the sake of it, and not as a way around a review (that tends to make things worse). The point is a tested path to keep taking payment if your main account is paused or restricted.

Set up properly, that means:

• An approved account with the second provider, with your real business details.
• A checkout that can switch to it without a developer rebuilding anything at midnight.
• A test transaction run every so often, so you know it still works.
• Order and payment records that live in your own system, not only in each provider's dashboard, so switching doesn't scatter your history. Rebuilding somewhere else once is the same idea applied to hosting.

This rung costs something: another set of fees to compare, another integration to maintain, another dashboard to reconcile. For a small store doing modest volume it may not be worth it yet. For a business where a week without card payments means missing payroll, it usually is.

Where to stop climbing

Most stores should be on rung three: they know their account, they warn their provider before a spike, and they have a cushion and a written plan. Rung four is for businesses where online payments are most of the revenue, or where a single provider pausing would stop the business.

Whichever rung you're on, the useful question is the same: if the payout you expect on Friday didn't come, what would happen on Monday? If the honest answer is "we'd figure it out," it's worth an hour to figure it out now.

We build and connect ecommerce operations, including checkout, payments and the order records behind them, and we'll happily look at how exposed your store is to one provider. If that Friday question makes you uneasy, talk to us.

Related work: Paddle8.