Iqx Corp v. Intuit Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: IQX Corp. (Wyoming)
  • Defendant: Intuit Inc. (Delaware)
  • Plaintiff's Counsel: Russ August & Kabat
• Case Identification: 2:26-cv-00351, E.D. Tex., 04/30/2026
• Venue Allegations: Plaintiff alleges venue is proper because Intuit resides in the district, has committed acts of infringement within the district, and maintains a regular and established place of business in the district.
• Core Dispute: Plaintiff alleges that Defendant's Intuit MailChimp text message marketing systems infringe two patents related to generating and delivering secure, customized e-commerce transactions via mobile messaging.
• Technical Context: The technology at issue facilitates mobile commerce by creating personalized, secure webpages for users and delivering access via text messages, aiming to enhance user engagement and transaction security.
• Key Procedural History: The asserted patents are part of the same patent family, with the U.S. Patent No. 12,368,799 being a continuation of an application series that traces back to the application for U.S. Patent No. 11,876,924. The complaint does not mention any prior litigation, inter partes review proceedings, or licensing history related to the patents-in-suit.

Case Timeline

Date	Event
2018-09-27	Priority Date for '924 Patent
2018-09-27	Priority Date for '799 Patent
2024-01-16	'924 Patent Issued
2025-07-22	'799 Patent Issued
2026-04-30	Complaint Filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 11,876,924 - Secure transactions using customized webpages

The Invention Explained

• Problem Addressed: The patent describes conventional online transaction methods as cumbersome and vulnerable to security risks like fraud, which undermines user trust Compl. ¶9 '924 Patent, col. 1:15-28 It also notes that the "one-size-fits-all" approach of many websites results in a poor user experience Compl. ¶9 '924 Patent, col. 1:30-41
• The Patented Solution: The invention describes a computer-implemented method that responds to a user's activation of a "hosted field" on a third-party document (e.g., a webpage), which indicates their willingness to receive messages at a specific telephone number Compl. ¶9 '924 Patent, abstract The system then dynamically generates a "customized second document" (e.g., a personalized webpage) containing transaction information tailored to that user and sends a message with a link to that document to the user's device '924 Patent, col. 1:57-col. 2:6 When the user activates the link, the system provides the customized document to their device, facilitating a secure and personalized transaction '924 Patent, col. 2:7-14 Figure 2 of the '924 Patent, incorporated by reference into the complaint, provides a flowchart illustrating this claimed method of receiving an activation, generating a document, sending a message with a link, and providing the document upon link activation Compl. ¶7 '924 Patent, Fig. 2
• Technical Importance: This technology aims to improve the security and user experience of mobile e-commerce by creating personalized, on-demand transaction pathways delivered directly to a user's trusted device '924 Patent, col. 3:57-col. 4:5

Key Claims at a Glance

• The complaint asserts claims of the '924 Patent, including independent claim 1 Compl. ¶12
• The essential elements of independent claim 1 (a method claim) include:
  • Configuring a service subscriber... to be subscribed to receive additional content... in response to determining that the service subscriber has previously provided authentication information;
  • Activating one or more customized webpages including at least one customized actionable item for performing an e-commerce transaction, the activating comprising generation of secure access information... wherein the at least one customized actionable item corresponds to prior actions associated with one or more prior transactions performed by the service subscriber;
  • Generating, for the service subscriber, a third party message associated with the one or more customized webpages, the third party message including the at least one customized actionable item; and
  • Causing transmission of the generated third party message to the service subscriber.
• The complaint does not explicitly reserve the right to assert dependent claims, though it references claim 6 (dependent on claim 1) in the context of a claim chart Compl. ¶12

U.S. Patent No. 12,368,799 - Automated silent network authentication protocol

The Invention Explained

• Problem Addressed: The complaint alleges that conventional systems for linking to documents could not securely handle sensitive credentials, requiring manual user authentication or leaving the system vulnerable to man-in-the-middle attacks Compl. ¶22 The patent background similarly notes the security risks and cumbersome nature of typical online transactions '799 Patent, col. 1:29-57
• The Patented Solution: The patent describes a "silent network authentication protocol" to authenticate a user's device for a transaction without requiring active user input '799 Patent, abstract After a user requests to perform a transaction via a link, the system generates a "security code packet" containing a "subscriber network credential" and a "client device carrier identifier" '799 Patent, claim 18 This packet is transmitted to an authentication service provider (e.g., a mobile carrier), which verifies if the credentials match its records. Based on the match/fail response, the system either permits or denies the transaction '799 Patent, claim 18 Figure 18 of the '799 Patent, incorporated by reference into the complaint, illustrates this silent authentication flow, from generating a security packet to performing the transaction upon successful verification Compl. ¶20 '799 Patent, Fig. 18
• Technical Importance: This technology aims to provide a higher level of security for mobile transactions by using device and network-level identifiers for authentication, creating a more seamless and secure user experience than traditional password or PIN-based methods '799 Patent, col. 5:35-45

Key Claims at a Glance

• The complaint asserts claims of the '799 Patent, and while it references a chart for "independent claim 6," claim 18 is the first independent claim that appears to align with the patent's title and core technical description of a silent authentication protocol Compl. ¶25 '799 Patent, claim 18
• The essential elements of independent claim 18 (a method claim) include:
  • Generating a customized webpage with transaction information for a subscriber;
  • Generating and transmitting a message with a link for performing the transaction;
  • Receiving a request from the client device to perform the transaction via the link;
  • Causing initiation of a silent network authentication protocol, which comprises:
    • Generating a security code packet comprising a subscriber network credential and a client device carrier identifier;
    • Transmitting the security code packet to an authentication service provider;
    • Receiving an indication that the credentials match or fail to match existing records;
  • Performing the transaction in response to receiving an indication of a match.
• The complaint does not explicitly reserve the right to assert dependent claims.

III. The Accused Instrumentality

Product Identification

• The complaint identifies the accused instrumentalities as Defendant's "text message marketing systems," specifically including "Intuit MailChimp" Compl. ¶11 Compl. ¶24

Functionality and Market Context

• The complaint alleges these are systems used for text message marketing but provides minimal detail on their specific technical operation Compl. ¶11 Compl. ¶24 Based on the infringement allegations, the accused functionality involves enabling Intuit's customers to create and send text messages to end-users, where such messages contain links that lead to webpages for conducting e-commerce. The complaint does not contain specific allegations about the market position or commercial importance of the accused Intuit MailChimp features.

IV. Analysis of Infringement Allegations

• '924 Patent Infringement Allegations
  The complaint states that a claim chart comparing the '924 Patent to the accused instrumentality is attached as Exhibit 2, but this exhibit was not provided with the complaint Compl. ¶12 The narrative theory of infringement alleges that Intuit's MailChimp systems satisfy the limitations of the patent's claims Compl. ¶12 This suggests an allegation that the MailChimp platform enables its users to perform a process of: (1) capturing an end-user's consent to receive messages (the "hosted field" activation); (2) in response, generating a customized webpage with transaction details relevant to that user; (3) sending a text message containing a link to that customized webpage; and (4) delivering the webpage for display when the end-user clicks the link. The complaint does not, however, provide factual allegations detailing how the MailChimp product specifically performs each of these steps.

• '799 Patent Infringement Allegations
  Similarly, the complaint references a claim chart for the '799 Patent as Exhibit 4, which was not provided Compl. ¶25 The complaint's infringement theory alleges that the Accused Instrumentalities satisfy the claims of the '799 Patent Compl. ¶25 This implies an allegation that when an end-user clicks a link in a MailChimp-sent text message to perform a transaction, the system initiates a "silent network authentication protocol." This protocol would necessarily involve the generation and transmission of a "security code packet" containing the user's "network credential" and "device carrier identifier" to an "authentication service provider" for verification before the transaction can proceed. The complaint offers no specific facts about how Intuit MailChimp implements such a security protocol.

• Identified Points of Contention:

  • Technical Questions ('924 Patent): A central question will be whether the standard user opt-in features of a marketing platform like MailChimp (e.g., a checkbox on a form) meet the claim limitation of activating a "hosted field" that triggers the subsequent generation of a "customized second document." The complaint lacks specific evidence of this direct causal link in the accused product.
  • Evidentiary Questions ('799 Patent): The infringement allegation for the '799 Patent raises a significant evidentiary question: what proof exists that Intuit MailChimp utilizes the highly specific "silent network authentication protocol" recited in the claims? The complaint makes a conclusory allegation without providing any technical details, screenshots, or other evidence that the accused system generates "security code packets" or interacts with "authentication service providers" in the manner claimed.

V. Key Claim Terms for Construction

• The Term: "hosted field" ('924 Patent, claim 1)

• Context and Importance: The activation of the "hosted field" is the triggering event for the entire claimed method. The outcome of the infringement analysis may depend on whether this term is construed broadly to cover any web-based opt-in mechanism or narrowly to require a specific technical implementation. Practitioners may focus on this term because its scope will determine whether standard marketing opt-in forms fall within the claim.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification describes the field's function as allowing a user to "indicate a willingness to receive one or more messages" '924 Patent, col. 5:2-5, language which could support an interpretation covering a wide range of user interface elements.
  • Evidence for a Narrower Interpretation: The summary of the invention also describes a computer that "injects a host field into a document associated with a third party" '924 Patent, col. 2:51-53 This could support a narrower construction requiring that the claimed system actively injects the field, rather than merely processing information from a pre-existing form element on a third-party site.

• The Term: "silent network authentication protocol" '799 Patent, claim 18

• Context and Importance: This term encapsulates the core novelty alleged for the '799 Patent. Whether Intuit's security mechanisms infringe will depend entirely on if they can be characterized as this specific protocol.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The term is not defined in a standalone glossary, which might allow a party to argue it covers any authentication process that occurs in the background without direct user interaction (e.g., entering a password).
  • Evidence for a Narrower Interpretation: Claim 18 itself provides a detailed, step-by-step definition of the protocol, requiring the generation of a "security code packet" with a "subscriber network credential" and a "client device carrier identifier," transmission to an "authentication service provider," and receipt of a match/fail indication '799 Patent, claim 18 This language strongly suggests the term is a label for this specific sequence of steps, supporting a narrow construction.

VI. Other Allegations

• Indirect Infringement: For both patents, the complaint alleges induced infringement under 35 U.S.C. § 271(b). The allegations state that Intuit provides the Accused Instrumentalities along with "user manuals and instruction materials" that actively encourage and instruct its customers to use the systems in a manner that directly infringes the patents Compl. ¶13 Compl. ¶26
• Willful Infringement: The complaint alleges willful infringement for both patents, asserting that Intuit has knowledge of the patents and their infringement "Through at least the filing and service of this Complaint and/or earlier" Compl. ¶13 Compl. ¶26 It further alleges that Intuit's continued infringement despite this knowledge is "knowing[], willfully, recklessly, egregiously and wantonly," warranting enhanced damages under 35 U.S.C. § 284 Compl. ¶17 Compl. ¶30

VII. Analyst's Conclusion: Key Questions for the Case

1. Evidentiary Sufficiency: A primary issue for the entire case will be one of evidentiary support. Can the Plaintiff substantiate its conclusory allegations with concrete evidence that the Intuit MailChimp platform actually performs the specific, multi-step processes recited in the asserted claims of both the '924 and '799 patents?
2. Functional Mismatch: A key technical question will be one of functional operation. Does the accused text message marketing platform's functionality align with the patent's specific architecture, particularly the '799 Patent's requirement for a "silent network authentication protocol" involving security packets and carrier-level verification, or is there a fundamental mismatch in how the accused system secures transactions?
3. Definitional Scope: The dispute will likely involve a significant claim construction battle over the scope of core terms. A central question for the court will be whether "hosted field" ('924 Patent) can be construed to read on standard web opt-in forms and whether "silent network authentication protocol" ('799 Patent) is limited to the explicit step-by-step process detailed in the patent's claims.