Why your processor is holding your money, and what the contract actually says
Payment Review Editorial Team
Payment Review Editorial Team

Money you have already taken has not arrived. Support says it is a hold. Your statement says reserve. The dashboard says pending, and nobody will tell you a date. This is one of the most common things that goes wrong between a business and its payment processor, and most of the confusion comes from a single fact: three completely different mechanisms share the same vocabulary, and they have three different cures.
What follows is what the card network requires a real acquirer's contract to say about reserves, and what the agreements you actually signed with the big payment facilitators say instead. The difference is larger than most merchants realise, and it is the strongest practical argument for graduating off an aggregator once your volume justifies it.
Work out which of these is happening before you do anything else. The wrong remedy simply wastes the week.
Visa's Ecosystem Risk Programs Guide, the October 2024 document that sets out the acceptance risk standards acquirers are measured against, makes exposure mitigation a mandatory control. An acquirer's contract with a merchant has to contain a clause covering reserves, guarantees and account- or transaction-level holds. And where the acquirer uses merchant reserves, the standard says it must explain that these are collateral that are property of the merchant, held and controlled by the acquirer in a unique deposit account in the merchant's name, or by other means that keep the funds segregated.
That is the strongest sentence a merchant has in this whole area, and almost nobody knows it exists. Property of the merchant. Segregated. Disclosed in the contract, in advance, with the reconciliation process explained.
The same standards require an acquirer to fund a merchant promptly after transactions clear, less any reserve funds accumulated to secure the merchant's obligations, and permit settlement to be retained to offset disputes or losses tied to that merchant. They also tell acquirers to write into the merchant agreement which actions they may take when credit-risk monitoring flags something — changing reserve requirements, adding holds on funds, conducting further review — and they contemplate conditional approval at underwriting, where an application is approved with reserves, holds, limits on business activity or guarantees attached from day one.
None of that is an ambush. It is machinery that is meant to be visible in the contract before you sign it. If you have a dedicated merchant account and cannot find that clause, that is the first thing to ask about.
Stripe, Square and PayPal are payment facilitators. You are boarded under their master merchant agreement rather than given your own acquirer relationship, which is exactly why signup takes minutes. Their reserve terms are correspondingly one-sided, and all three publish them.
Under the Stripe Financial Services Terms, part of the Stripe Services Agreement and last modified on 18 November 2025, Stripe may establish a Reserve and will notify you of its terms in a document it calls a Reserve Notice. Stripe has sole control of the reserve. You have no legal or equitable right or interest in it and no claim on any earnings it generates, and you cannot draw funds from it. Stripe releases money from the reserve only if, and to the extent that, it is satisfied the relevant risk exposure has been mitigated. It may change the reserve terms if it believes the underlying risk has changed or a financial provider requires it, and it may fund and replenish the reserve using funds you provide on request, funds it owes you for transactions, or debits to your bank account.
There is no ceiling in that text, no stated duration, and the release test is Stripe's own satisfaction.
Square's Payment Terms, last updated 30 July 2026, are blunter still. Square may withhold funds by temporarily suspending or delaying payouts, and may require you to keep an amount in a reserve, and it states that it may require a reserve for any reason related to your use of the services. The amount is whatever Square reasonably determines will cover potential losses to Square, and it may be raised, reduced or removed at any time in Square's sole discretion, based on payment history, a credit review, an award or judgment, or otherwise as Square or its processor may determine. You grant Square a security interest and a lien over the funds, and authorise withdrawals from the reserve or any linked bank account without prior notice.
PayPal's user agreement, last updated 1 September 2026, is the most specific of the three about mechanics, which makes it genuinely useful reading even if you do not use PayPal. It describes two categories. A rolling reserve holds a percentage of each day's receipts and releases it on a schedule; the worked example in the agreement is 10 per cent held for a 90-day rolling period, so day one's 10 per cent comes back on day 91. A minimum reserve is a fixed amount you must keep available, taken either as an upfront deposit or accumulated from a percentage of sales until it is reached. Both can apply at once.
PayPal also lists what it weighs: how long you have been in business, whether your industry has a higher likelihood of chargebacks, your 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. It commits to notifying you of the reserve terms, and again if it changes them.
Separately from reserves, PayPal describes risk-based holds on individual payments. Those generally remain in place for up to 21 days from the date the payment was received, may be released earlier at PayPal's sole discretion — uploading shipment tracking is the example the agreement gives — and may last longer if the payment is challenged.
Reserves are a credit decision, not a punishment, and the trigger is almost always one of five things.
A reserve is a normal condition of acceptance in restricted categories, and by itself it says nothing bad about a provider. The warning signs are different: reserve terms nobody will put in writing, a release date that keeps moving, funds not segregated on an account that is supposed to be a real merchant account, or a hold with no stated end on a business that ships the same day. If a termination follows, what lands you on the terminated merchant file matters more than the money in the reserve, because it is the thing that follows you to the next application.
If your category attracts reserves as a matter of course, the useful comparison is between specialists rather than between an aggregator and a specialist. Our reviews of PaymentCloud, Durango Merchant Services, Soar Payments and Easy Pay Direct set out pricing, contract terms and what each one discloses about reserves and holds, and the guide to high-risk merchant accounts sets them side by side. If you are low-risk and ship promptly, reserves should be rare and pricing is the thing to shop instead — Helcim and Dharma Merchant Services both publish their margins, and how to read a merchant processing statement will tell you what you are paying now.
The single most useful habit is to read the exposure clause before you sign rather than after the money stops. It is in every one of these agreements, it is free to read, and it is the only document that will tell you what your provider is allowed to do next — which is also why the debanking rule that took effect this June changes less for merchants than the headlines suggested: your position here is contractual, not supervisory.