Rolling Reserve Calculator for High-Risk Merchants

Merchants read a term sheet that says 10% rolling reserve, 180 days and file it next to the discount rate, as if it were another 10% off the top. It is not. Every dollar comes back to you if chargebacks do not eat it. It is collateral, not a charge. It moves a fixed slice of your cash from your bank account to the processor's and keeps it there for as long as you process. The number that matters is not the percentage on the term sheet but monthly volume multiplied by the reserve percentage multiplied by the hold period in months.

Run that on a real account. A business doing $100,000 a month at 10% on a six month hold has $10,000 withheld every month. Month one it holds $10,000, month two $20,000, and by the end of month six the balance is $60,000. In month seven the first batch releases, and from then on $10,000 goes in and $10,000 comes out every month. Cash flow normalises. The $60,000 does not come back.

That plateau is where merchants stop paying attention, and it is the expensive part: the monthly pain has gone and the balance sheet hole is permanent. At the 6.75% bank prime loan rate in the Federal Reserve's H.15 release of September 2, 2026, carrying $60,000 you cannot touch costs roughly $4,050 a year in financing. The hole also scales with success: grow to $200,000 a month and the steady state locked balance grows to $120,000, funded out of the months when you are buying inventory and hiring.

A rolling reserve withholds a percentage of every batch and releases each batch on its own clock. PayPal's US User Agreement spells out the mechanics: a reserve set at 10% for a 90 day rolling period means 10% of day 1's money is held and released on day 91, day 2's money on day 92, and so on. PayPal calls rolling reserves the most common type. Stripe works the same way, holding a percentage of each charge and releasing that hold a set number of days later.

An upfront reserve is a different instrument. You post a lump sum before processing a single transaction, and nothing is withheld from your daily batches. PaymentCloud puts the usual size at 50% to 100% of monthly processing volume. That is brutal at signup and benign afterwards. A rolling reserve is the reverse: painless in week one and permanent thereafter. If you have the cash and you expect to grow, an upfront reserve is often cheaper, because it does not scale with your volume.

A minimum reserve is a floor balance you must keep available in the account at all times. PayPal builds one either as a single upfront deposit or by taking a percentage of sales until the floor is reached, and its agreement states that one or both categories may be applied at the same time. Read your reserve notice carefully for the word 'and', because two reserves at once is a documented possibility, not a horror story.

A capped reserve withholds a percentage until the balance hits a fixed ceiling and then stops. This is the version to ask for, and Corepay and Stripe both describe it. A capped reserve behaves identically to a rolling one until you reach the cap, then stops growing while the rolling version tracks your volume forever. If an acquirer opens with 10% rolling, ask what the same risk looks like capped at six months of reserve at today's volume. You are asking them to fix the number, not lower it, which is a much easier yes.

There is no rate card for reserves. The networks permit them and set no number. Visa's public rules require an acquirer to pay its merchant promptly after transaction deposit, less credits, discounts, disputes, other agreed fees, and 'Merchant reserve funds (if applicable) accumulated to guarantee the Merchant's ... payment system obligations to the Acquirer.' A second rule, US region only, requires an acquirer to hold and control reserves accumulated from merchant settlement funds. Both are permission, not a formula. Your reserve is a term in your merchant agreement and nothing else, which is why the same business gets quoted 5% at one acquirer and 15% at another the same week.

What does get published sits in a narrow band. Stripe's guidance puts rolling reserves at 5% to 15% of each transaction, with 30 to 90 days for lower risk sectors and 180 days or more for industries with higher chargeback rates. PayPal's contractual example is 10% for 90 days. Corepay, a US high-risk acquirer, publishes 5% to 15% with holds usually 90 to 180 days. PaymentCloud puts the average at 5% to 10% of expected monthly sales volume. Square publishes neither a percentage nor a duration.

The 180 day figure is not arbitrary and it is not a floor. Under the Visa Core Rules and Visa Product and Service Rules effective April 18, 2026, the standard dispute time limit is 120 calendar days from the transaction processing date, with certain delayed delivery conditions stretching to a ceiling of 540 calendar days. Regulation Z adds a shorter clock at the front: a cardholder must give notice of a billing error no later than 60 days after the creditor transmitted the first periodic statement reflecting it. So 120 days covers most exposure and 180 gives an acquirer a margin. Stripe's Connect Reserves API enforces that ceiling in code: a hold cannot be scheduled more than 180 days out, and releases automatically at 180 days.

If you are quoted more than six months, or more than 10%, the burden is on the acquirer to name the exposure. Ask which dispute conditions apply to your product and for how long. A merchant shipping physical goods in three days has a completely different tail than one selling a twelve month membership. Bring the 120 day number to the conversation.

PayPal publishes the factors it weighs, and they are the ones every underwriter uses: how long you have been in business, whether your industry has a higher likelihood of chargebacks, your payment processing history with PayPal and other providers, your business and personal credit history, your delivery time frames, and whether you have a higher than average number of returns, chargebacks, claims or disputes. Stripe adds two more: longer than average delivery windows, and an unexplained sharp increase in processing volume. A good month can trigger a reserve.

Coming off is slower than going on and it is never automatic. Stripe runs another credit review a few days before a reserve is set to expire and decides then whether to remove, decrease, increase or extend it. Square reviews accounts with reserves after a minimum of six months, proactively and without being asked. PaymentCloud is blunter: renegotiation becomes possible only after about six months of actual processing without chargebacks. Nothing moves unless you ask, with a chargeback ratio and a refund policy to point at.

Read the release language in your contract before you rely on the hold period. The Stripe Services Agreement, section 3.3, says the user acknowledges Stripe has sole control over the Reserve, has no legal or equitable right or interest in any earnings generated by it, and that Stripe releases funds 'only if, and to the extent that, Stripe is satisfied that the relevant risk exposure has been mitigated.' The hold period on your term sheet is a schedule, not a guarantee, and the interest your money earns is not yours.

Leaving is where the number gets ugly, and almost nobody models it. Stopping processing stops new withholding, but the existing balance does not release on the same day. PaymentCloud states that banks usually hold reserve funds for 180 days post closure. PayPal's user agreement lists, among the actions it may take, holding your business account balance for up to 180 days to protect against the risk of liability, and longer under a court order. Square's terms say only that funds held at closure are paid out on your payout schedule, naming no day count at all. Switch from acquirer A to acquirer B, both wanting 10% for six months, and the worst case is not a wash: A's $60,000 sits frozen post closure while B's builds from zero, and your peak locked balance hits $120,000 for the overlap. Budget that before you sign with B, not after.