6:22-cv-01075
Kioba Processing LLC v. Charles Schwab & Co Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Kioba Processing LLC (Georgia)
- Defendant: Charles Schwab & Co., Inc. (California); Charles Schwab Bank (Federally Chartered); The Charles Schwab Corporation (Delaware)
- Plaintiff’s Counsel: Daignault Iyer LLP
- Case Identification: 6:22-cv-01075, W.D. Tex., 10/12/2022
- Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Defendants maintain a "regular and established place of business" in Austin, operate a "centrally located hub" in Westlake, and conduct business with customers throughout the district.
- Core Dispute: Plaintiff alleges that Defendants’ digital banking platform, including its mobile applications, biometric authentication services, and debit card security features, infringes four patents related to biometric data processing, payment instrument security, mobile payment systems, and modifiable authentication levels.
- Technical Context: The dispute is in the financial technology (fintech) sector, focusing on the security architecture and user-interface methods for authenticating users and securing transactions in a mobile and online banking environment.
- Key Procedural History: The complaint alleges that Plaintiff’s licensing agent sent a letter to Defendant’s General Counsel on May 18, 2020, identifying the patent portfolio and inviting licensing discussions. The complaint further alleges that after receiving follow-up communications, Defendant did not respond, a fact pattern that may be used to support allegations of willful infringement.
Case Timeline
| Date | Event |
|---|---|
| 1999-01-13 | ’078 Patent Priority Date |
| 2000-06-28 | ’915 Patent Priority Date |
| 2001-01-24 | ’382 Patent Priority Date |
| 2002-03-01 | ’902 Patent Priority Date |
| 2005-07-12 | ’902 Patent Issue Date |
| 2005-08-16 | ’382 Patent Issue Date |
| 2006-09-12 | ’078 Patent Issue Date |
| 2013-05-14 | ’915 Patent Issue Date |
| 2020-05-18 | Plaintiff’s agent sends pre-suit notice letter to Defendant |
| 2020-07-23 | Plaintiff’s agent sends first follow-up email |
| 2020-10-07 | Plaintiff’s agent sends second follow-up email |
| 2022-10-12 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 6,917,902 - "System and Method for Processing Monitoring Data Using Data Profiles"
The Invention Explained
- Problem Addressed: The patent’s background section describes that traditional monitoring systems were not configured to process biometric data (e.g., from fingerprint or facial scanners) because the incoming data was often incompatible with existing reference sources and processing rules, limiting the integration of biometric security ('902 Patent, col. 1:42-58).
- The Patented Solution: The invention proposes a system that uses "data profiles" to manage and process data from various monitoring devices. Each data profile defines one or more data templates (e.g., a biometric reference), data rules for evaluation, and associated outputs or actions. A server receives monitoring data, evaluates it according to a corresponding data profile, and generates an action assessment, allowing for the integration of disparate data types into a unified, rule-based system ('902 Patent, Abstract; col. 2:23-48).
- Technical Importance: The technology provided a standardized framework for integrating diverse biometric and other sensor data sources into a cohesive, rules-based monitoring and security process (Compl. ¶39).
Key Claims at a Glance
- The complaint asserts at least independent claim 1 ('902 Patent).
- Essential elements of Claim 1 (a method) include:
- Obtaining monitoring device data characteristic of an individual from one of a plurality of monitoring devices.
- Associating at least one data profile corresponding to a data type of the obtained monitoring device data, where the data profile includes an identification of a data processing template, at least one processing rule, and at least one action assessment.
- Processing the monitoring device data according to the at least one data profile.
- Generating an action assessment corresponding to the processing of the monitoring device data.
- The complaint does not explicitly reserve the right to assert dependent claims.
U.S. Patent No. 6,931,382 - "Payment Instrument Authorization Technique"
The Invention Explained
- Problem Addressed: The patent describes the security risks of online commerce, where stored financial data is vulnerable to theft and fraudulent use. It notes a need for a system to assure merchants that a user is authorized and to give consumers greater control to prevent unauthorized transactions (’382 Patent, col. 2:7-63; Compl. ¶45).
- The Patented Solution: The invention discloses a method that gives payment instrument owners the ability to "selectively to block and unblock their payment instruments" (’382 Patent, col. 3:10-12). The method involves blocking authorization for a payment instrument "on a default basis," requiring the authorized holder to communicate with an authentication function prior to a transaction to request that the instrument be unblocked (’382 Patent, col. 4:39-50; Compl. ¶46).
- Technical Importance: The technology proposed shifting the security posture of payment instruments for online transactions from an "always active" state to an "off by default" state, giving cardholders proactive control (Compl. ¶46).
Key Claims at a Glance
- The complaint asserts at least claims 5 and 6 ('382 Patent). Claim 5 is an independent method claim.
- Essential elements of Claim 5 (a method) include:
- Blocking the authorization for a payment instrument, on a default basis, by the issuing entity.
- Communicating by the authorized instrument holder with an authentication function to subject the holder to authentication and to request that the payment instrument be unblocked.
- Authenticating the authorized instrument holder.
- If the authentication result is positive, causing the issuing entity to store the request to unblock the payment instrument.
- The complaint asserts dependent claim 6 in addition to independent claim 5.
U.S. Patent No. 7,107,078 - "Method and System for the Effecting Payments by Means of a Mobile Station"
Technology Synopsis
The patent addresses the challenge of providing a convenient way for users to select among different payment methods on a mobile device for a transaction (’078 Patent, col. 1:36-47; Compl. ¶52). The patented solution involves a network application that stores a user's payment profiles and, when a payment is to be made, generates and sends a message to the user's mobile station containing a list of alternative payment methods for selection (’078 Patent, Abstract; Compl. ¶52).
Asserted Claims
At least independent claim 1 ('078 Patent) (Compl. ¶83).
Accused Features
The complaint accuses Schwab's mobile applications, which allegedly provide a method for effecting user payments and transfers by means of a mobile station connected to a telecommunication system (Compl. ¶¶84, 87).
U.S. Patent No. 8,442,915 - "Modifiable Authentication Levels in Authentication Systems for Transactions"
Technology Synopsis
The patent recognizes that increased e-commerce led to more fraud and a need for user verification that did not cause inconvenience (’915 Patent, col. 1:25-44; Compl. ¶58). The invention provides an authentication system where a host computer receives a transaction request, sets an authentication level based on a parameter of that transaction (e.g., price), and then transmits a request for identification to the customer's mobile device to complete the authentication (’915 Patent, Abstract; Compl. ¶58).
Asserted Claims
At least independent claim 7 ('915 Patent) (Compl. ¶92).
Accused Features
The complaint accuses Schwab's two-step authentication and verification services, which allegedly set an authentication level based on transaction parameters and use a customer's mobile device to transmit identification information for authentication (Compl. ¶¶93-95).
III. The Accused Instrumentality
Product Identification
The accused instrumentalities are collectively referred to as the "Schwab Products and Services" and the underlying "Schwab System" (Compl. ¶¶14-15). Specific accused products and services include: Schwab Bank Visa Platinum Debit Cards, the Debit Card "Lock/Unlock" feature, the Schwab Voice ID Service, Schwab Two-Step Authentication services, and the Schwab Mobile applications for iOS and Android (Compl. ¶14).
Functionality and Market Context
The complaint alleges these products provide core digital banking functionality. The Schwab Mobile app allows users to access their accounts using biometric identifiers like a finger, face ID, or a preset passcode (Compl. ¶62). The complaint includes a screenshot from Schwab's website illustrating these mobile login options (Compl. p. 21). The "Voice ID" service allegedly uses voice biometrics to identify customers over the phone (Compl. ¶62). The "Lock/Unlock" feature, as depicted in a screenshot of a mobile app interface, allows a user to block new ATM transactions, purchases, and cash advances on their debit card (Compl. p. 38; ¶72). The "Two-Step Authentication" service provides an additional layer of security by sending an access code to a user's phone or other device to authorize a transaction or login (Compl. ¶¶94-95). These features are positioned as providing customers with modern, secure, and convenient ways to manage their finances.
IV. Analysis of Infringement Allegations
’902 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| obtaining monitoring device data characteristic of an individual from at least one of the plurality of monitoring devices... | The Schwab System obtains biometric data such as a fingerprint, Face ID, or Voice ID from a user's smartphone or telephone. | ¶62 | col. 2:33-36 |
| associating at least one data profile corresponding to a data type of the obtained monitoring device data, wherein the data profile includes an identification of a data processing template, at least one processing rule and at least one action assessment... | The Schwab System allegedly associates a data profile with the obtained biometric data, with the profile containing a data processing template, a processing rule, and an action assessment. | ¶63 | col. 2:38-43 |
| processing the monitoring device data according to the at least one data profile; and | The Schwab System is alleged to process the user's incoming biometric data according to the associated data profile. | ¶64 | col. 2:43-44 |
| generating an action assessment corresponding to the processing of the monitoring device data to the at least one data profile. | The system allegedly generates an action assessment (e.g., granting or denying account access) based on the processing of the biometric data against the data profile. | ¶65 | col. 2:45-48 |
Identified Points of Contention
- Evidentiary Question: A primary question will be evidentiary: what proof does the complaint or subsequent discovery provide that Schwab’s system utilizes a specific, structured "data profile" that contains the three distinct components required by the claim (a data processing template, a processing rule, and an action assessment)? The complaint’s allegations regarding this element are framed in a conclusory manner that tracks the claim language (Compl. ¶63).
’382 Patent Infringement Allegations
| Claim Element (from Independent Claim 5) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| blocking the authorization for a payment instrument, on a default basis, by the issuing entity; | Customers use the "Lock/Unlock" feature to block their Schwab debit card, which the complaint alleges constitutes blocking on a default basis. | ¶71 | col. 4:39-42 |
| communicating by the authorized instrument holder...with an authentication function to subject the authorized instrument holder to authentication and to request that the payment instrument be unblocked... | A customer logs into the Schwab Mobile app (authentication) and uses the interface to toggle the switch to unblock the card for future transactions. | ¶72 | col. 4:43-47 |
| authenticating the authorized instrument holder, and if the authentication result is positive, causing the issuing entity to store the request to unblock the payment instrument for the authorization of payments for the transaction or transactions. | After the customer is authenticated within the app, the system processes the request, causing the issuing entity (Schwab Bank) to store the unblocked status to permit future authorizations. | ¶73 | col. 4:47-50 |
Identified Points of Contention
- Scope Question: A potential dispute over claim scope may arise regarding the term "on a default basis." The infringement theory will raise the question of whether a user-initiated, persistent "lock" state, which remains until the user toggles it again, constitutes blocking "on a default basis" as contemplated by the patent, or if the term requires the instrument to automatically revert to a blocked state after each transaction or a set period. A screenshot in the complaint shows a toggle interface for "Card Locked" and "Card Unlocked" statuses (Compl. p. 38).
V. Key Claim Terms for Construction
The Term: "data profile" (’902 Patent, Claim 1)
- Context and Importance: This term is central to the asserted claim of the ’902 Patent. The infringement analysis will depend entirely on whether the architecture of Schwab's accused system can be shown to use a "data profile" that meets the claim's specific three-part definition. Practitioners may focus on whether Schwab’s system uses a more generalized rules engine that does not map onto this claimed structure.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent defines a data profile as including "an identification of a data processing template, at least one processing rule and at least one action assessment corresponding to the processing of the data processing template and at least one processing rule" (’902 Patent, col. 2:38-43). This language defines the required components without necessarily limiting their implementation to a single data structure.
- Evidence for a Narrower Interpretation: Figure 2 of the patent depicts "Data Profiles," "Data Templates," and "Data Rules" as separate logical components interacting with a server. This could suggest that a "data profile" is a distinct entity that points to or associates separate template and rule objects, potentially narrowing its construction to exclude systems where these concepts are more diffusely implemented.
The Term: "on a default basis" (’382 Patent, Claim 5)
- Context and Importance: The viability of the infringement claim for the ’382 Patent may turn on the construction of this term. The dispute will likely center on whether Schwab’s user-toggled "Lock" feature satisfies the "default" requirement.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification discusses giving owners "control over the usage of their payment instruments by giving them the ability selectively to block and unblock" them (’382 Patent, col. 3:10-12). This focus on user control could support an interpretation where the user-selected "blocked" state becomes the operative default until changed.
- Evidence for a Narrower Interpretation: The abstract states the holder communicates with the issuing entity to block authorization "on a default basis" and communicates with a trusted party "prior to a non-face-to-face transaction" to request an unblock. This may suggest that the default is a per-transaction state of being blocked, requiring an unblocking action for each new transaction, a narrower meaning than a persistent, user-toggled state.
VI. Other Allegations
- Indirect Infringement: The complaint alleges that Schwab actively induced infringement of at least claims 5 and 6 of the ’382 Patent (Compl. ¶69). The basis for this allegation is that Schwab provides its customers with instructions, advertisements, and promotional materials through its website that specifically encourage them to use the accused "Lock/Unlock" feature (Compl. ¶¶74-75). The complaint provides a screenshot of a video transcript explaining how to use the feature, which may support the element of intent (Compl. p. 35).
- Willful Infringement: The complaint alleges that Schwab had pre-suit knowledge of the patents-in-suit as of May 18, 2020, the date its General Counsel allegedly received a letter from Plaintiff's agent identifying the patents and inviting licensing discussions (Compl. ¶¶26-27). The complaint further alleges that Schwab did not respond to this letter or subsequent follow-up emails, which may be used to argue that any ongoing infringement was willful (Compl. ¶30).
VII. Analyst’s Conclusion: Key Questions for the Case
- A key evidentiary question will be one of architectural mapping: does discovery into the Schwab System reveal a technical architecture that uses a "data profile" containing the specific three-part structure (template, rule, action assessment) required by Claim 1 of the '902 patent, or will a fundamental mismatch in technical operation be shown?
- A core issue will be one of definitional scope: can the term "on a default basis" in Claim 5 of the '382 patent be construed to cover a user-selected, persistent "lock" state, or is its meaning limited to a system where a payment instrument automatically reverts to a blocked state before each transaction?
- A critical question for damages will be one of intent: given the detailed allegations of pre-suit notice provided directly to Schwab’s legal department, will Schwab’s alleged failure to respond be sufficient to establish that its continued accused conduct constituted willful infringement, thereby exposing it to the possibility of enhanced damages?