Payment Processor Disputes — Stripe, PayPal, Square Holds & Freezes (2024 Edition)

I publish illustrative scenarios prepared by my practice. All participants and conversations are fictional. The fictional posts are not posts by real users, accounts of client experiences, or reports of actual results.
Illustrative scenario prepared by my practice. · Featured scenario
For informational purposes only. Payment processor terms vary and change frequently. Consult a licensed attorney for advice specific to your situation.
Hypothetical question

This thread covers:

  • Stripe reserve holds — rolling reserves, sudden balance holds, and how to get funds released
  • PayPal 180-day freezes — account limitations, frozen funds, and escalation strategies
  • Square account terminations — sudden shutdowns, appeals process, and alternatives
  • Chargeback disputes — evidence requirements, representment strategies, and win rates
  • Regulatory complaints — CFPB, state AG, and money transmitter licensing issues

Related threads you should also read:

Key advice summary (details in thread below):

  • Document everything — every email, chat transcript, and phone call with your processor
  • Know your rights under state money transmitter laws and federal regulations
  • File CFPB complaints early — they have been effective in forcing resolutions
  • Never keep all your operating capital in a single payment processor
  • Consider your alternatives and build redundancy before you need it
  • Read your processor's terms of service carefully — especially the arbitration clause and the reserve/hold provisions

Please keep this thread on-topic.

Illustrative response

PayPal froze my account with $8,200 in it — money from legitimate freelance writing clients. Their reason? "Suspicious activity." The suspicious activity was a single $3,500 payment from a new client (a marketing agency) that I'd been corresponding with for weeks.

PayPal's "resolution center" was a nightmare. They asked me to upload invoices, contracts, and proof of delivery. I did all of that within 48 hours. Then... nothing. For three weeks. When I finally got through to someone on the phone, they said my case was "under review" and they couldn't provide a timeline.

Meanwhile, I had rent due and couldn't access my own money.

