BrowserKey v. J.P. Morgan Chase: Patent Suit Dismissed With Prejudice in 21 Days
BrowserKey, LLC asserted US7249262B2 against JPMorgan Chase’s mobile and web banking applications — including Chase Mobile, Chase Pay, and Nutmeg — in the Eastern District of Texas. The case collapsed within 21 days when BrowserKey voluntarily dismissed with prejudice, permanently surrendering all infringement claims.
A 21-Day E.D. Tex. Patent Case That Ended Before It Began
On April 28, 2025, BrowserKey, LLC — represented by Fabricant LLP — filed suit in the Eastern District of Texas against J.P. Morgan Chase & Co., asserting that Chase’s mobile and web applications infringed US7249262B2. The accused products included Chase Mobile, Chase Pay, Nutmeg applications across iOS, iPadOS, and Android, and JPMorgan’s broader web and mobile application suite — a wide sweep of consumer-facing financial technology.
Just 21 days after filing, on May 19, 2025, BrowserKey filed a Notice of Dismissal, voluntarily dismissing all claims with prejudice under Rule 41(a)(1)(A)(i). The court accepted and acknowledged the notice, closed the case, and ordered each party to bear its own costs. A dismissal with prejudice is final and on the merits — BrowserKey cannot re-assert these claims against Chase on this patent.
A resolution in 21 days — before any defendant response or substantive motion — is structurally consistent with a pre-trial settlement or a licensing agreement reached under pressure of litigation. The public record is silent on whether any consideration changed hands. What is clear is that BrowserKey absorbed a permanent bar on re-filing, which typically reflects either a negotiated exit or an assessment that the claim could not survive early scrutiny.
Filing to Voluntary dismissal in 21 days
21 days — well below the median E.D. Tex. patent case lifespan, suggesting pre-suit leverage or rapid settlement
Dismissed with prejudice: what the 21-day exit means for both parties
Rule 41(a)(1)(A)(i): plaintiff’s right to dismiss, once — but at a cost
Under Rule 41(a)(1)(A)(i), a plaintiff may voluntarily dismiss without a court order before the defendant serves an answer or a motion for summary judgment. Here, BrowserKey exercised that right but chose — or agreed — to dismiss WITH prejudice. That election transforms a procedural withdrawal into a final adjudication on the merits, permanently barring re-assertion of the same claims against Chase on US7249262B2.
Permanent bar on re-filingBrowserKey surrenders its infringement claims against Chase permanently
A with-prejudice dismissal is the strongest form of finality available at this stage. BrowserKey cannot re-file this case against Chase on US7249262B2 in any U.S. court. Whether this reflects a confidential licensing resolution or a strategic retreat is unknown from the public record. The patent itself remains in force and may still be asserted against other defendants, but Chase has secured a complete defence against future BrowserKey claims on this patent.
Claims extinguished vs. ChaseJPMorgan Chase exits clean — no costs, no injunction risk
Chase achieved the best procedural outcome available at this stage: full dismissal with prejudice, no liability finding, no injunction, and no adverse cost order. The court’s fee ruling — each party bears its own costs — means Chase absorbed its own legal fees but faces no further exposure on these specific claims. Whether a licensing payment was part of a broader resolution is not reflected in the court record.
Full defence securedUS7249262 remains live IP — other fintech and banking platforms stay at risk
The dismissal resolves the Chase dispute but does not extinguish the patent. US7249262B2 could still be asserted against competing mobile banking and authentication platforms. The speed of resolution — 21 days — and the with-prejudice terms suggest this may have been a targeted enforcement action. Fintech product teams and banking app developers should treat this outcome as a signal to assess their own exposure to the underlying technology claims.
Patent enforcement continuesFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | BrowserKey, LLC | Company | Patent assertion entity — holder of US7249262B2, mobile browser authentication technologySearch in Eureka ↗ |
| Defendant | J.P. Morgan Chase & Co. | Company | J.P. Morgan Chase & Co. — global financial institution operating Chase Mobile, Chase Pay, and Nutmeg appsSearch in Eureka ↗ |
| Plaintiff counsel | Alfred Ross Fabricant | Attorney | Counsel for BrowserKey, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Jacob Daniel Ostling | Attorney | Counsel for BrowserKey, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Peter Lambrianakos | Attorney | Counsel for BrowserKey, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Vincent J. Rubino , III | Attorney | Counsel for BrowserKey, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Fabricant LLP | Law Firm | Representing BrowserKey, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Fabricant LLP (NY) | Law Firm | Representing BrowserKey, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Fabricant LLP (Rye) | Law Firm | Representing BrowserKey, LLCSearch in Eureka ↗ |
| Presiding judge | Judge N/A | Judge | Texas Eastern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The court’s order reflects a ministerial acceptance of BrowserKey’s Rule 41(a)(1)(A)(i) notice rather than a merits adjudication. Critically, the with-prejudice designation — stated explicitly in the notice and adopted by the court — converts the voluntary withdrawal into a final disposition. The ‘each party bears own costs’ fee allocation is standard for consent-based exits and does not imply any finding on either party’s conduct or claim strength. The order leaves no live claims and no avenue for BrowserKey to re-engage Chase on US7249262B2.
US7249262B2 — mobile browser authentication and secure session technology
US7249262B2 (application number US10/139924) is a granted U.S. utility patent asserted in the context of mobile and web-based authentication — a technology layer that sits at the core of every consumer banking application. The patent was asserted against Chase Mobile, Chase Pay, Nutmeg (iOS, iPadOS, Android), and JPMorgan’s broader web and mobile application suite, suggesting its claims reach across authentication or session management workflows common to multi-platform financial services deployments.
Authentication and secure browser session patents occupy a strategically sensitive position in the fintech IP landscape. As financial institutions migrate core services to mobile and web channels, the attack surface for assertion entities holding foundational method or system claims in this space widens. US7249262B2’s breadth — evidenced by the number and variety of accused products — suggests it may be positioned for multi-defendant assertion campaigns. Any platform operating mobile banking, in-app authentication, or secure web sessions should treat this patent as a monitoring priority.
Should you run an FTO against US7249262B2?
If your organisation operates a mobile banking application, consumer-facing financial platform, or any product incorporating browser-based or app-layer authentication workflows, US7249262B2 warrants a targeted freedom-to-operate review. This case demonstrates that assertion activity is live and that even a defendant of JPMorgan’s scale resolved quickly rather than contest the claims. Smaller fintech platforms, neobanks, and payment application developers face materially higher litigation risk if they lack an FTO opinion on file.
PatSnap Eureka’s FTO Search Agent allows IP and R&D teams to map US7249262B2’s claim scope against your product architecture, identify prosecution history estoppel, and surface prior art that may limit enforceability — all before a complaint is filed. Proactive FTO analysis in this technology domain is faster and significantly less expensive than reactive litigation defence in the Eastern District of Texas.
Run a freedom-to-operate analysis on US7249262B2 to assess your product’s exposure
Run FTO in Eureka →Similar mobile authentication patent cases in E.D. Texas
Cases involving mobile banking and authentication patent assertions in the Eastern District of Texas, including other Fabricant LLP-filed infringement actions.
What this case signals for the fintech and mobile banking IP landscape
A 21-day dismissal with prejudice in E.D. Tex. rarely happens without a strategic reason. Here is what IP teams should take away.
E.D. Tex. remains a high-leverage venue even for rapid exits
Filing in the Eastern District of Texas carries inherent pressure regardless of case strength. The 21-day lifecycle here — from filing to dismissal — suggests the venue choice functioned as intended: to create urgency. IP counsel advising financial services clients should treat any E.D. Tex. filing as a signal requiring immediate triage, not routine docketing.
With-prejudice dismissals protect defendants durably — but at unquantified cost
Chase secured a permanent bar on re-assertion, which is a durable outcome. However, the public record does not disclose whether a licensing fee or settlement payment accompanied that protection. Defendants negotiating early exits should press for with-prejudice terms as a baseline; patent assertion entities will often concede them in exchange for other consideration.
BrowserKey v J.P. — key questions answered
A dismissal with prejudice under Rule 41(a)(1)(A)(i) is a final disposition on the merits. BrowserKey cannot re-file the same infringement claims against J.P. Morgan Chase & Co. based on US7249262B2 in any U.S. court. The patent itself remains valid and may still be enforced against other defendants.
The public record does not disclose the reason. A 21-day lifecycle before any defendant response is structurally consistent with a confidential licensing or settlement agreement reached under the pressure of litigation. It may also reflect a strategic reassessment of claim viability. The with-prejudice election suggests BrowserKey received something of value in return, but no financial terms are publicly available.
BrowserKey accused Chase Mobile, Chase Pay, the Nutmeg applications for iOS, iPadOS, and Android, and the broader JPMorgan web and mobile applications suite. This suggests the patent’s claims are directed at authentication or session management functionality common across multi-platform consumer banking deployments.
BrowserKey was represented by Fabricant LLP, with named attorneys Alfred Ross Fabricant, Jacob Daniel Ostling, Peter Lambrianakos, and Vincent J. Rubino III. Fabricant LLP is a New York-based firm with an established practice in patent assertion litigation, particularly in the Eastern District of Texas.
No. The court ordered each party to bear its own costs, expenses, and attorneys’ fees — a standard allocation in consensual early dismissals. It does not reflect a finding on the merits, litigation conduct, or relative strength of the parties’ positions. An ‘exceptional case’ fee award under 35 U.S.C. § 285 was not issued, which is typical when a case resolves before substantive proceedings begin.
PatSnap Eureka searches patents and litigation data to answer instantly.