Secure Matrix LLC v. Buff City Soap LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Secure Matrix LLC (Delaware)
  • Defendant: Buff City Soap, LLC (Delaware)
  • Plaintiff's Counsel: Rabicoff Law LLC; Crewse Law Firm, PLLC
• Case Identification: 3:26-cv-00804, N.D. Tex., 03/12/2026
• Venue Allegations: Venue is asserted on the basis that the Defendant maintains an established place of business within the Northern District of Texas.
• Core Dispute: Plaintiff alleges that Defendant's unspecified products infringe a patent related to systems and methods for user authentication and verification, typically involving a secondary device.
• Technical Context: The technology concerns secure authentication methods for online portals and electronic payments, a field critical for e-commerce and data security.
• Key Procedural History: The complaint does not reference any prior litigation, inter partes review proceedings, or licensing history related to the patent-in-suit.

Case Timeline

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

U.S. Patent No. 8,677,116 - "Systems and methods for authentication and verification"

• Patent Identification: U.S. Patent No. 8,677,116, "Systems and methods for authentication and verification," issued March 18, 2014 ('116 Patent).

The Invention Explained

• Problem Addressed: The patent identifies a growing need for methods to securely and quickly authenticate users accessing secured internet portals (e.g., websites) or initiating online electronic payments, moving beyond traditional credential entry '116 Patent, col. 1:20-27
• The Patented Solution: The invention describes a multi-device authentication system where a user interaction is initiated on a primary computer, which provides a "reusable identifier" (e.g., as a QR code) to both a verification server and the user's display '116 Patent, abstract '116 Patent, col. 6:4-13 A user then employs a secondary electronic device (e.g., a smartphone) to capture this identifier, combine it with local user verification information, and send the combined data to the verification server for authorization '116 Patent, col. 6:20-28 If validated, the server transmits an authorization signal, granting the user access on the primary computer '116 Patent, col. 6:28-33
• Technical Importance: This approach aims to enhance security and user experience by using identifiers that do not contain sensitive user or transaction-specific information, making them simpler, safer, and faster for mobile devices to process '116 Patent, col. 6:34-62

Key Claims at a Glance

The complaint does not specify which claims are asserted, instead referencing "exemplary claims" in an unattached exhibit Compl. ¶11 Compl. ¶16 Independent claims 1 (a method) and 11 (a system) are the broadest claims in the patent. The elements of independent claim 1 are:

• Using a computer system to receive a first signal from a computer providing a secured capability, where the signal contains a reusable identifier assigned for a finite period of time.
• Using the computer system to receive a second signal from a user's electronic device, where the signal contains a copy of the reusable identifier and user verification information.
• Using a processor to evaluate, based on the signals, whether the user is authorized.
• In response to an authorization indication, using the computer system to transmit a third signal with authorization information to the electronic device and/or the computer.

The complaint does not explicitly reserve the right to assert dependent claims.

III. The Accused Instrumentality

Product Identification

The complaint does not identify any specific accused products, methods, or services by name Compl. ¶11 It refers generally to "Defendant products identified in the charts incorporated into this Count" and "Exemplary Defendant Products" Compl. ¶11 The referenced charts were not attached to the complaint as filed.

Functionality and Market Context

The complaint does not provide any description of the functionality or features of the accused instrumentalities. It makes only a conclusory allegation that the unspecified products "practice the technology claimed" by the '116 Patent Compl. ¶16

IV. Analysis of Infringement Allegations

The complaint alleges that infringement is detailed in claim charts provided as Exhibit 2 Compl. ¶16 However, Exhibit 2 was not attached to the filed complaint. The complaint's text provides only a conclusory narrative, stating that the "Exemplary Defendant Products incorporated in these charts satisfy all elements of the Exemplary '116 Patent Claims" Compl. ¶16 No specific theory of how any particular product feature meets any specific claim limitation is provided in the complaint body.

No probative visual evidence provided in complaint.

Identified Points of Contention

The complaint's lack of specificity prevents a detailed analysis of potential infringement disputes. However, should an accused product be identified (e.g., an e-commerce platform), the analysis would raise several key questions:

• Scope Questions: What specific feature of the accused instrumentality constitutes the claimed "reusable identifier"? Does this identifier function independently of user-specific or transaction-specific data as described in the patent?
• Technical Questions: Does the accused system assign its identifier "for a finite period of time" as required by claim 1, and what technical evidence supports this temporal limitation? What data transmitted from a user's device constitutes the claimed "user verification information"?

V. Key Claim Terms for Construction

The complaint does not provide sufficient detail for analysis of specific terms in the context of an accused product. However, based on the patent's disclosure, several terms in the independent claims appear central to any potential dispute.

The Term: "reusable identifier"

• Context and Importance: This term is the core of the invention. Its construction will determine whether a wide range of authentication tokens (e.g., session cookies, third-party login tokens, single-use QR codes) fall within the claim scope. Practitioners may focus on this term because the patent repeatedly distinguishes it from "one-time-use" or "unique" identifiers containing transaction-specific information '116 Patent, col. 9:8-21
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent states the term "has its broadest reasonable interpretation," including an identifier that can be "used more than once" and is "not unique to one particular user or transaction" '116 Patent, col. 9:6-12 This could support an argument that any token used for more than a single, instantaneous transaction is "reusable."
  • Evidence for a Narrower Interpretation: The specification contrasts the invention with systems where "a smartphone sends login or payment information to a webserver, the webserver can associate the user to the transaction" '116 Patent, col. 9:18-21 An embodiment describes using a "predefined and previously generated list" of identifiers in a "round robin" fashion '116 Patent, col. 9:22-41 This may support a narrower construction limited to pre-generated, non-transactional tokens that are recycled over time.

The Term: "assigned for use by the secured capability for a finite period of time"

• Context and Importance: This limitation in claim 1 adds a temporal component to the "reusable identifier." The viability of an infringement theory could depend on whether an accused system's authentication token has a defined, limited lifespan that matches this requirement.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification provides a wide range of examples, from "one or more minutes" to "one or more days" '116 Patent, col. 9:43-45, which could support construing "finite period" to cover standard session timeouts in web applications.
  • Evidence for a Narrower Interpretation: The patent describes a system where "the same reusable identifier 214 cannot be used again within the same time period," but can be reused in a subsequent period '116 Patent, col. 9:46-51 This could support a narrower construction requiring a specific lifecycle of activation, expiration, and potential reactivation, rather than a simple session timeout.

VI. Other Allegations

Indirect Infringement

The complaint alleges induced infringement, stating that Defendant sells products to customers and distributes "product literature and website materials inducing end users and others to use its products" in an infringing manner Compl. ¶14 Compl. ¶15 The factual basis for this allegation is deferred to the unattached Exhibit 2 Compl. ¶14

Willful Infringement

The complaint does not allege pre-suit knowledge of the '116 Patent. It asserts that "service of this Complaint... constitutes actual knowledge of infringement" and that Defendant's continued activities "Despite such actual knowledge" support a claim for enhanced damages Compl. ¶13 Compl. ¶14 This establishes a basis for alleging only post-filing willfulness.

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

• A foundational issue will be the identification of the accused instrumentality. The complaint makes infringement allegations against unspecified "Exemplary Defendant Products" detailed in an unattached exhibit, raising the initial question of which specific products or services of a soap company are at the center of the dispute and whether the complaint provides plausible grounds for infringement.
• A core issue will be one of definitional scope: can the term "reusable identifier," which the patent contrasts with user- and transaction-specific tokens, be construed to cover the authentication or payment processing technology used by the yet-to-be-identified accused product (e.g., a standard e-commerce platform)?
• A key evidentiary question will concern the temporal limitation of the asserted claims: what technical evidence will be required to demonstrate that an accused system's identifier is "assigned for use... for a finite period of time," and how will this claimed functionality be distinguished from conventional web session management?