What finally worked:

  • Filed a CFPB complaint (complaint #XXXXXXX) describing the timeline and impact
  • Filed a complaint with the Nebraska Department of Banking & Finance (PayPal is licensed in Nebraska as a money transmitter)
  • Sent a demand letter via certified mail to PayPal's legal department citing Nebraska's Uniform Money Services Act

Got a call from PayPal's "executive escalations" team 6 weeks after the freeze. Account was fully restored with an apology. No explanation for why it was flagged in the first place.

I've since moved my primary payment processing to Stripe and only keep PayPal as a backup with minimal funds in it.

Illustrative response

Treasury Management 101 for Anyone Using Payment Processors

A business relies on a single payment processor, that processor freezes funds or imposes reserves, and suddenly the business can't make payroll. Here's how to protect yourself:

  1. Your primary account should be a real business bank account — not a processor. Set up daily or weekly automatic sweeps from your processor to your bank. Don't let funds sit in Stripe/PayPal/Square.
  2. Use at least two processors — Stripe + PayPal, or Stripe + Square, or a dedicated merchant account + one of the big three. If one goes down, you can route to the other within hours.
  3. Keep 2-3 months of operating expenses in your bank account — not in your processor. This is your buffer if funds get frozen.
  4. Set up ACH/wire as a backup payment method — especially for large invoices. Direct bank transfers bypass processors entirely.
  5. Monitor your chargeback ratio weekly — if it's creeping above 0.5%, take immediate action. Both Visa and Mastercard have monitoring programs that kick in at 0.9-1.0%, and processors will act even sooner.

The businesses I work with that follow these rules have never been seriously impacted by a processor freeze. The ones that don't follow them are the ones calling me in a panic.

For more on structuring payments for your business, see the related thread: ACH vs wire for large payments.

Illustrative response

Square straight-up terminated my account. No warning, no appeal, no explanation beyond "your account has been deactivated due to activity that violates our Terms of Service." I'm a personal trainer who takes payments for training sessions. Nothing remotely shady.

They held $2,300 in pending payouts for 90 days. When I called, they literally said they couldn't tell me what I did wrong because of "security reasons." How am I supposed to fix something if you won't tell me what the problem is?

Has anyone successfully appealed a Square termination? I saw the thread about Square alternatives but I'm still trying to get my money back first.

Illustrative response

Square terminations are unfortunately very common and very hard to reverse. The thread Kelly linked above has good alternatives. For your frozen funds, file a CFPB complaint immediately. Square typically releases held funds within 90 days of termination but a CFPB complaint can accelerate it.

On the broader topic of chargebacks, since that's been coming up a lot: the #1 mistake I see businesses make is not responding to chargebacks with enough evidence. Here's what you need for a strong representment:

  • Proof of delivery — tracking numbers, signed delivery confirmations, or for digital goods, access logs showing the customer used the service
  • Communication records — emails, chat logs showing the customer acknowledged receiving the product/service
  • Your refund/cancellation policy — as it was presented to the customer at time of purchase
  • Transaction details — AVS match, CVV match, IP geolocation matching the billing address
  • Prior transaction history — if the customer has made successful purchases before

See also: What evidence do I need for a chargeback dispute?

Illustrative response

CFPB Developments and the Class Action Landscape (January 2024 Update)

A few important legal developments to be aware of:

1. CFPB's Larger Participant Rule for Payment Processors

The CFPB finalized its rule in late 2024 defining "larger participant" thresholds for general-use digital payment applications. This means the CFPB now has direct supervisory authority (not just enforcement authority) over companies like PayPal, Venmo, Cash App, and similar services that process more than 5 million transactions annually. This is a significant shift — the CFPB can now conduct examinations and audits, not just respond to complaints.

2. Growing Class Action Activity

We're seeing a wave of class action lawsuits against payment processors. Key cases to watch:

  • Rodriguez v. PayPal Holdings, Inc. — putative class action in the Northern District of California alleging PayPal's fund-hold practices violate California's Unfair Competition Law (Bus. & Prof. Code 17200) and constitute conversion of funds
  • Multiple arbitration proceedings against Stripe regarding reserve practices — while these are individual (due to the class action waiver), the pattern is growing
  • Fintech Merchants Coalition v. Square, Inc. — alleging Square's termination practices violate implied covenant of good faith and fair dealing

3. State-Level Action

California, New York, and Illinois have all introduced legislation that would impose specific requirements on payment processors regarding fund holds — including mandatory notice periods before imposing reserves and clear appeals processes for account terminations. None have passed yet, but the trend is clear.

My advice: if you've been affected by a processor freeze or hold, document everything meticulously. Even if you resolve your individual case, your records could be useful if a class action moves forward.

Illustrative response

Something that doesn't get discussed enough: when a processor flags or terminates your account, they often share that information with other processors through databases like MATCH (Member Alert to Control High-Risk Merchants), formerly known as the TMF (Terminated Merchant File).

If Stripe or Square terminates you and places you on the MATCH list, you may have difficulty getting approved by any major processor for up to 5 years. This is why it's important to resolve disputes before they escalate to termination.

You have a right to know if you're on the MATCH list. Under the Fair Credit Reporting Act (FCRA), if you're denied a merchant account, the processor must tell you why. If it's because of a MATCH listing, you can dispute it. The listing processor is required to investigate and correct inaccurate listings.

Also, if a processor places you on MATCH without valid reason (the list of valid MATCH reason codes is defined by Mastercard), that's a potential FCRA violation and you may have a claim for damages.

Illustrative response

Question for the attorneys: is there a statute of limitations on these claims? I had $6,000 held by PayPal back in 2024 and eventually gave up trying to get it back. They said the funds were "forfeited" under their Acceptable Use Policy. Is it too late for me to do anything?

Illustrative response

It depends on your state and the specific claim, but you likely still have time. In California (where PayPal is based and where you appear to be located), the statute of limitations for breach of contract is 4 years (Cal. Code Civ. Proc. 337), and for conversion of funds it's 3 years (Cal. Code Civ. Proc. 338(c)).

If this happened in 2024, you're likely within both windows. A few things to consider:

  • PayPal cannot simply "forfeit" your funds unless they have a specific legal basis (e.g., fraud, illegal activity, or a specific contractual provision that has been validly agreed to)
  • Many states have unclaimed property laws that require companies to escheat (turn over) abandoned funds to the state — PayPal can't just keep your money indefinitely
  • Check your state's unclaimed property database — your funds may have been turned over to the state controller

I'd recommend filing a CFPB complaint as a first step, even this late. It costs nothing and often prompts a response.

Illustrative response

From the technical side: if you're running a business on Stripe, you should be monitoring your Stripe Radar score and dispute rate programmatically. Here's what we do:

  • Webhook listener for charge.dispute.created events — sends immediate Slack alert to our finance team
  • Daily automated report on chargeback ratio (trailing 30 days)
  • Alert if any single transaction exceeds 3x our average transaction size (these are the ones most likely to trigger risk reviews)
  • Automated evidence submission for common dispute types using Stripe's Dispute API

The key is catching problems before they trigger Stripe's risk system. By the time you get that email saying "we're placing a reserve on your account," the automated system has already made its decision and reversing it is an uphill battle.

Prevention is 10x easier than cure with payment processors.

Illustrative response

I want to flag something from the HR/payroll side that doesn't get enough attention. If your payment processor freezes your funds and that causes you to miss payroll, you have a serious legal problem on your hands — potentially worse than the freeze itself.

In most states, failing to pay employees on their regular payday is a violation of state wage and hour laws, regardless of the reason. In California, the penalty is a full day's wages for each day payment is late (Labor Code 203). In New York, there are criminal penalties for willful failure to pay wages.

This is why Lisa's advice about keeping 2-3 months of operating expenses in your bank account is so critical. Payroll should never — ever — depend on timely access to processor funds.

I've seen two businesses this year where a Stripe freeze caused a missed payroll cycle. Both ended up settling with employees in addition to dealing with the processor issue. Don't let this happen to you.

Related Resources

→ All Payment Processor Demand Letters → PayPal Fee Calculator → Stripe Reserve Calculator
Illustrative response

Pro tip: if your payment processor tells you "funds will be available in 90-120 days," that's usually a rolling hold. New transactions extend the clock. Stop processing through that account immediately.

Illustrative response

This is exactly why I started documenting everything from day one.

Illustrative response

Bumping this because it just happened to me. Stripe dropped a 30% rolling reserve on my account after one customer disputed a $900 order. I'm a two-person print shop, not a high-risk business. The reserve email said it was based on 'projected dispute exposure,' whatever that means.

Reading through the thread now. Sounds like the CFPB complaint is the move. Did anyone get a faster result going to their state regulator instead of CFPB, or is CFPB really the best first step?

Illustrative response

I did both at the same time and honestly CFPB got the response. My state DFPI complaint (I'm in California) took weeks just to get acknowledged. The CFPB portal forces the company to respond on a clock, which is the whole point.

One tip: in the CFPB narrative, lead with the dollar amount and how long it's been held, then the business impact. Keep it factual. The ones I've seen get fast results read like a timeline, not a rant.

Illustrative response

PayPal hit me with the 180-day hold last week. $4,100. The thing that gets me is they keep saying 'after 180 days you can withdraw,' like that's a resolution. That's just them holding my money for half a year and then giving it back.

Is the 180 days an actual hard rule or can it be shortened with documentation? I uploaded invoices and delivery proof already.

Illustrative response

Question for the group: my Stripe reserve is structured as a rolling reserve, so every day new money goes in and old money is supposed to roll out 90 days later. But it doesn't feel like anything is actually rolling out. How do you even audit that?

I exported the balance report and it's a mess of line items. Has anyone reconciled a rolling reserve to confirm the processor is actually releasing on schedule?

Illustrative response

For anyone with international clients: I switched everything to bank wire and Wise after my freeze. Slower, but no holds, no 180-day surprises. The fee on a Wise transfer is way less than having $5K locked up for six months.

PayPal absolutely flags new + international + larger-than-usual as a combo. That's the trifecta that froze mine too.

Illustrative response

The redundancy post earlier in this thread convinced me. We just finished wiring up a second processor as failover. Took the engineer about a week. If you're running a subscription business and you'd miss payroll from one freeze, this is not optional anymore.

Side note: we also moved annual plans to ACH. No chargebacks on ACH and the funds don't sit in a processor reserve. Wish we'd done it two years ago.

Illustrative response

Day 1 of my Stripe freeze, posting so I can come back and update later. $22,000 held. Reason given: 'review of account activity.' We sell event tickets, so a big spike before an event is normal for us but apparently looks scary to their risk model.

Filing the CFPB complaint tonight. Will report back on timing.

Illustrative response

Does filing a CFPB complaint ever backfire? Like, has anyone had a processor close their account in retaliation for complaining? That's my fear, I still need the account for daily sales.

Illustrative response

I worried about the same thing. In my case nothing happened to the account after the complaint, it just got the held money released. But I'd be lying if I said retaliation never happens, processors can close accounts at will under their terms.

My personal approach was to get a backup processor live first, so if they did close me I wasn't dead in the water. Then I filed. Having the backup also lowered my stress about the whole thing.

Illustrative response

On the retaliation question, general info only and not legal advice: most processor agreements let the company terminate for convenience, so a 'retaliation' theory is hard to win on its own. That said, regulators take a dim view of a company closing accounts specifically because someone exercised a complaint right, and you generally cannot contract away every consumer-protection remedy.

Practically, the advice above is right. Stand up a backup before you escalate. And if your funds are already past the card dispute window, say so plainly in every channel, because at that point the company's stated risk justification has largely evaporated. Keep your tone factual and your records tight. This varies by state, so confirm specifics with counsel licensed where you operate.

Illustrative response

Etsy seller here, separate but related: my issue is the chargeback itself. Buyer claimed 'item not as described' on a custom piece I made to their exact spec, with photos they approved in chat. I have everything. How do I actually win the representment?

Reading the evidence checklist upthread, I think I have all of it. Just nervous about how the card network actually decides these.

Illustrative response

'Item not as described' is one of the harder reason codes because it's subjective, but your approved-design chat is gold. Put the approval screenshots front and center, with timestamps, and a short cover summary that literally says 'buyer approved this exact design on [date], see Exhibit A.'

Win rates on representment go way up when you make the reviewer's job easy. They're skimming. One clear page that tells the story beats 40 pages of raw logs. Good luck, your facts sound strong.

Illustrative response

Has anyone tried small claims court for held funds instead of, or in addition to, the regulatory route? The arbitration clause carve-out for small claims keeps coming up but I haven't seen anyone here actually do it.

My amount is $6,400, which is under my state's small claims limit. Wondering if the threat of a small claims filing alone shakes the money loose.

Illustrative response

Coming back to this thread months later. The advice here genuinely saved me. After my PayPal hold last spring I set up the two-processor + daily sweep system people described, and last month when Square put a temporary hold on a big payout it barely registered because the bulk of my cash was already in the bank.

For anyone in the panic phase right now: it does get better, and the structural fixes are worth doing the moment you're out of the immediate fire.

Illustrative response

Brand new to selling online and reading this thread is honestly terrifying. Is there a 'least likely to freeze you' processor for a small handmade goods shop, or are they all equally capable of this?

Trying to set things up right from day one instead of learning the hard way like everyone here.

Illustrative response

Honest answer: none of them are freeze-proof, so don't pick based on that. Pick based on fees and integration, then assume any of them can hold funds and build around it. Daily sweep to a real bank account, a backup processor ready to go, and a couple months of runway in the bank.

If you set that up on day one you've already beaten 90% of the people who end up in threads like this. The freeze isn't the disaster, having no buffer when it happens is the disaster.

Illustrative response

Quick clarifying question since the thread is full of experts: when you file the CFPB complaint, do you list the processor as the company, or their bank partner? PayPal and Stripe both have a bank in the background and I wasn't sure who to name.

Don't want to file against the wrong entity and lose two weeks on a technicality.

Illustrative response

I named the processor directly (PayPal in my case) and it routed fine. The CFPB portal lets you search for the company by name and it'll surface the right registered entity. I wouldn't overthink the bank partner unless the company genuinely isn't in their list.

If you can't find them in the dropdown, you can still submit and describe the company, and CFPB routes it. It worked for me.

Illustrative response

Two general clarifications for the thread, not legal advice, and rules vary by state and change over time. First, on naming the right company: file against the entity you contracted with, which is usually the processor named in your user agreement. The CFPB will route it; you don't need to diagnose their backend banking relationships.

Second, a recurring theme I want to underline. The strongest factual point most of you have is timing: once the card-network dispute window has closed on a transaction, the processor's stated reason for holding that specific money largely disappears. Put that in writing, per transaction, with dates. It reframes the conversation from 'please give me my money' to 'there is no remaining risk to reserve against,' which is much harder to ignore. If the amount is large and you're stuck, a consultation with an attorney licensed in your state about your specific facts is worth it before deciding whether to escalate to arbitration or court.