PayPal Just Switched from AAA to JAMS. Your Case Model Should Have Changed with It.

PayPal updated its user agreement with an effective date of September 1, 2026. Buried in the legal section: the company is moving its arbitration provider from AAA to JAMS and adding mass arbitration procedures to its contract.

If you're a plaintiff firm with a PayPal mass arb campaign in your pipeline, that sentence just changed your case economics. If you didn't notice it, you're about to model the wrong matter.

This isn't just a PayPal story. It's a pattern. Defendants are no longer just rewriting arbitration clauses to add bellwethers or batching. They're switching providers entirely, sometimes mid-cycle, sometimes quietly, sometimes both. And every switch changes the math.

The Fee Delta Is Not Trivial

AAA and JAMS price mass arbitration differently. Not a little differently. Structurally differently.

AAA's 2024 mass arbitration fee schedule moved to a staged, tiered initiation fee structure with a process arbitrator managing threshold issues across the inventory. JAMS, under its May 2024 Mass Arbitration Procedures, applies when roughly 75 or more similar demands are filed by coordinating counsel and installs its own process administrator. But the fee mechanics diverge in ways that compound fast on a large claimant pool.

JAMS carries a 13% Case Management Fee on top of its headline filing fee. On a 5,000-claimant matter, that's not a rounding error. It's a line item that changes whether the matter pencils out. AAA's tiered per-case fees don't drop linearly the way most firms assume, either, but the shape of the cost curve is different from JAMS's shape. When a defendant moves from one to the other, your entire fee projection needs to be rebuilt from scratch.

Most firms don't rebuild it. They take the old model, swap the provider name at the top, and assume the numbers are close enough. They're not.

Procedural Timeline Changes Too

AAA triggers its mass arbitration supplementary rules at 25 or more similar claims. JAMS triggers at roughly 75. That difference matters more than it looks like on paper.

If you're filing 200 demands against a defendant that just switched to JAMS, you're still in mass arb territory. But the procedural on-ramp is different. JAMS requires a sworn declaration as to the accuracy and non-frivolousness of each demand. AAA's process arbitrator framework handles threshold and administrative issues in a way that doesn't map one-to-one onto JAMS's process administrator model.

The practical effect: your intake and verification workflow that was tuned for AAA's requirements may not satisfy JAMS's. Your timeline assumptions for how quickly demands move from filed to administered may be off by weeks or months. And if you're funding the matter on a cost-of-capital model (which you should be), weeks matter. Months are expensive.

Why Defendants Are Shopping Providers Now

This is the part most plaintiff firms haven't internalized yet. Defendants aren't just adding procedural complexity to their arbitration clauses. They're actively selecting the provider whose fee structure and mass arbitration rules create the most friction for plaintiff-side economics.

Some are moving to NAM or ADR Services for even more aggressive cost reduction. PayPal's move to JAMS is more moderate, but it's still strategic. JAMS's higher threshold (75 vs. 25) means smaller campaigns may not trigger mass arb procedures at all, which changes how the provider manages the cases. The sworn declaration requirement adds a screening layer that creates work on the plaintiff side before the first arbitrator is assigned.

None of this is illegal. None of it is even unusual in the context of contract drafting. But it is a deliberate move to reshape the economic landscape that plaintiff firms operate in, and it rewards the firms that notice and re-model before they spend money.

The Real Risk: Modeling Against Yesterday's Clause

Here's where this gets expensive. A firm decides to pursue a mass arb campaign against a company. They pull the arbitration clause from six months ago. They model fees, timeline, and settlement range based on that clause. They spend $80,000 or $150,000 on claimant acquisition. Then they go to file and discover the clause changed. The provider is different. The fee structure is different. The procedural requirements are different.

Now they have a portfolio of signed claimants and a case model that doesn't match reality. The options at that point are all bad: absorb the delta, restructure the campaign, or explain to your funding source why the projections were wrong.

The fix is boring and operational. Before you greenlight acquisition spend on any mass arb matter, pull the current terms of service. Not the version you cached last quarter. The live version, as of today. Compare the arbitration clause to what you modeled. If the provider changed, rebuild the fee model from the provider's current schedule. If the mass arb trigger changed, recalculate your filing strategy. If new procedural requirements appeared (bellwethers, batching, sworn declarations, global mediation mandates), map them into your timeline and staffing plan.

This takes a few hours of work. Skipping it can cost six figures.

What This Means for Your Admin Stack

Provider switches also change what you need from your claims administrator. If you built your outreach and document collection workflow around AAA's requirements and the defendant just moved to JAMS, your admin needs to adjust signing workflows, verification steps, and filing formats. If your admin is a legacy shop that treats every provider the same way, that adjustment either doesn't happen or happens slowly and expensively.

This is one of the reasons we built GroupSettle to own the entire stack, from native document signing through SMS and email delivery to the AI super agent that handles over 80% of claimant inquiries. When a provider switch changes what documents need to be signed, how declarations need to be formatted, or what verification is required, we change the workflow in the system. We don't send a change order to a third-party e-signature vendor and wait.

I'm biased. I built the thing. But the underlying point stands regardless of who administers your claims: your admin needs to be able to adapt to provider switches without a two-week lag and a five-figure invoice.

The Monday Takeaway

If you have any mass arb campaign in your pipeline right now, pull the defendant's current terms of service today. Not next week. Today. Compare the arbitration clause to what you modeled. If anything changed (provider, threshold, fee allocation, procedural steps), rebuild the model before you spend another dollar on acquisition.

PayPal's switch from AAA to JAMS is public and easy to find. The next company that does it might not announce it as clearly. The firms that build a clause-monitoring discipline into their pre-acquisition workflow are the ones that won't get surprised. The ones that don't will keep finding out after they've already spent the money.