How to Explain a Reserve to Your Merchant

Last Updated on August 3, 2026

A reserve is money set aside from a merchant’s sales to cover any chargebacks. It’s the merchant’s money, and it comes back to them over time as the account builds a clean track record. It is a standard onboarding structure, not a penalty. However, merchants rarely hear it that way unless you frame it well. This is the conversation that either keeps a deal moving or bringing it to a halt, and how you handle it says more about you than about the processor. Here are the talking points that work.

The reserve conversation is where a lot of good deals stall. The approval came back with conditions, the merchant hears “they’re holding my money?,” and suddenly the person who was ready to sign is asking why they should. You are the one who has to bridge that gap. This piece gives you the language to do it.

First, Understand What a Reserve Actually Is

A rolling reserve holds back a small percentage of each day’s settlements (typically 5% or 10%) into a separate account. That held-back money isn’t gone. It’s the merchant’s money, set aside to cover chargebacks that might come in later, and it gets released back to the merchant on a rolling basis as the account builds history. Money goes in as new transactions settle, and older held-back funds release back out as they age past the risk window. It’s a rolling balance, not a permanent deduction.

Not every reserve runs indefinitely on a percentage. Some are structured as a capped reserve. This is where the processor holds back that same small percentage of settlements only until the reserve reaches a set total (a fixed dollar target) and then stops withholding once the account gets there. After the cap is reached, the merchant receives their full settlements again, and the accumulated total sits as the cushion. The two structures work the same way day to day; the difference is that a capped reserve has a defined endpoint for the withholding, while a rolling reserve keeps cycling money in and out as long as it’s in place. Which structure applies depends on the account, and it’s worth knowing which one your merchant has before you explain it to them, since “we hold back a percentage until we reach a set amount, then you’re back to full settlements” is often an easier conversation than an open-ended rolling reserve.

The reason it exists is timing. When a customer disputes a charge, the chargeback can land weeks or even months after the original transaction. The reserve makes sure there’s money available to cover those disputes when they arrive, so the processor isn’t exposed and, this is the part merchants miss, so the merchant isn’t suddenly hit with a demand to cover chargebacks out of pocket after they’ve already spent the revenue. The reserve is a cushion that protects both sides.

That’s the whole concept. Not a fee. Not a hold on their ability to operate. A percentage of settlements set aside temporarily, released back over time, that covers disputes when they arrive.

The Framing That Works: Standard Practice, Not Punishment

The single most important thing you can do in this conversation is set the frame before the merchant sets it for themselves. Left to their own interpretation, a merchant hears “reserve” as “they don’t trust me” or “they’re keeping my money.” Your job is to replace that frame with the accurate one: this is a standard structure that comes with certain kinds of accounts.

Language that works:

“A reserve is a normal part of how processing works. It’s a small percentage of your settlements held in a separate account that covers any chargebacks that come in after a sale, and it releases back to you as your account builds history. It’s not a fee and it’s not money you lose. It’s your money and it’s set aside temporarily as a cushion.”

Notice what that framing does. It normalizes (“a normal part of how processing works”), it’s specific about the operation (“held in a separate account… releases back to you”), and it corrects the two misconceptions head-on (“not a fee… not money you lose”). You’re not apologizing for the reserve and you’re not overselling it. You’re explaining it as what it is.

Avoid defensive or apologetic framing. Don’t say “unfortunately they’re requiring a reserve” or “I tried to get them to waive it.” That framing tells the merchant the reserve is a bad thing you failed to prevent, which is exactly the interpretation you’re trying to avoid. The reserve is a normal condition, and your tone should reflect that.

Explaining Why This Merchant Has One

Merchants often want to know why their account carries a reserve when they’ve heard others don’t. This is a fair question and you should be ready for it. A reserve isn’t applied randomly or to everyone. A reserve is applied as a response to something specific about the account. Being able to name the general reason, honestly and without alarm, builds the merchant’s confidence that the decision was considered rather than arbitrary.

The common reasons, in language you can use with a merchant:

• The business collects payment ahead of delivering the product or service. “Because customers pay you now for something they receive later, there’s a longer window where a dispute could come in. The reserve covers that window.” This is the travel, events, memberships, and pre-order situation.
• The account is new and hasn’t built a track record yet. “Once the account has some clean history behind it, that’s the basis for revisiting the reserve. Right now there’s no history to point to yet, so the reserve stands in for it.” This is the honest framing for a startup or a merchant new to card processing.
• The chargeback history has some elevation to work through. “The reserve reflects the dispute activity on the account. As the numbers come down and stay down, that’s what the account gets evaluated on going forward.”
• The vertical carries standard elevated requirements. “Businesses in your category typically carry a reserve as part of how they’re set up. It’s standard for the space, not specific to anything about your business.”

Match the reason to the actual basis for the reserve rather than guessing or making one up. If you’re not sure why the reserve was applied, that’s a question for your SPM before you have the conversation with the merchant, not something to improvise in the moment.

Handling “How Long Until I Get It Back?”

This is the question every merchant asks, and it’s the one where agents most often get themselves into trouble by over-promising.

Here’s the honest situation: reserves are reviewed once the account has built enough clean processing history to evaluate the trajectory, and at that review the decision is made about whether to cap the reserve, begin releasing it, or continue accruing based on how the account is performing. What you should not do is promise a specific date or a specific outcome. The release depends on how the account actually performs, and committing to a timeline you don’t control sets up a broken promise later.

Language that’s honest and doesn’t over-commit:

“The reserve gets reviewed once your account has built up some clean processing history. At that point, based on how the account is performing, the reserve terms get revisited. The best thing you can do to move that along is exactly what you’re already planning to do, and that is to process cleanly and keep disputes low. That track record is what the review looks at.”

That answer is true, it’s reassuring, and it puts the outcome in the merchant’s hands where it belongs. It also doesn’t box you into a date or a promise that the actual review process might not deliver. If the merchant presses for a specific timeline, the honest answer is that you’ll get them the specifics from your SPM rather than guessing, because the timing is handled case by case and you’d rather give them a real answer than a wrong one.

What Not to Say

A few things that consistently make the reserve conversation worse:

• Don’t call it a hold on their money. “Hold” implies they can’t access funds they’re entitled to. The reserve is a cushion that releases back over time, not a freeze.
• Don’t apologize for it or frame it as something you failed to prevent. That tells the merchant it’s a bad outcome. It’s a standard condition.
• Don’t promise a release date or a specific release amount. The review is based on account performance, and you don’t control the outcome. Promising a date you can’t guarantee costs you credibility when it doesn’t happen on schedule.
• Don’t compare it unfavorably to a competitor. “I know Processor X wouldn’t hold a reserve” undercuts the deal you’re trying to close and may not even be true. Plenty of processors would apply the same or stricter conditions to the same account. If a merchant raises a competitor, redirect to the substance of what this account actually needs.
• Don’t guess at the reason. If you don’t know why the reserve was applied, find out before the conversation rather than improvising.

Turning the Reserve Into a Trust-Builder

The best agents use the reserve conversation to strengthen the merchant relationship rather than just survive it. Here’s how.

A reserve conversation handled with confidence and clarity signals to the merchant that you know how this industry works and that you’re guiding them through a normal process rather than scrambling to explain a problem. Merchants take their cues from you. If you treat the reserve as routine, they will too. If you treat it as an awkward thing to apologize for, they’ll treat it as a red flag.

Frame the reserve as part of a relationship that improves over time. The account starts with a certain structure, builds a track record, and the terms get revisited as that track record accumulates. That’s a story about a partnership that gets better as trust is established, which, to be fair, is actually what’s happening. A merchant who understands that arc is far more comfortable than one who thinks the reserve is a permanent condition of doing business.

