Rolling Reserve on Your Merchant Account: How to Get Your Money Released

You woke up and your deposit is short. Not missing. Short. Your processor is depositing 90 or 95 percent of each day's sales and holding the rest. After a few days you finally get a straight answer from someone: you are on a rolling reserve.

A rolling reserve is a hold your processor places on a percentage of your daily revenue, usually 5 to 10 percent, that gets released back to you 90 to 180 days later. It is standard practice for businesses the processor considers high risk, and it can cripple your cash flow in the meantime. Here is exactly why it happens, how long it usually lasts, and the steps that actually get the reserve released earlier.

Related: If your entire account was frozen (not just a reserve), read Stripe froze my account: how to get your money back.

Why your processor just put you on a reserve

Rolling reserves exist because the processor is on the hook for chargebacks even after the card is charged. If your customer disputes a transaction 60 days later, the processor has to refund the cardholder whether or not they can reclaim the money from your account. A reserve is their protection against that risk.

Processors trigger reserves for a handful of specific reasons. In my experience, it is almost always one of these.

1. A chargeback ratio spike

Most processors set a hard limit of 1 percent chargebacks on gross transaction count. Hit that threshold for even one month and you go on a reserve automatically. The trigger is usually not the absolute number of chargebacks but the ratio, so a slow month combined with a normal number of chargebacks can catch you off guard.

2. Unusually high ticket transactions

If your average ticket size spikes suddenly, the processor's fraud system flags it. A jewelry store that normally runs $200 transactions suddenly runs a $12,000 charge, and the processor assumes either a data breach or a fraudulent transaction and opens a reserve to protect themselves.

3. A volume jump

Tripling your monthly volume in a single month is a classic reserve trigger. The processor's underwriting assumed a certain volume, and you just blew past it. Underwriting re-evaluates and, while that is happening, they hold a reserve.

4. A business category reclassification

This one is brutal. If someone at the processor decides your business falls into a "high risk" Merchant Category Code (MCC) that was not how you originally underwrote, you can get flipped onto a reserve with no warning. Common examples are coaches and consultants getting reclassified as "online education," subscription boxes getting reclassified as "recurring billing," and anything touching supplements or health products.

5. An external trigger

A chargeback from a specific card network (Discover in particular), a negative review surge, a negative news mention, a regulatory flag: any of these can cause the processor's risk team to open a reserve on your account.

How long a rolling reserve usually lasts

The contract language matters here. Pull your merchant agreement and look for the reserve section. You want to know three numbers:

1. Reserve percentage. Usually 5, 8, or 10 percent of gross daily sales.
2. Release period. How many days after each transaction the held amount is released back to you. Common values are 90, 120, or 180 days.
3. Total duration of the reserve program. How long the rolling hold itself stays in place. This is often 6 months but can be indefinite.

If your contract says the release period is 180 days, the first released money will arrive 180 days after the reserve started. After that, each day you process, the oldest held funds release back to you so the reserve becomes a rolling lag.

Steps that actually get the reserve released early

I have helped merchants through this more times than I want to count. These steps work in the order I list them.

Step 1: Get the specific reason in writing

Call the processor's risk department, not customer support. Ask for the specific reason the reserve was placed and the specific conditions that would cause it to be released. Get their answer in writing, in an email. "For our records, can you email me the exact reason the reserve was placed and what needs to happen for it to be released?"

This single email is your leverage. Processors often put reserves on for vague reasons and cannot defend them when asked. About a quarter of the reserves I have seen get released within a week of this email alone.

Step 2: Fix the underlying issue

If the reason was a chargeback ratio, file chargeback representments on every dispute you can win. Each won chargeback reduces your ratio retroactively. If the reason was unusual ticket size, send the processor proof of the legitimate sale (invoice, customer email, delivery confirmation).

Step 3: Ask for a reserve review in 30 days

Risk teams will rarely release a reserve immediately, but most will agree to review it after a clean 30-day window. Put the review date on your calendar and follow up on day 31 asking for the release.

Step 4: Negotiate a lower percentage

If the full release is not available, ask to drop from 10 percent to 5 percent. This is almost always possible after a clean 30 days and it cuts your cash-flow pain in half while you wait for the longer release.

Step 5: Move to a dedicated merchant account

If your processor is Stripe, Square, Shopify, or PayPal, the reserve is being managed by a risk algorithm with no human escalation path. Moving to a dedicated merchant account (a real underwritten account with a specific acquiring bank) gives you a human underwriter who can unwind the reserve if you explain the business. I have done this with multiple merchants who went from a 10 percent rolling reserve on Stripe to a zero-reserve dedicated account in under two weeks.

What you should never do

Do not try to route transactions through a second account to avoid the reserve. Processors detect this and it is the fastest way to get both accounts frozen and the funds held indefinitely while they investigate.

Do not chargeback your own customers to try to reduce volume. This tanks your ratio in the wrong direction and the processor sees it immediately.

Do not close the account while the reserve is active. The reserve will follow the closed account until the full release period has elapsed, and you will not have an active dashboard to check the status.

The cleanest long-term fix

If you are running a legitimate business and keep ending up on rolling reserves, you have probably outgrown the platform processor model. Stripe, Square, Shopify, and PayPal are volume-aggregator models that work great for small merchants but get progressively more conservative as your volume grows. A dedicated merchant account from a processor like ours rarely uses rolling reserves on legitimate businesses because the underwriting happens up front, not reactively.

If you want someone to look at your specific situation and tell you whether the reserve is justified or not, send over your statements. I will give you a straight answer either way.

Related reads: