Charles Schwab v. Blaze Mobile: Mobile Banking Patent Dispute Dismissed With Prejudice
Charles Schwab sought a declaratory judgment against Blaze Mobile over three mobile banking patents covering non-browser-based banking applications, server-side mobile transactions, and authentication methods. The parties jointly stipulated to dismiss the action with prejudice after 210 days, with each side bearing its own legal costs.
Schwab Seeks Declaratory Relief on Mobile Banking Patents, Then Walks Away
On February 28, 2025, The Charles Schwab Corporation filed a declaratory judgment action in the Northern District of California (Case No. 5:25-cv-02122) against Blaze Mobile, Inc. and related entities. Schwab sought a judicial declaration — most likely of non-infringement or invalidity — with respect to three US patents held by Blaze Mobile: US11847649B2, US11783365B1, and US10235664B2. These patents cover mobile banking functionality delivered via non-browser-based applications, server-side mobile banking methods, and mobile transaction authentication.
The case closed on September 26, 2025, via a stipulated dismissal with prejudice under Federal Rule of Civil Procedure 41(a)(1)(A)(ii). Both sides agreed to end the litigation jointly, with each party absorbing its own costs, expenses, and attorneys’ fees. A dismissal with prejudice is final — Schwab cannot re-litigate the same claims against Blaze Mobile, and Blaze Mobile cannot revive the same infringement assertions in a counter-action arising from the same nucleus of facts resolved here.
The 210-day duration and mutual cost-bearing arrangement are consistent with a negotiated resolution — potentially a licensing agreement, covenant not to sue, or broader commercial settlement — though the public record does not disclose the underlying terms. The decision by Schwab, a major financial institution, to initiate declaratory judgment proceedings typically signals it had received or anticipated a patent assertion letter from Blaze Mobile. The with-prejudice dismissal suggests both parties reached a durable resolution rather than merely pausing hostilities.
Filing to Dismissed with Prejudice in 210 days
210 days — resolved before trial, suggesting early commercial resolution
Stipulated dismissal with prejudice: what it means for both parties
Rule 41(a)(1)(A)(ii) dismissal with prejudice is final and binding
A stipulated dismissal under Rule 41(a)(1)(A)(ii) requires both parties’ signatures and, when filed with prejudice, operates as a final adjudication on the merits. Neither Schwab nor Blaze Mobile can reinitiate litigation over the same claims in federal court. This is a more conclusive endpoint than a voluntary dismissal without prejudice, which would leave the door open to re-filing.
Permanent bar to re-litigationSchwab secures permanent resolution — but terms remain undisclosed
Schwab filed for declaratory relief, suggesting it sought certainty that its mobile banking products do not infringe Blaze Mobile’s patents. The with-prejudice dismissal achieves a durable endpoint. Whether Schwab obtained a formal license, a covenant not to sue, or some broader commercial arrangement is not visible in the public record — but the finality of the dismissal is consistent with Schwab having secured the protection it sought.
Declaratory relief resolvedBlaze Mobile’s patent claims against Schwab are permanently extinguished
By agreeing to dismiss with prejudice, Blaze Mobile relinquishes any infringement claim it might have asserted against Schwab based on the three patents at issue. This does not, however, affect Blaze Mobile’s ability to assert those patents against other defendants. The mutual cost-bearing arrangement suggests no clear winner emerged, and the resolution may reflect Blaze Mobile extracting value through confidential licensing terms.
No residual claim against SchwabMobile banking IP assertions remain active risk for fintech and financial institutions
Blaze Mobile’s patent portfolio — covering non-browser mobile banking, server-side transaction methods, and authentication — remains in force against the broader market. The Schwab resolution does not invalidate any claims and may embolden further assertion activity. Financial institutions and fintech platforms offering comparable mobile banking functionality should treat these patents as live enforcement risk and consider FTO analysis.
Portfolio remains enforceableFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | The Charles Schwab Corporation | Company | Major US financial services firm — holder of declaratory judgment claims over US11847649B2Search in Eureka ↗ |
| Defendant | Blaze Mobile, Inc. | Company | Mobile financial technology patent assertion entity holding mobile banking and authentication patentsSearch in Eureka ↗ |
| Plaintiff counsel | Joshua L. Raskin | Attorney | Counsel for The Charles Schwab CorporationSearch in Eureka ↗ |
| Plaintiff counsel | Julie Pamela Bookbinder | Attorney | Counsel for The Charles Schwab CorporationSearch in Eureka ↗ |
| Plaintiff counsel | Nicholas A. Brown | Attorney | Counsel for The Charles Schwab CorporationSearch in Eureka ↗ |
| Plaintiff counsel | Scott J. Bornstein | Attorney | Counsel for The Charles Schwab CorporationSearch in Eureka ↗ |
| Plaintiff law firm | Greenberg Traurig LLP | Law Firm | Representing The Charles Schwab CorporationSearch in Eureka ↗ |
| Plaintiff law firm | Greenberg Traurig LLP (NYC) | Law Firm | Representing The Charles Schwab CorporationSearch in Eureka ↗ |
| Defendant counsel | Darren E. Donnelly | Attorney | Counsel for Blaze Mobile, Inc.Search in Eureka ↗ |
| Defendant law firm | Polsinelli PC | Law Firm | Representing Blaze Mobile, Inc.Search in Eureka ↗ |
| Presiding judge | Judge N/A | Judge | California Northern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The stipulated dismissal invokes Rule 41(a)(1)(A)(ii), requiring joint agreement of all appearing parties — a procedurally clean and binding mechanism. The with-prejudice designation converts the dismissal into a final merits disposition for purposes of res judicata, permanently barring Schwab from reasserting the same declaratory claims and Blaze Mobile from reasserting the same infringement theories against Schwab. The mutual cost-bearing provision suggests neither side extracted a clear litigation win, consistent with a privately negotiated commercial resolution whose specific terms are not reflected in the public docket.
US11847649B2, US11783365B1 & US10235664B2 — Mobile Banking & Authentication Patents
The three patents at the centre of this dispute protect distinct but overlapping aspects of mobile financial services delivery. US11847649B2 (App. No. 14/691537) covers mobile banking using a non-browser-based application — a category encompassing native app-based banking infrastructure. US11783365B1 (App. No. 18/205385) addresses method and system claims for server-side mobile banking. US10235664B2 (App. No. 14/219223) covers mobile banking transaction authentication at a server level. Together, the portfolio targets foundational architecture used in mainstream retail banking apps.
The strategic significance of this portfolio lies in its breadth across the mobile banking stack — from client-side application delivery to server-side authentication. These are not fringe use cases: non-browser native app banking and server-authenticated mobile transactions are standard features across virtually every major US retail banking platform. That Charles Schwab — a sophisticated financial institution with substantial in-house IP resources — opted for declaratory judgment rather than a licensing negotiation suggests these patents carry meaningful infringement risk optics, even if their ultimate validity or claim scope remains untested on the merits.
Should you run an FTO against US11847649B2, US11783365B1, and US10235664B2?
Any financial institution, neobank, or fintech developer offering native mobile banking applications with server-side authentication should treat these three Blaze Mobile patents as active FTO considerations. The Schwab case confirms that even major, well-resourced institutions face assertion pressure from this portfolio. If your product delivers mobile banking functionality outside a browser — particularly with server-validated transactions — your engineering and legal teams should map your implementation against the independent claims of each patent before a demand letter arrives.
PatSnap Eureka’s FTO Search Agent allows IP and R&D teams to upload product specifications and run automated claim-mapping against US11847649B2, US11783365B1, and US10235664B2. Eureka identifies prior art, claim scope boundaries, and design-around opportunities — enabling proactive risk triage rather than reactive litigation. For mobile banking platforms under competitive pressure, this analysis can inform both product architecture decisions and licensing negotiation strategy before enforcement escalates.
Run a freedom-to-operate analysis on US11847649B2 to assess your product’s exposure
Run FTO in Eureka →Similar Mobile Banking Patent Litigation in N.D. California
Explore related declaratory judgment and patent infringement cases involving mobile banking, non-browser application, and authentication patents filed in N.D. California federal courts.
Related patent case — similar technology
Comparable case in the same technology domain. Patent holder and defendant reached resolution after proceedings.
SettledRelated infringement action — same court
Comparable Blaze mobile banking using a non-browser based application-adjacent infringement action. Patent enforcement dynamics analysed in depth.
Active · District CourtRelated invalidity challenge — appellate outcome
Combined invalidity and infringement action in the same technology space. Decided after substantive proceedings.
DecidedThe Charles Schwab Corporation’s broader IP enforcement history
The Charles Schwab Corporation’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat this case signals for the mobile banking IP landscape
A major US bank seeking declaratory relief over mobile authentication patents highlights growing IP enforcement risk in financial technology.
Declaratory judgment filings signal active patent assertion pressure on banks
Schwab’s decision to initiate declaratory judgment proceedings — rather than wait for a lawsuit — typically follows receipt of a licensing demand or infringement notice. Financial institutions operating mobile banking platforms should monitor patent holders like Blaze Mobile and conduct proactive FTO assessments before assertion escalates to full litigation.
With-prejudice dismissals often mask confidential licensing outcomes
The mutual cost-bearing, with-prejudice structure of this dismissal is a hallmark of a negotiated exit. Companies facing similar patent assertion campaigns from Blaze Mobile or comparable mobile fintech patent holders should note that the underlying commercial terms — potentially including royalty rates or licensing scope — are not publicly available, limiting benchmarking of settlement value.
Blaze Mobile’s three-patent portfolio poses ongoing risk to mobile banking platforms
US11847649B2, US11783365B1, and US10235664B2 cover fundamental mobile banking methods that are widely deployed across the US fintech sector. The Schwab dismissal does not disturb these patent claims. Any institution or app developer delivering non-browser-based mobile banking or server-side authentication should assess exposure before receiving a demand letter.
N.D. California forum choice signals strategic patent enforcement posture
Filing a declaratory judgment action in the Northern District of California — home to major technology companies and experienced patent bench — is a deliberate tactical choice. It suggests Schwab anticipated complex technical patent arguments and preferred a venue with deep IP expertise. Defendants in future Blaze Mobile actions may face different forum dynamics if Blaze selects alternative districts.
The v Blaze — key questions answered
Charles Schwab filed a declaratory judgment action against Blaze Mobile in the Northern District of California on February 28, 2025. The parties jointly stipulated to dismiss the case with prejudice on September 26, 2025, under Rule 41(a)(1)(A)(ii), with each party bearing its own costs. No court ruling on the merits was issued.
Three patents were at issue: US11847649B2 (mobile banking via non-browser-based application), US11783365B1 (method and system for server-side mobile banking), and US10235664B2 (mobile banking transactions with server-level authentication). All three remain in force following the dismissal.
A with-prejudice dismissal is a final disposition. Schwab cannot refile the same declaratory judgment claims against Blaze Mobile’s three patents, and Blaze Mobile is barred from asserting the same infringement theories against Schwab. The dismissal does not affect Blaze Mobile’s ability to assert the same patents against other defendants.
Declaratory judgment actions are typically initiated when a patent holder sends licensing demands or infringement notices that create a reasonable apprehension of suit. Schwab’s filing suggests it received — or anticipated — such communications from Blaze Mobile and preferred to seek judicial certainty in a favourable venue rather than await a direct infringement lawsuit.
Yes. The Schwab dismissal resolved claims only between those specific parties and did not invalidate or limit the scope of the three patents. US11847649B2, US11783365B1, and US10235664B2 remain enforceable. Financial institutions, neobanks, and fintech developers offering native mobile banking applications with server-side authentication should assess their exposure through freedom-to-operate analysis.
Protect Your Mobile Banking Platform from Patent Assertion Risk
The Blaze Mobile portfolio remains enforceable against any platform offering native mobile banking or server-side authentication. Run an FTO analysis in PatSnap Eureka before your institution receives a licensing demand.
PatSnap Eureka searches patents and litigation data to answer instantly.