A Shopify merchant sold a $12.72 order in October 2024. The payout that hit their account was $0.24. No email. No warning. The payout date in the dashboard read 11/12/2099. For most merchants, that's their first introduction to a rolling reserve.
A rolling reserve is a percentage of each transaction your payment processor withholds and holds in a non-interest-bearing account for a defined period, usually 90 to 180 days, before releasing it back to you.
Think of it like a conveyor belt. Each day's sales step onto the belt, and each day's reserve steps off the other end exactly 90 or 180 days later, whatever the hold period is. If a processor holds 10% for 180 days, the 10% from your January 1 sales comes off the belt on July 1. The 10% from January 2 comes off July 2. New sales keep stepping on while old ones roll off, which is why the reserve never fully empties as long as you keep processing. Standard-risk merchants typically see 5-10% held. High-risk merchants see 10-15%. Merchants in the highest-risk categories have reported reserves up to 25%. None of it earns interest while the processor holds it.
Rolling reserves withhold a percentage of every transaction continuously with no ceiling. Capped reserves work the same way but stop withholding once the reserve balance hits a set maximum. Upfront reserves are a lump sum you deposit before the processor lets you start running transactions at all.
| Reserve type | When it's used | What it means for you |
|---|---|---|
| Rolling | Established merchants when a risk signal fires mid-relationship | Withholding never stops as long as you process |
| Capped | Negotiated terms with a defined ceiling | Withholding stops once the cap is reached |
| Upfront | New high-risk merchants with no processing history | One deposit required before you can process |
If you are in a reserve conversation with a processor, capped is what to push for. It is the only structure with a defined end to the withholding.
Processors require reserves because chargebacks land on them first. When a customer disputes a charge and wins, the card network debits the acquiring bank, the bank debits the processor, and the processor then tries to recover the money from you. If your account is empty or already closed, the processor eats the loss. The reserve is their buffer against that outcome.
A rolling reserve isn't a punishment. It's a processor's way of buying time while deciding how much risk they're willing to keep carrying.
Processors often set reserves before your chargeback rate becomes a major problem, because they're the ones financially responsible if you can't cover the refunds or disputes yourself.
A volume spike reads as elevated risk to an aggregator like Stripe or Square, even when your chargeback rate hasn't moved. Algorithms don't know the difference between unexpected growth and unexpected risk, and the reserve adjusts before anyone reviews whether the growth was legitimate.
Stripe applies this pattern without a stated volume threshold, and it has been documented in more than 200 cases handled by a single legal firm tracking fund-hold disputes. One BBB complaint against Stripe describes a 25% rolling reserve placed on an account "due to a temporary volume increase from a seasonal event," with the merchant unable to make payroll for laborers who had already done the work. Fitness memberships in January, subscription boxes in Q4, travel agencies in summer: these are documented trigger windows, not edge cases. Square runs the same play. One merchant reported a 120-day hold with zero chargebacks and no stated problem at all.
The reserve does not pause your obligations. Payroll, suppliers, and inventory orders keep coming due. Only your incoming cash stops. Run the math on what that actually costs: a merchant processing $500,000 a month with a 10% rolling reserve on a 90-day hold has roughly $150,000 in permanent, non-interest-bearing lockup at any given time.
There are two different reasons a processor holds a reserve, and they lead to opposite outcomes. Sometimes it's a sign the processor wants to continue the relationship: the reserve is monitoring capital with a defined release schedule, and clean performance over time (typically 6-12 months) leads to a renegotiation. Businesses operating in categories a processor has already decided not to support, telehealth is a common example, often experience the other kind: a reserve that signals the relationship may be ending rather than continuing. There is no real release date, because there was never a plan to keep the relationship. The reserve just extends.
This is what it looks like in practice, documented at Stripe: a 90-day hold notice on day 0, extended to 120 days by day 85, then an additional 90 days required for "ongoing review" past day 200. No contractual cap. No person you can call to change the outcome.
With an aggregator like Stripe or Square, reserve terms are set algorithmically and there is no one to negotiate with. With a dedicated high-risk processor, reserve terms are part of the approval conversation from day one, not something that appears after a surprise.
That difference comes down to structure. A dedicated processor has the ability to review reserve terms over time because there's an actual underwriting relationship on file, not an anonymous risk score getting recalculated overnight. Terms get set at approval and reviewed on a schedule, typically after 6-12 months of clean processing history, instead of adjusting on their own the moment an algorithm flags something.
The best way to avoid a rolling reserve is to set expectations before your business changes. Let your processor know about major volume increases, seasonal spikes, new products, or significant changes to your business model before they show up as unexpected risk.
If you got a reserve notice and you're not sure whether to ride it out or find a new processor before the next extension hits, that's exactly the conversation to have now, not after day 200. At Pinpoint, we regularly help merchants navigate reserve conversations, negotiate terms where appropriate, and place businesses with banking partners that better match their risk profile. Talk to a dedicated account manager.
How much does a rolling reserve typically hold back? 5-10% for standard-risk merchants, 10-15% for high-risk merchants, and up to 25% in the highest-risk categories.
How long does a rolling reserve last? Usually 90 to 180 days, released on a rolling schedule as new sales replace the oldest held funds.
Can a rolling reserve be negotiated down? Not with an aggregator like Stripe or Square, where terms are set algorithmically. With a dedicated high-risk processor, reserve terms are set at approval and reviewed on a defined schedule, typically after 6-12 months of clean processing.
Does a rolling reserve mean my account is about to be closed? Not always. It depends on why the processor placed it: a reserve meant to keep you processing has a defined release schedule, while a reserve on a relationship the processor is exiting just keeps extending with no real end date.