And be straight with them: the reserve is protecting them too. A merchant who spends every dollar of settled revenue and then gets hit with a wave of chargebacks months later is in a terrible spot. The reserve means the money to cover those disputes is already set aside. You’re not just explaining a processor requirement. You’re actually explaining a structure that keeps the merchant from a cash-flow problem they might not see coming.

A Quick-Reference Script

When you need it fast, here’s the core conversation in one place:

What it is: “A reserve is a small percentage or a capped sum of your settlements held in a separate account to cover any chargebacks that come in after a sale. It’s your money, set aside temporarily, and it releases back to you as your account builds history.”

Why it’s normal: “It’s a standard structure for accounts like yours. It’s not a fee, it’s not a penalty, and it isn’t money you lose.”

Why this account has one: [Name the actual basis — deferred delivery, new account, dispute history, or vertical standard — in plain terms.]

How long: “It gets reviewed once your account has built up clean processing history, and the terms get revisited based on how the account is performing. Clean processing is what moves that along.”

The reassurance: “It’s a cushion that protects you too — it means the money to cover disputes is already set aside, so you’re never caught short after the fact.”

Frequently Asked Questions

Is a reserve the same as a hold on the merchant’s funds? No, and the distinction matters when you’re explaining it. A hold implies the merchant can’t access money they’re owed. A rolling reserve sets aside a small percentage of settlements into a separate account and releases it back over time as the account builds history. The merchant continues receiving the large majority of every settlement; only the reserve percentage is set aside, and even that comes back on a rolling basis.

What’s the difference between a reserve and a pre-fund? A rolling reserve sets aside a percentage of ongoing settlements as a cushion against future chargebacks. A pre-fund is different — it’s an upfront amount, typically associated with new merchants where the account has no history to lean on yet. They address different situations and a well-structured account usually carries one or the other, not both. If your merchant’s terms mention a pre-fund, that’s worth a separate conversation with your SPM about how to frame it, since the “it’s a fraud filter for new accounts” logic is different from the rolling-reserve cushion logic.

Can I tell my merchant exactly when the reserve will be released? No — and you shouldn’t try. The reserve is reviewed once the account has built clean processing history, and the outcome of that review depends on how the account actually performs. Promising a specific date or release amount sets up a broken promise if the timing works out differently. The honest and reassuring answer is that clean processing is what drives a favorable review, which puts the outcome in the merchant’s hands.

My merchant says their current processor doesn’t hold a reserve. How do I respond? Don’t get pulled into a competitor comparison. Different processors structure accounts differently, and the fact that one processor didn’t apply a reserve doesn’t mean the account doesn’t warrant one — it may reflect a different risk appetite, a grandfathered arrangement, or simply a different point in the account’s history. This is the same dynamic that leads a platform like Stripe or Shopify Payments to treat an account differently than a traditional acquirer does, which is worth understanding before you have the conversation. Redirect to the substance: the reserve on this account reflects a specific, explainable basis, and it’s a standard structure for the situation. If the merchant genuinely has clean history and no reserve elsewhere, that’s useful information to raise with your SPM, since a reflexive reserve on a clean established merchant is worth a second look.

What reserve percentage is standard? Reserves typically fall in a narrow band — 5% or 10% of settlements is the common range, calibrated to the specific risk on the account. Higher reserves are uncommon and reserved for genuinely elevated situations. If a proposed reserve seems unusually high for the account, that’s worth raising with your SPM before you take it to the merchant, because an unusually high reserve sometimes signals that a different structure — a reduced approved volume, for instance — would serve the merchant better.

My merchant is upset about the reserve and threatening to walk. What’s my move? First, make sure the framing landed — a lot of reserve resistance comes from the merchant hearing “they’re keeping my money” rather than “this is a temporary cushion that releases back.” Re-explain the mechanic calmly and correct the misconception. Second, if the merchant’s objection is really about cash flow at the reserve percentage, that’s a conversation to have with your SPM, because there may be room to structure the account differently — a different reserve level paired with an adjusted approved volume, for example. Walking away from a workable deal over a reserve the merchant misunderstood is the outcome good framing prevents.

Back