TL;DR: A merchant account reserve is a percentage of your card-processing revenue withheld by your acquirer or processor to cover chargebacks, fraud losses, and refunds. Rolling reserves typically run 5% to 15% of monthly volume held for 90 to 180 days. Funding holds are different: they are short-term, event-triggered freezes lasting 1 to 14 days. Eight triggers determine whether you get a reserve, including your chargeback ratio, industry, average ticket size, and processing history. Processors including PayPal, Stripe, and Square can hold your funds for up to 180 days or longer under their published user agreements. You can negotiate reserve terms every 90 to 180 days, reduce them by cutting chargebacks, and avoid them altogether through proper documentation and fraud prevention infrastructure.
A merchant account reserve is a predetermined amount of a business's processing revenue withheld by an acquiring bank or payment processor in a separate, non-interest-bearing account. The reserve protects the processor against financial losses caused by chargebacks, fraud, or business failure. Think of it as a security deposit for your payment relationship, similar to a landlord's damage deposit or collateral on a business loan, according to Kount (Equifax).
Reserves exist because of a structural risk in card processing. When a customer pays you today, the card network settles the funds to your account within one to two business days. But a chargeback dispute can arrive weeks or months later. If that dispute reverses the transaction and your account has no balance to cover it, your acquirer takes the loss. The reserve is the buffer that prevents that from happening, as explained by Stripe's official reserve FAQ.
A reserve does not stop you from processing payments. Stripe explicitly confirms that reserves do not affect your ability to continue accepting cards. The funds held in reserve are returned to you once the holding period ends, minus any chargebacks or refunds that were drawn from the reserve during that window.
Reserves are different from payment holds in one critical way: reserves are an ongoing, structured arrangement applied to every transaction over a defined period, while a hold is a one-time, event-triggered freeze on specific funds. Understanding that distinction matters because they require different responses. A reserve is negotiated; a hold is resolved through documentation and communication with your processor's risk team.
The size and duration of a reserve depends on factors your processor weighs continuously: your industry, your chargeback ratio, your processing history, your average ticket size, and your financial stability. Chargebacks911 notes that high-risk industries routinely face reserves regardless of their individual track record, simply because the underlying product or business model carries elevated dispute potential.
Not all reserves work the same way. Processors use four primary structures depending on the risk profile of the merchant and the nature of the relationship. Understanding which type you have determines how much capital is tied up at any given time and how quickly it can be released.
| Reserve Type | How It Works | Who Gets It | Capital Recovery |
|---|---|---|---|
| Rolling Reserve | Fixed percentage of each day's sales withheld for 90-180 days, then released on a rolling schedule | Most high-risk merchants; new accounts with elevated risk | Continuous: funds release as they age out of the holding window |
| Fixed / Minimum Reserve | Processor withholds until a set dollar balance is reached; once funded, normal payouts resume | High-volume merchants; accounts with defined liability ceiling | Lump sum released at relationship end or after defined review period |
| Capped Reserve | Rolling reserve with a maximum dollar cap; withholding stops once the cap is met | High-risk merchants; merchant-friendly alternative to uncapped rolling | Released after the rolling hold period expires on capped balance |
| Upfront Reserve | Full reserve amount required at account opening via lump sum or withheld from early settlements | New merchants in very high-risk verticals; travel, ticketing, SaaS | Conditionally released after 90-180 days if account performs well |
The rolling reserve is the most common structure for high-risk merchant accounts. It withholds a set percentage of each day's card sales and holds those funds for a fixed window, most often 90, 120, or 180 days. Each day, a new tranche is withheld and the oldest tranche ages off and releases. TailoredPay describes it accurately: you always have money in transit equal to the hold window multiplied by your daily reserve deduction.
The fixed or minimum reserve requires you to maintain a specific dollar balance in the reserve account at all times. A processor withholds a larger share of early settlements until the balance target is met, after which normal payouts resume. If chargebacks later erode the reserve below the target, withholding restarts until the balance is restored. SyncPal's analysis of PayPal reserves notes that minimum reserves may be held indefinitely until the account demonstrates consistent positive activity.
The capped reserve is a rolling reserve with a ceiling. Withholding continues until the reserve balance reaches a predetermined maximum, at which point the processor stops deducting. SecureGlobalPay notes that caps are typically set at half to one full month of processing volume. The cap makes cash flow planning significantly more predictable, which is why it is often described as the most merchant-friendly structure among the four types.
The upfront reserve collects the full reserve balance at the start of the relationship rather than building it incrementally. Kount identifies three ways merchants can fund an upfront reserve: a direct lump-sum deposit, a transfer from another account, or allowing the processor to withhold all net revenue from early settlements until the target is reached. Upfront reserves are most common in travel, ticketing, subscriptions, and situations where the risk of future chargebacks is high relative to current processing volume.
Processors do not apply reserves arbitrarily. Eight specific triggers determine whether your account gets a reserve, how large it is, and how long it lasts. Knowing these triggers gives you both predictive power and a road map for reducing or eliminating your reserve over time.
1. Elevated Chargeback Ratio. The primary trigger is a high dispute rate. Chargebacks911 notes Mastercard's Excessive Chargeback Merchant threshold sits at a 1.5% rate with more than 100 chargebacks per month. Visa's new VAMP program, which replaced VDMP and VFMP on April 1, 2025, set an initial threshold of 1.5% but tightened it to 0.9% as of January 1, 2026, according to the Merchant Risk Council. Stripe internally flags accounts at a dispute rate of approximately 0.75% to 1%, well below the card network thresholds, per SecureGlobalPay.
2. High-Risk Industry Classification. Certain industries carry an elevated reserve requirement regardless of individual performance. These include travel and ticketing, adult entertainment, CBD and hemp products, nutraceuticals and dietary supplements, online gaming, subscription and recurring billing models, coaching and informational products, and cryptocurrency-related businesses. SwipeSum reports that high-risk accounts typically pay 3.5% to 6.5% plus 20 to 35 cents per transaction, compared to 2.6% to 3.1% plus 10 cents for standard-risk accounts, and carry a 5% to 15% rolling reserve held for three to six months.
3. New Merchant Without Processing History. Even a clean business model can trigger a reserve if there is no track record. Chargebacks911 confirms that new businesses without credit history may face temporary reserves that are removed once perceived risk decreases. TrackiPal's PayPal analysis notes that PayPal applies higher rolling rates to new business accounts until a consistent, successful transaction record establishes authenticity.
4. Sudden Volume Spikes. Unexpected surges in transaction count or average ticket size automatically trigger a fraud review. PayCompass explains that these spikes can resemble patterns associated with compromised credentials or account takeover fraud. Even if the spike is entirely legitimate, such as a product launch or promotional event, the processor may hold funds temporarily. Notifying your processor in advance of planned volume increases can prevent unnecessary holds.
5. High Average Ticket Size. High-value individual transactions carry disproportionate chargeback risk. CatalystPay notes that luxury goods, premium electronics, and travel packages are particularly prone to dispute because a single reversed transaction represents a large dollar liability for the acquirer.
6. Product or Business Model Changes. Changes to your product line, pricing structure, or marketing claims after account approval can trigger a re-underwriting review. SecureGlobalPay confirms that processors review websites and marketing materials for consistency with what customers actually receive. A mismatch between your checkout flow and your advertised terms is one of the most common triggers for mid-relationship reserves and account freezes.
7. Poor Personal or Business Credit. Chargebacks911 lists personal credit history as a direct factor in reserve determinations. PayPal's reserve policy explicitly takes both personal and business credit history into account when calculating rolling reserve rates.
8. Pre-selling and Delivery Delays. Selling products or services in advance of delivery creates a window of chargeback exposure that the processor cannot see into. TrackiPal reports that PayPal specifically cites pre-selling and consistent delivery delays as independent triggers for reserve imposition.
| Trigger | Typical Reserve Response | Resolution Path |
|---|---|---|
| Chargeback ratio above threshold | Reserve imposed or increased; possible account review | Reduce dispute rate below 0.5%; use Ethoca Alerts and Verifi RDR |
| High-risk industry | 5%-15% rolling reserve standard at onboarding | Negotiate after 6-12 months of clean processing |
| New account, no history | Temporary reserve, often 90-day jumpstart | Build 90-day clean track record; request formal review |
| Volume spike (unannounced) | Temporary hold 1-14 days; possible reserve increase | Pre-notify processor; provide documentation of promotion |
| High average ticket size | Higher reserve percentage or upfront reserve | Implement 3DS; require delivery confirmation on high-value orders |
| Business model change | Reserve imposed; possible freeze pending re-underwriting | Proactively disclose changes; update processor before going live |
| Poor credit history | Higher reserve percentage or longer hold period | Provide financial statements; demonstrate operational stability |
| Pre-selling / delayed delivery | Reserve or hold matching the delivery exposure window | Shorten fulfillment timelines; provide tracking data proactively |
Merchants frequently confuse funding holds with reserves, but the two operate differently and require different responses. Understanding the distinction matters because a hold is typically resolved quickly through documentation, while a reserve is a structural change to your payout schedule that requires negotiation over time.
| Feature | Funding Hold | Reserve |
|---|---|---|
| Trigger | Specific event: fraud review, volume spike, new account, large transaction | Ongoing risk profile: industry, chargeback rate, history |
| Duration | 1 to 14 days typically | 90 to 180 days (rolling); indefinite (minimum reserve) |
| Scope | Specific funds or transactions | Percentage of all ongoing settlements |
| Affects processing? | Sometimes; may pause payouts while review is active | No; processing continues normally |
| Resolution method | Submit documentation: invoices, shipping proof, fulfillment records | Demonstrate sustained low-risk behavior over 90-180 days; renegotiate |
| Negotiable? | Limited; processor must complete its review | Yes; after meeting review cycle milestones |
A funding hold is a temporary withholding of specific funds while the processor's risk team investigates a transaction or account event. PayCompass explains the standard hold resolution process: a red flag triggers the hold, the risk team determines whether it is transaction-level or account-level, documentation is requested, and then the funds are released, the account is limited, or the issue is escalated. Providing supplier invoices, fulfillment records, tracking numbers, and shipping confirmations typically resolves a hold in one to fourteen days.
Stripe. Stripe's standard payout schedule moves funds through a pending status before they become available, typically on a two-day rolling basis for U.S. merchants. For compliance reserves under Stripe Connect, the holding periods extend considerably: 10 days in Thailand, 90 days in most countries, and up to two years for certain U.S. connected accounts, per Stripe's account balances documentation. For long-standing negative balances, Stripe may hold platform funds for up to 180 days before transferring them to zero out a connected account's deficit.
PayPal. PayPal's User Agreement explicitly permits holds of up to and in some cases exceeding 180 days when an account breaches its terms, as documented in the Zepeda v. PayPal class action settlement records. PayPal's rolling reserves generally run 30 to 180 days at rates of 10% to 20% for many accounts, according to Synctrack's PayPal reserve analysis. Minimum reserves may be held indefinitely per SyncPal's PayPal funds-in-reserve guide.
Square. During the COVID-19 pandemic in May 2020, Square applied a 30% reserve held for 120 days to merchants it identified as taking prepayments for goods or services to be delivered in the future. ITPro and eSeller365 documented widespread merchant complaints about the policy, with over 1,600 business owners signing a petition against it. Square maintains that it notifies sellers before placing them in the reserve program.
The legal record on processor holds reveals a consistent pattern: merchants often receive insufficient disclosure about why funds are held, how long holds will last, and what actions would lead to release. Three major cases define the enforcement landscape.
| Case / Action | Year | Allegation | Outcome |
|---|---|---|---|
| Zepeda v. PayPal Inc. | 2010-2017 | PayPal froze accounts for 180 days without notice of trigger or remedy pathway; violated EFTA | Near-$4 million settlement; PayPal required to disclose hold reasons and revise User Agreement |
| Square/Block COVID Reserve Controversy | 2020 | 30% reserve held 120 days imposed on small businesses; Mon Ethos filed lawsuit alleging wrongful withholding | Litigation ongoing; Square added disclosures; petition signed by 1,600+ merchants |
| CFPB v. Block Inc. (Cash App) | 2025 | Failed to investigate fraud, used chargeback process in lieu of EFTA obligations, deceived consumers about fraud protections | $75-120 million in consumer redress; $55 million civil penalty; 24/7 live support line required |
| FTC v. Payment Processors (MATCH violations) | 2026 | Processors handled hundreds of millions for MATCH-listed merchants; failed to conduct screening | Contempt motion filed; proceedings ongoing |
Zepeda v. PayPal Inc. (Case No. 5:10-cv-02500 SBA) was filed in the U.S. District Court for the Northern District of California. Plaintiffs alleged that PayPal improperly placed holds and reserves on accounts without notice, failed to disclose what triggered the freeze, gave merchants no opportunity to resolve the triggering condition, and violated the Electronic Fund Transfer Act by not providing monthly statements or error-resolution notices. The court granted final settlement approval on March 24, 2017. The near-$4 million settlement required PayPal to revise its User Agreement, add disclosures about its fraud and risk modeling, and disclose the specific reason for any hold or limitation, according to Top Class Actions.
Block Inc. and Cash App faced CFPB enforcement action on January 16, 2025. The CFPB found that Block failed to provide effective customer service for disputed transactions, failed to prevent and limit fraud, used the card network chargeback process as a substitute for its EFTA obligations, and deceived consumers about fraud protections. The settlement totaled $175 million: between $75 million and $120 million in consumer redress and a $55 million civil penalty, per the CFPB enforcement database. Block was also required to create a 24-hour live consumer service line.
The FTC's 2026 contempt motion against a payment processing operation alleged the processors handled hundreds of millions of dollars for merchants already on Mastercard's MATCH list, helped clients circumvent fraud monitoring programs, and failed to screen high-risk clients adequately, according to FTC attorney reporting. A parallel FTC action against Paddle.com in 2025 resulted in a $5 million settlement for processing payments for businesses selling deceptive tech support software under Paddle's own merchant name, per All About Advertising Law.
The pattern across all cases is the same: merchants did not know why funds were held, how long the hold would last, or what they could do to end it. That lack of disclosure is now the primary legal and regulatory vulnerability for processors, and it gives merchants a framework for demanding transparency when a reserve or hold is imposed.
Reserve calculations are straightforward once you understand the rolling structure. The formula is: monthly processing volume multiplied by the reserve percentage multiplied by the hold period in months equals the maximum capital permanently tied up at any point in time.
Here is a complete worked example based on a merchant processing $100,000 per month with a 10% rolling reserve held for 90 days (three months), per TailoredPay:
If the same merchant had a 180-day hold period instead of 90 days, the steady-state capital tied up would double to $60,000. This is why hold period is as important as reserve percentage when evaluating your true cash impact. A 5% reserve at 180 days ties up the same capital as a 10% reserve at 90 days on equivalent volume.
For a business in the adult entertainment vertical processing $30,000 per month with a 10% reserve and 180-day hold, the steady-state reserve reaches $18,000 constantly held, per MyntPay's adult payment processing guide. That is nearly 60% of a single month's revenue in perpetual lockup.
| Industry | Typical Reserve Rate | Hold Period | Capital Tied Up on $100k/month |
|---|---|---|---|
| CBD / Hemp | 5%-10% | 60-90 days | $10,000-$30,000 |
| Dietary Supplements / Nutraceuticals | 5%-15% | 90-180 days | $15,000-$90,000 |
| Adult Entertainment | 5%-20% | 90-180 days | $15,000-$120,000 |
| Travel and Ticketing | 10%-20% | 90-180 days | $30,000-$120,000 |
| Coaching / Informational Products | 5%-15% | 90-180 days | $15,000-$90,000 |
| SaaS / Digital Goods | 5%-10% | 90 days | $15,000-$30,000 |
| General High-Risk | 5%-15% | 90-180 days | $15,000-$90,000 |
| Standard / Low-Risk | 0% | N/A | $0 |
The capital-tied-up calculation matters beyond cash flow planning. If your processor is holding $30,000 of your working capital, that $30,000 has an opportunity cost. It cannot fund inventory, advertising, payroll, or growth. Over a 12-month rolling period, the cumulative impact of a 10% reserve on a growing business can significantly constrain expansion, which is why reducing your reserve percentage and hold period should be an active operational goal, not a passive hope.
Discovering your processor has placed you on a reserve can feel alarming. The right response is systematic, not reactive. TFM Law's reserve guide outlines five immediate steps.
After stabilizing the immediate situation, begin the negotiation process. Chargebacks911 confirms that reserve terms are negotiable. Processors may reconsider if you present a documented track record of reduced chargebacks, increased volume, and improved security measures. Request periodic reviews every three to six months. The most effective negotiating moments come after completing at least one full review cycle with measurable improvement, per ChargebackHelp.
When negotiating, propose concrete structural alternatives rather than simply asking for reduction. ChargebackHelp recommends proposing: a lower reserve percentage, a shorter rolling hold period, or a capped reserve structure that stops growing once a defined balance is reached. Each of these is less aggressive than the current structure while still providing protection for the processor.
On the technical side, two tools directly address the chargeback ratios that drive reserve decisions. Ethoca Alerts (Mastercard) delivers real-time dispute notifications from card issuers before chargebacks are filed, preventing 35% to 45% of potential chargebacks when merchants issue refunds within the alert window, according to 2Accept's chargeback alert comparison. Verifi RDR (Visa) automatically resolves qualifying Visa disputes using merchant-defined rules in approximately three seconds, preventing 71% of Visa disputes without manual intervention, per the same source. Implementing both tools, combined with 3D Secure authentication, directly addresses the metrics processors use to justify reserve levels. Chargeback.io reports that 3DS reduces fraud-related chargebacks by up to 70% and shifts liability for Card-Not-Present fraud to the card issuer.
If legal remedies become necessary, TFM Law identifies four escalation paths: contract review and dispute resolution, demand letter or mediation, civil lawsuit for wrongful withholding, and regulatory complaints filed with the FTC or CFPB. Most processor agreements include mandatory arbitration clauses that limit class action participation, a structure upheld by the U.S. Supreme Court in AT&T Mobility LLC v. Concepcion (2011), per SGR Law. Individual arbitration remains available to most merchants, but the cost-benefit calculation is challenging for smaller reserve amounts.
Prevention is more effective than negotiation. Five practices materially reduce the probability of a reserve being imposed at account opening or triggered mid-relationship.
Build processing history before scaling. Without a prior processing record, even a low-risk business can face a precautionary reserve. Using a secondary processor at lower volumes to establish a track record before migrating full volume to a primary account reduces reserve risk. CreditHubAccess recommends notifying your processor in advance of any planned volume spike. After six to twelve months of maintaining chargeback ratios below 0.5%, you have leverage to negotiate reserve reductions, per MyntPay. Many acquirers offer reserve reviews after just 90 days of clean processing, according to SwipeSum.
Implement clear refund and cancellation policies. Most consumer-initiated chargebacks stem from billing confusion, unclear cancellation processes, or unmet delivery expectations. Making cancellation easy, sending pre-billing notifications for subscriptions, and honoring cancellation requests immediately all reduce the dispute rate that drives reserve determinations. ChargebackHelp confirms that even modest improvements in these areas produce measurable chargeback reductions.
Disclose your business accurately at onboarding. Mismatches between your merchant application and your actual business model are a direct trigger for re-underwriting and reserve imposition. TFM Law recommends keeping an accurate record of all settlements and reserve reports, and conducting periodic compliance checks to ensure your Merchant Category Code (MCC) matches your actual business activity. Durango Merchant Services advises providing up-to-date financial statements, tax returns, and business licenses proactively rather than waiting for processors to request them.
Use multiple processors. Running two or more payment processors simultaneously protects against both holds and account freezes. If one processor freezes your account, you continue processing through the other. TFM Law recommends this approach specifically for businesses operating in high-risk categories. Having a secondary processor already integrated means a one-hour response to a freeze instead of a weeks-long scramble to rebuild your checkout flow.
Deploy anti-fraud infrastructure from day one. Address Verification System (AVS) checks, CVV verification, velocity limits on transaction frequency, IP geolocation matching, and 3D Secure authentication all reduce fraud signals that trigger reserves. CreditHubAccess recommends implementing these tools before scale, not as a reactive measure after a reserve has been imposed. A processor that sees a well-instrumented risk environment at onboarding is less likely to impose a precautionary reserve than one that sees no fraud controls in place.
Reserves and holds sit at the intersection of card network rules, federal law, and state consumer protection statutes. Four regulatory frameworks shape what processors can and cannot do.
Visa VAMP. Visa's Acquirer Monitoring Program (VAMP) replaced VDMP and VFMP on April 1, 2025, with an advisory period through September 30, 2025 and enforcement beginning October 1, 2025. The VAMP Ratio threshold was set at 1.5% initially and tightened to 0.9% as of January 1, 2026, per the Merchant Risk Council. VAMP also tracks an Enumeration Ratio; accounts where 20% or more of transactions are flagged as attempted enumeration attacks are classified as high-risk. Merchants who breach VAMP thresholds trigger mandatory acquirer-level responses, which almost always include reserves, per Solidgate's VAMP analysis.
Mastercard ECM. Mastercard's Excessive Chargeback Program (ECP) maintains two tiers. The Excessive Chargeback Merchant (ECM) tier applies at a 1.5% chargeback rate with more than 100 chargebacks per month. The High Excessive Chargeback Merchant (HECM) tier applies at 3% or more with 300 or more chargebacks per month. Merchants in the ECM program pay $1,000 per month in fees, with escalating penalties and standard termination at 1.5% or higher sustained for three months, according to Chargebacks911.
MATCH List. Mastercard's Member Alert to Control High Risk Merchants (MATCH) database contains terminated merchant files. All payment processors must check MATCH when onboarding any new merchant, per Stripe's MATCH documentation. A MATCH listing typically lasts five to seven years and bars the listed merchant from obtaining a standard merchant account during that period, per Performance Card Service. Excessive fraud is defined for MATCH purposes as a fraud-to-sales dollar volume ratio of 8% or greater in a calendar month, combined with 10 or more fraudulent transactions totaling $5,000 or more, according to Easy Pay Direct.
EFTA, Regulation E, and UDAAP. The Electronic Fund Transfer Act requires payment platforms to investigate and resolve disputes about unauthorized transactions promptly. The CFPB used EFTA violations as the primary basis for its enforcement action against Block Inc., as documented on the CFPB's enforcement page. The Dodd-Frank Act's UDAAP provisions prohibit payment processors from engaging in unfair, deceptive, or abusive practices. The NCUA's UDAAP guide defines unfair acts as those causing substantial injury that is not reasonably avoidable. Merchants can file UDAAP complaints with state attorneys general when processors impose reserves in violation of contract terms or without adequate disclosure. Regulation II under Dodd-Frank governs debit interchange and applies to issuers with $10 billion or more in assets, as detailed by the Federal Reserve.
Not every reserve resolves through negotiation. Some reserves reveal a fundamental misalignment between your business model and your current processor's risk appetite. Knowing when to stay and when to move is a strategic decision, not a reactive one.
Temporary reserves have defining characteristics: they were applied at account opening with a defined end date, the processor offers reviews every 90 to 180 days, the release conditions are specified in writing, and your chargeback ratios have been declining. ChargebackHelp and TFM Law both describe this as a standard, manageable reserve relationship that rewards improved performance with reduced terms.
Permanent or problematic reserves show different signals. The reserve terms were never defined in writing. The processor keeps extending review periods without milestones. The reserve percentage increased without explanation. After six or more months of clean processing history, the processor refuses to engage in renegotiation. The processor cannot produce documentation for why the reserve exists. ECS Payments describes several additional red flags: unexplained payout delays beyond the stated settlement period, inability to reach a dedicated account manager, and unilateral mid-contract reserve increases.
Stripe's published policy notes that in some cases a reserve may be required indefinitely to support a business on Stripe. A few days before a reserve expires, Stripe conducts another credit review; if it identifies continued elevated risk, the reserve is extended, per Stripe's reserve FAQ. For businesses in verticals that Stripe classifies as restricted, such as online coaching and informational products, a reserve may be a symptom of a deeper policy incompatibility that no amount of clean processing history resolves.
If the decision to switch is made, several transition rules apply. Ensure your current reserve will be released on its existing schedule before closing the account. Avoid abrupt closure. Allow the new processor to review your account before migrating full volume, and build processing history at the new processor gradually. Beyond Bancard's switching guide recommends having a parallel integration running at the new processor before reducing volume at the current one. Explore payment processor options that specialize in your vertical and have explicit, documented reserve policies for businesses with your risk profile.
A rolling reserve withholds a percentage of every transaction on an ongoing basis, with funds releasing on a rolling schedule as they age past the hold window, typically 90 to 180 days. A fixed or minimum reserve requires you to maintain a specific dollar balance in the reserve account at all times. Once a rolling reserve's funds age out, they release automatically. A fixed reserve balance is held until the processor's review determines the balance is no longer needed, which may take substantially longer. SecureGlobalPay provides worked examples of both structures.
Legally, processors can hold funds for as long as their user agreements permit, and most reserve the right to extend holds at their discretion. PayPal's User Agreement explicitly allows holds of "up to and in some cases exceeding 180 days" for accounts that breach its terms, as documented in the Zepeda v. PayPal settlement. Stripe states that in rare cases a reserve may be required indefinitely, per Stripe's FAQ. The regulatory limit on how long funds can be held without cause is contested territory, and the CFPB's action against Block Inc. suggests that indefinite holds paired with insufficient disclosure are vulnerable to enforcement action.
Yes, reserves are negotiable. Chargebacks911 confirms that processors reconsider reserve terms when merchants demonstrate consistent low-risk performance. Request a formal review every three to six months. Present documented evidence of reduced chargeback ratios, improved dispute resolution times, and enhanced fraud prevention tools. Propose specific structural alternatives: a lower percentage, a shorter hold period, or a capped arrangement. Mentioning competitive offers from other processors, tactfully and professionally, also strengthens the negotiating position.
A Stripe reserve is applied proactively based on risk profile and does not stop you from processing payments. A Stripe account freeze is a more severe action that typically involves full suspension of payouts and sometimes processing. Freeze triggers include dispute percentages above approximately 0.75% to 1%, selling products on Stripe's restricted business list, sudden unannounced volume spikes, or discrepancies between marketed products and actual delivery, per SecureGlobalPay's Stripe freeze guide. Stripe's algorithm may detect policy violations even in accounts that were initially approved, particularly for online coaching and informational product businesses.
If your account is closed voluntarily, the reserve is typically held for the remainder of the stated hold period before being released to you, minus any chargebacks or refunds processed during that window. If the account is terminated by the processor, the reserve may be held for a longer period at the processor's discretion, particularly if the termination was related to fraud or policy violations. Abrupt account closures can complicate and extend the release timeline, which is why TFM Law recommends against closing an account while a reserve is active unless there are clear legal grounds to do so. Merchants terminated for chargeback violations may also be placed on the MATCH list, which prevents them from obtaining a standard merchant account for five to seven years, per Stripe's MATCH documentation.