Merchant reserves and deposit holds, explained

A reserve is money your processor keeps from your settlements as a buffer against chargebacks and refunds you might not be able to cover. A hold is the same idea applied suddenly to a specific batch or period. Both exist because the processor advances you funds before a transaction is beyond dispute, and both feel like the processor keeping your money — which, factually, is what is happening.

Understanding why makes the conversation about terms rather than about grievance.

Why would a processor want one?

Because if a customer disputes a sale in four months and your business is gone, somebody still owes the money, and that somebody is the acquiring bank. A reserve is that bank's protection against your future self.

Reserves are common for new businesses without processing history, for categories with higher dispute rates, for businesses that take payment well before delivery, and for accounts whose volume jumps sharply. None of those are accusations about you specifically.

What are the usual structures?

Three. A rolling reserve, where a percentage of each day's settlement is held and released on a schedule — a fixed share held for a set number of months, then paid out as the window rolls forward. A capped reserve, which builds to a fixed amount and then stops. And an upfront reserve, funded at the start.

A rolling reserve is the most common and the most negotiable, because three variables are in play: the percentage, the holding period, and whether it is capped.

What should you actually negotiate?

The cap and the review date, more than the percentage. A rolling reserve with no cap grows with your business forever, which is a poor deal for a store that is succeeding. A cap turns it into a finite buffer.

Then ask for a written review date — a point at which clean processing history triggers a reassessment. Providers agree to this more often than merchants ask, and a reserve without a review mechanism tends to become permanent through inertia rather than decision.

What causes a sudden hold?

Pattern changes, mostly. A volume spike well above your declared numbers. A single transaction far above your average ticket. A run of chargebacks. A sharp shift in entry method, such as suddenly keying transactions that were previously dipped. Or a mismatch between what you sell and what a disputed transaction describes.

Most of these have innocent explanations, and the fastest way through is to supply the explanation with documents — invoices, delivery confirmations, an event that explains the spike. Arguing about the principle takes longer than answering the question.

How do you keep it from happening?

Tell your provider before the pattern changes. A big catering order, a seasonal peak, a new product line with higher tickets, a second location — a short email in advance converts a risk flag into a note on the file.

That habit is worth more than any negotiation. Risk teams respond to surprises; an account that explains itself in advance stops generating them.

What does a hold actually look like day to day?

A deposit that does not arrive, usually without a notice reaching you first. The store notices the gap in the bank account before anybody notices the email, which is why the first ten minutes go into confirming that a hold is what happened rather than a bank delay or a failed batch.

Check three things in order: did the batch close, did the processor report it as settled, and has anything arrived in your portal. That sequence separates a genuine risk hold from the two much more common explanations, and it means the call you make afterwards is to the right department.