A rolling reserve is not a fee. It is your money, held against a defined risk, for a defined period, under a clause you can read. When the period ends and the money does not move, the question is not whether you have a claim — it is whether you can prove it. Most merchants can, and do not know it.
How release clauses are typically written
Reserve clauses in acquiring and PSP agreements follow a recognisable pattern. The institution withholds a percentage of settled volume — commonly somewhere between five and fifteen per cent — and each withheld tranche is released after a fixed window, typically 90 or 180 days, the window being calibrated to the chargeback exposure of the underlying transactions.
Read your clause carefully, because the drafting decides everything. Three features matter most:
- The release trigger. Is release automatic on expiry of the window, or "subject to" something — a review, the absence of open disputes, the institution's discretion?
- The qualifier. Many clauses say "180 days or such longer period as [the institution] reasonably determines". That qualifier is where retention goes to hide. Note the word that survives in almost every version: reasonably. A discretion expressed that way is not unlimited, and an institution exercising it has to be able to say what it is for.
- Post-termination treatment. Most agreements have a separate regime for reserves after termination — often a final holding period running from the termination date. This is the clause that governs the scenario most merchants are actually in.
None of this drafting is sinister in itself. Reserves exist for a real reason: chargebacks arrive late, and the institution carries the scheme liability. The problem is not the clause. The problem is what happens after the clause has done its job.
The three common stretches
When a reserve is retained past its contractual release date, the justification tends to take one of three forms. We see them often enough to treat them as patterns.
1. The perpetual risk review. The window expires; the merchant asks; the institution replies that the account is "under risk review" and the reserve will be released "once the review concludes". No scope, no timeline, no named reviewer, and — months later — no conclusion. A review invoked to justify retention has to be a review of something. A file of generic responses, each restating the review's existence and none describing its content, is itself evidence: it shows the institution was asked, in writing, and could not point to a contractual basis for continuing to hold the funds.
2. The reclassified reserve. The rolling reserve quietly becomes something else — a "security amount", a "collateral requirement", a "termination holdback" — usually at or around offboarding, and usually on terms found nowhere in the agreement. Reclassification matters because it swaps a clause with a defined release date for one without. Unless the agreement actually gives the institution the right to convert one into the other, the original release clause keeps running, whatever label appears on the statement.
3. The set-off against unspecified fines. The reserve is consumed — partly or wholly — by deductions: scheme fines passed through without underlying documentation, "non-compliance assessments", accumulated penalty fees. A set-off is only as good as the obligation it is set against. An institution deducting a fine from your reserve should be able to produce the scheme notice behind it, the calculation, and the contractual basis for passing it through. Strikingly often, it cannot.
In each pattern, note what the institution is not saying. It is not saying the money is not yours. It is saying — indefinitely — not yet. That distinction is the foundation of the claim.
The patterns also compound. A typical file shows all three in sequence: the review justifies the first missed release date, the reclassification covers the next six months, and by the time the merchant escalates, deductions have quietly reduced the balance in dispute. Each step looks procedural on its own. Laid out on a single timeline — which is exactly how we present a file — the sequence reads differently.
What your documentation must show
A reserve claim is one of the most documentable claims in the merchant ecosystem, because every element of it exists on paper. The file needs four things.
The clause. The agreement, with the reserve and release provisions, every schedule and amendment, and any side letter that touched the reserve percentage or window. If the institution varied the terms along the way, the variation correspondence too.
The dates. When each withheld tranche arose and when its window expired. For a post-termination reserve: the termination date, and the final release date the clause produces. This is arithmetic, and you should do it before the counterparty does — the merchant who arrives with a tranche-by-tranche release schedule sets the baseline of the conversation.
The statements. Settlement files and account statements showing the amounts withheld and the running reserve balance. Export them now, while you still have portal access — not when the dispute escalates and the login stops working.
The written request. A clear, dated, written demand for release after the contractual date, and the institution's response — or its silence. This single document changes the character of the file. Before it, the institution can characterise the retention as routine. After it, the retention is a considered decision, made in writing, with whatever justification the institution chose to give. Make the request specific: cite the clause, state the amount, state the date the window expired.
If you have these four elements, you have most of a file. What remains — reconciling the reserve balance against the settlement history, pricing the claim, choosing the track — is the work we do after a fit check.
Retention is not forfeiture
One more distinction, because counterparties blur it deliberately. A reserve clause is a retention mechanism: it delays payment of money that remains yours. It is not a forfeiture mechanism: it does not convert your money into the institution's because the relationship ended badly, because the account was terminated for risk, or because the offboarding letter used stern language.
For the institution to keep the money — as opposed to merely holding it longer — it needs a positive basis: an actual liability of yours it can lawfully set off, in an amount it can evidence. "Terminated for risk" is a reason to hold a reserve through the chargeback tail. It is not, by itself, a reason to keep it after the tail has run off. Merchants give up reserve claims every year because the termination felt like a punishment and the reserve felt like the fine. The claim usually survives the termination — and the angrier the offboarding letter, the more carefully the set-offs deserve to be checked.
If your release date has passed
Pull the agreement, run the dates, and send the written request if you have not already. Then let us take a look: the reserve scenario in brief is on our reserves page, and the assignment mechanics are defined under the CARA. A fit check takes five minutes, costs nothing upfront, and gets you an initial view within five business days.
This article is for information purposes only and does not constitute legal advice.