Payment Processor Disputes · Memo

Getting a Frozen-Account Demand Letter Past Customer Support to Legal

Counsel know how to write a demand letter. The challenge with a frozen processor account is operational: how to make sure the letter gets to a human who can release the funds. I will walk through what has worked in the matters I have handled.

The frustration in a processor account freeze is not usually with the law. It is with the routing. The merchant has uploaded the documentation, the support agent has acknowledged receipt, and then the matter sits in a queue for a period that exceeds anything reasonable. The merchant's lawyer writes a demand letter. The demand letter goes to support@stripe.com or service@paypal.com. The demand letter joins the queue. Nothing changes.

I have written a lot of these. What I have learned is that the legal merit is necessary but not sufficient. The escalation is the operational work, and it is where counsel who specialize in these matters do their best work.

The structural problem

Major payment processors run support operations at scale. The frontline team handles tens of thousands of contacts a day. The triage rules they operate under are designed to handle volume, not to identify legally significant escalations. A demand letter that arrives through the standard support channel will be tagged, ticketed, and routed using the same logic as a refund inquiry. The escalation paths from the support tier to the risk-operations tier and from risk-operations to legal are gated by criteria that do not include 'an attorney sent a letter.' What does open the gates: regulatory inquiries, formal litigation filings, named-executive correspondence, and pattern signals from the risk-operations team.

The escalation strategy I run is built around those four channels.

Named-executive correspondence

The first move on any meaningful matter is named-executive correspondence. The general counsel, the chief compliance officer, and the head of risk operations of the processor are public information. Their addresses at the corporation are the same domain as the company. Letters addressed to specific named officers at the corporate headquarters do not get triaged by the consumer support team. They get triaged by an executive-correspondence team that escalates to the named addressee's office. That team is small, has authority, and operates on different criteria than the support queue.

The letter sent to a named officer is not the same letter sent to support. The named-officer letter is shorter. It does not recite the facts at length. It opens with the contract section being breached, the specific statute (if any) being triggered, the dollar exposure to the company, and the specific action being requested. It includes a deadline. It attaches the supporting facts as exhibits rather than reciting them in the body. It is the kind of letter a chief compliance officer can route to outside counsel in under five minutes. That is the design objective.

The regulatory complaint as parallel track

The DFPI in California, the New York DFS, the Texas Department of Banking, and the regulators in other states with relevant jurisdiction receive complaints from merchants frozen by major processors. A complaint to the relevant state regulator is not by itself a fast remedy. The complaint creates a record that the processor must respond to and creates a parallel track that operates outside the processor's internal support routing. The CFPB, post-2025 reorganization, takes a narrower set of payment-processor matters but is still a relevant audience for consumer-facing or pattern-and-practice issues.

The regulatory complaint should be referenced in the named-officer demand letter. Not as a threat. As a statement of fact. The letter notes that a complaint has been filed with the relevant state regulator and that a copy of the complaint and the supporting documentation is available on request. The regulator's involvement raises the matter's profile inside the processor's legal team. The matter moves from a support-routing problem to a regulatory-response problem, which is a different team and a different timeline.

The litigation filing

The third escalation channel is the litigation filing. For a freeze of meaningful size, filing a complaint in California Superior Court (or the relevant venue) and serving the processor moves the matter unambiguously into the legal department. The filing is expensive, time-consuming, and changes the negotiating posture, so I do not recommend it lightly. For matters where the freeze is large enough to justify the cost and the merchant has clean facts, the filing is the fastest reliable mechanism to get the processor's legal team to engage.

The arbitration agreement in the User Agreement complicates this. A premature complaint filing in court is likely to be met with a motion to compel arbitration. The drafting move is to file a complaint that seeks public-injunctive relief under California's UCL, which McGill v. Citibank N.A., 2 Cal. 5th 945 (2017), holds is not waivable by arbitration agreement. The arbitration-compellable claims (breach of contract, conversion, restitution) can be filed separately in the AAA. Whether the cost of running two parallel proceedings is worth the leverage depends on the dollars at stake.

What the demand letter should say

For the letter that does go to support (because every escalation should be paired with a clean record at the support tier), the structure I use:

1. Account identification with the specific account, dates, and the limitation event.
2. The contract sections being relied on. Quote them. Include section numbers.
3. The specific factual ground on which the limitation is asserted to be a breach. Not a general grievance, a specific point.
4. The statutory overlay if applicable (ECOA for credit-product limitations, FCRA for consumer-report-based decisions, UCL for unfair-business-practice patterns, conversion for funds held beyond the contractual hold period).
5. The specific remedy requested with a dollar number.
6. The deadline, typically ten business days for an initial response and twenty-one business days for full release of funds.
7. A statement that further escalation (regulatory complaint, litigation filing) will follow if the matter is not resolved.

The letter is signed by counsel with the attorney's state bar number. The letter is sent by certified mail with signature requested and also by email to the support channel. A copy goes to the named officer at corporate headquarters under separate cover. The certified-mail tracking record is preserved.

What does not work

A few patterns I have seen fail.

A demand letter that runs to ten pages of factual recitation buries the legal claim. The legal team scanning it cannot find the cause of action. The letter gets routed back to support as 'merchant has counsel, asking for documentation.' The fix is to put the legal theory in the first paragraph and the facts in exhibits.

A demand letter that opens with a threat without first stating a contractual breach reads as a shakedown. The legal team treats it accordingly. The fix is to lead with the breach.

A demand letter that asks for damages without offering a release mechanism gives the processor no path to resolution. The legal team's authority to settle is bounded by the demand. If the demand is for $500,000 in consequential damages on a $200,000 hold, the matter sits unresolved while the processor's legal team determines whether the consequential-damages theory has merit. The fix is to bifurcate: an immediate request for release of held funds (which the processor can grant under existing authority) and a separate request for damages (which can be discussed in subsequent correspondence).

The realistic timeline

For a well-prepared escalation, the timeline I have seen is roughly: named-officer letter sent on day 1; processor legal team engagement on days 5 to 14; substantive response on days 14 to 30; resolution discussion on days 21 to 45. For matters that require regulatory or litigation pressure, add thirty to ninety days. For matters where the merchant's documentation is incomplete or the underlying facts support the processor's position, the timeline does not improve and the merchant should consider alternative outcomes (a wind-down with funds returned net of legitimate chargeback exposure).

Sergei Tokmakov, Esq., CA Bar #279869. This memo is attorney commentary on legal questions and is not legal advice. Reading it does not create an attorney-client relationship. Past matter outcomes depend on facts and the responding party; nothing here is a prediction of result.