Few things stop a small business faster than logging in and seeing that your deposits are on hold. Payroll is due, suppliers need to be paid, and the money from sales you already made is suddenly out of reach.
Funds freezes feel random, but they almost never are. Processors hold money when they think they may be on the hook for future chargebacks or fraud. Once you understand what triggers a hold, most of them are avoidable.
Why processors hold your money at all
When a customer disputes a card charge, the money comes back out of the merchant's account. If the merchant can't cover it, because they've closed, run out of cash or disappeared, the processor and its bank are left paying. A hold or reserve is the processor's way of keeping enough money on hand to cover that risk.
Regulators are also watching how processors manage risk. In September 2026, the FTC announced a $4.85 million settlement with Nuvei that requires stronger merchant screening and extra investigation when a client's chargebacks rise above set levels, and a proposed $12 million settlement with Humboldt Merchant Services over merchant accounts opened for shell companies. Actions like these give every processor good reason to keep a close eye on chargebacks and account changes.
The three kinds of holds
- A hold on specific deposits. The processor pauses one or more payouts while it reviews unusual activity. These are usually short and end once you provide the information requested.
- A reserve. The processor keeps a portion of your sales for a set period. A rolling reserve, for example, holds a percentage of each day's sales and releases it months later. Some reserves are a fixed amount collected up front or built up over time.
- A termination hold. If an account is closed, the processor may keep funds for months afterward to cover chargebacks that arrive after the account ends. Your merchant agreement should spell out how long.
The most common triggers
- A sudden jump in volume. If you normally process $20,000 a month and suddenly run $80,000, the processor sees risk, even if it's a great month.
- Tickets far above your normal size. A business approved for $150 average sales that suddenly runs $5,000 charges will get attention.
- Rising chargebacks or fraud reports. Disputes are the number-one trigger. Card network programs like Visa's VAMP put pressure on processors to act early. Our guide to Visa's 1.5% VAMP threshold explains how that ratio works.
- Selling something you didn't disclose. If your application said "wellness products" and you're selling peptides, or you added a new product line without telling your processor, a review can lead to a hold or closure.
- Long delivery times or pre-orders. Taking payment today for something delivered in three months increases the risk window for disputes.
- Lots of refunds or keyed-in cards. Unusual refund patterns and heavy manual entry can look like fraud.
- Missing or outdated information. Expired documents, a changed bank account or ownership changes the processor doesn't know about can pause payouts.
Why fast-approval accounts sometimes freeze later
Many app-based payment services let you start accepting cards within minutes, with limited upfront review. That speed is convenient, but the risk review often happens after you're already processing. If the provider later decides your business doesn't fit its rules, holds or closures can follow.
A traditional merchant account works the other way around: the business is reviewed before approval, and reserve terms, if any, are agreed in advance. For industries that providers consider higher risk, that upfront review is usually the difference between stable processing and repeated shutdowns.
How to avoid a freeze
- Be complete and accurate on your application. Describe exactly what you sell, how you deliver it and your expected volume and average ticket.
- Give your processor a heads-up. Before a big promotion, a large order or a seasonal spike, call or email them first.
- Keep disputes low. Use a recognizable billing descriptor, clear refund policies and responsive customer service.
- Keep records ready. Invoices, contracts, delivery tracking and customer communications resolve most reviews quickly.
- Read the reserve and termination sections of your agreement before you sign, so nothing is a surprise later.
- Check your statements. New fees or reserve lines can be early warnings. Our guide to reading your processing statement shows where to look.
If your funds are already frozen
Stay calm and stay in contact. Ask your processor, in writing, why the funds are being held, what documents they need and when you can expect a decision. Send what they ask for promptly and keep copies. Avoid opening a new account with incomplete or inaccurate information to get around the hold; that can make things much worse, including landing your business on the card networks' terminated merchant list.
If you're in an industry where holds keep happening, it may be time for a processor that underwrites your business properly from the start. Our high-risk merchant accounts are set up for exactly that, including payment processing for peptide businesses. For in-person sales, a compliant dual pricing program can also eliminate processing fees; here's how dual pricing works.
Dealing with holds, reserves or high fees? Send us your most recent processing statement for a free savings analysis. We'll review your account terms and fees and show you your options, with no obligation.
This article is for general information and isn't legal advice. Hold and reserve terms vary by processor and agreement; review your merchant agreement and talk with your processor or attorney about your situation.
Related guides
Visa's 1.5% Chargeback Threshold (VAMP): How to Stay Under It
Since April 2026, Visa can flag U.S. merchants at a 1.5% fraud and dispute ratio. Here's how VAMP is calculated and how to stay well under it.
What Is Dual Pricing? A Complete Guide for Business Owners
Dual pricing shows two prices for every item — one for cash, one for card — so the cost of card acceptance stops eating your margin. Here is how it actually works at the register.
