BenedorTSE LLC v. Wells Fargo Bank NA

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: BenedorTSE, LLC (Delaware)
  • Defendant: Wells Fargo Bank, N.A. (National banking association, main office in South Dakota, principal place of business in California)
  • Plaintiff's Counsel: Waddey Acheson LLC
• Case Identification: 3:25-cv-01335, M.D. Tenn., 01/14/2026
• Venue Allegations: Venue is alleged to be proper because Defendant Wells Fargo has committed acts of infringement in the district and maintains a regular and established place of business, including a specific bank branch located in Nashville, Tennessee.
• Core Dispute: Plaintiff alleges that Defendant's Wells Fargo Mobile banking application and its supporting systems infringe three U.S. patents related to technology for secure electronic transactions.
• Technical Context: The technology involves methods for authenticating online transactions by generating and transmitting encrypted data that binds a user's identity to their specific hardware device, aiming to enhance security without exposing sensitive information to merchants.
• Key Procedural History: The complaint alleges a long history between the parties, including licensing discussions from 2009 to 2013. It is also alleged that Defendant Wells Fargo was made aware of the patents-in-suit during the prosecution of its own patent applications, where one of the asserted patents was cited against it by a USPTO examiner. These allegations are presented to support claims of pre-suit knowledge and willful infringement.

Case Timeline

Date	Event
2000-12-01	Earliest priority date for all Patents-in-Suit; Original Application filed
2009-01-01	Approximate date licensing/merger discussions began between Benedor and Wells Fargo/Wachovia
2011-07-01	Approximate date Benedor attempted to engage Wells Fargo CTO
2012-04-25	Wells Fargo files its U.S. Patent Application 13/456,157
2012-09-04	U.S. Patent No. 8,260,723 issues
2012-12-31	Approximate date Wells Fargo executive described new security program
2013-03-01	Approximate date Wells Fargo allegedly became aware of the '723 Patent and its infringement
2013-06-11	U.S. Patent No. 8,463,713 issues
2015-01-06	Wells Fargo's U.S. Patent No. 8,930,271 issues
2016-07-26	U.S. Patent No. 9,400,979 issues
2026-01-14	Complaint Filing Date

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

U.S. Patent No. 9,400,979 - Transactional Security Over a Network, issued July 26, 2016

The Invention Explained

• Problem Addressed: The patent family addresses the state of the art in e-commerce prior to December 2000, which was characterized by insecure and inconvenient payment systems Compl. ¶8 Methods like SSL only protected data in transit, leaving it vulnerable on merchant servers, while more advanced protocols were too cumbersome for widespread adoption Compl. ¶¶9-10 A technological gap existed for a practical method to cryptographically bind a user's identity to their specific device for a transaction Compl. ¶14
• The Patented Solution: The invention proposes a method where the user's device performs authentication by generating and transmitting an encrypted code for authorization Compl. ¶1 Compl. ¶16 This method uses a processor on the user's device to read a hardware identifier and combine it with a user-agreement identifier, creating an encrypted user code that is valid for only a single transaction request '979 Patent, col. 35:1-30 This code is sent to a provider for authorization, avoiding the transmission of sensitive information like credit card numbers to the merchant '979 Patent, col. 35:31-41
• Technical Importance: This approach sought to provide "person-present" verification for online transactions by treating the user's personal device as a security token, enhancing security while improving user convenience Compl. ¶14

Key Claims at a Glance

• The complaint asserts infringement of at least Claim 1 of the '979 Patent Compl. ¶42
• The essential elements of independent Claim 1, as paraphrased by the complaint, include:
  • receiving a user-entered password via a graphical login interface;
  • determining whether the entered password was valid;
  • after validation, reading a device-specific hardware identifier from the user's device;
  • determining whether the device identifier was valid or recognized for the user's account;
  • retrieving from device storage a user identifier corresponding to the user's agreement with Wells Fargo;
  • creating encrypted user data that includes both the user identifier and the device identifier; and
  • transmitting the encrypted data to Wells Fargo's servers to request transaction authorization. Compl. ¶42
• The complaint does not explicitly reserve the right to assert dependent claims for this patent, but makes a general allegation of infringement of "one or more claims" Compl. ¶41

U.S. Patent No. 8,463,713 - Transactional Security Over a Network, issued June 11, 2013

The Invention Explained

• Problem Addressed: As a member of the same patent family, the '713 Patent addresses the same deficiencies in prior art e-commerce security as described for the '979 Patent Compl. ¶¶8-14
• The Patented Solution: The '713 Patent describes a similar method for securing transactions. It involves a computerized device receiving a password, reading a hardware identifier, retrieving a user agreement identifier, and creating an encrypted user code from those identifiers '713 Patent, col. 37:13-38 This encrypted code is then transmitted for authorization, ensuring that personal payment information is not directly exposed during the transaction Compl. ¶16 '713 Patent, col. 35:31-41
• Technical Importance: The invention provided a framework for using a customer's own device as an authentication factor, aiming to make online transactions more secure and convenient than prevailing methods Compl. ¶14

Key Claims at a Glance

• The complaint asserts infringement of at least Claim 13 of the '713 Patent Compl. ¶51
• The essential elements of independent Claim 13, as paraphrased by the complaint, include:
  • receiving a user-entered password via a graphical login interface;
  • determining whether the entered password was valid;
  • upon validation, reading a hardware identifier from the user's device;
  • determining whether the hardware identifier was valid or recognized;
  • retrieving a user-agreement identifier corresponding to the user's agreement with Wells Fargo;
  • creating encrypted user data combining the user-agreement identifier and the hardware identifier; and
  • transmitting the encrypted data to Wells Fargo in a request for an authorization decision. Compl. ¶51
• The complaint alleges infringement of "one or more claims" of the '713 Patent, suggesting the possibility of other asserted claims beyond Claim 13 Compl. ¶50

U.S. Patent No. 8,260,723 - Transactional Security Over a Network

• Patent Identification: U.S. Patent No. 8,260,723, "Transactional Security Over a Network," issued September 4, 2012 Compl. ¶20
• Technology Synopsis: The '723 Patent, part of the same family, describes a method to secure purchase transactions by creating an "encrypted customer code" on a user's device '723 Patent, abstract This code combines a customer identifier string, hardware identifiers, and a unique count value, and is transmitted to a merchant and a verification entity for authorization without exposing the underlying sensitive data Compl. ¶60 '723 Patent, abstract
• Asserted Claims: The complaint asserts infringement of at least Claim 13 Compl. ¶60
• Accused Features: The Wells Fargo Mobile application and its supporting systems are alleged to practice the claimed method by generating and transmitting encrypted identifiers for transaction authorization (Compl. ¶24; Compl. ¶25).

III. The Accused Instrumentality

Product Identification

The "Accused Instrumentality" is identified as the "Wells Fargo Mobile" application for iOS and Android devices, operating in conjunction with Wells Fargo's supporting computer systems Compl. ¶1 Compl. ¶24

Functionality and Market Context

The complaint alleges the Accused Instrumentality is used by millions of customers to access financial accounts and authorize transactions Compl. ¶24 Its core accused function is practicing the patented methods for "generating and transmitting encrypted user and device identifiers to authorize transactions" Compl. ¶1 No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

'979 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving a user-entered password via a graphical login interface	The complaint alleges the Accused Instrumentality receives a user's password through its login screen.	¶42	col. 35:15-17
determining whether the entered password was valid	The Accused Instrumentality is alleged to validate the user's entered password.	¶42	col. 35:18-19
after validation, reading a device-specific hardware identifier from the user's device	Upon password validation, the Accused Instrumentality is alleged to read a hardware identifier from the mobile device.	¶42	col. 35:20-22
determining whether the device identifier was valid or recognized for the user's account	The Accused Instrumentality is alleged to determine if the read hardware identifier is valid for the user's account.	¶42	col. 35:23-25
retrieving from device storage a user identifier corresponding to the user's agreement with Wells Fargo	The complaint alleges the Accused Instrumentality retrieves a user identifier related to the user's agreement.	¶42	col. 35:26-30
creating encrypted user data that includes both the user identifier and the device identifier	The Accused Instrumentality is alleged to create an encrypted data package containing both the user and device identifiers.	¶42	col. 35:31-34
transmitting the encrypted data to Wells Fargo's servers to request transaction authorization	The Accused Instrumentality is alleged to transmit the encrypted data to Wells Fargo's servers to authorize a transaction.	¶42	col. 35:35-38

'713 Patent Infringement Allegations

Claim Element (from Independent Claim 13)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving a user-entered password via a graphical login interface	The complaint alleges the Accused Instrumentality receives a user's password through its login screen.	¶51	col. 37:15-17
determining whether the entered password was valid	The Accused Instrumentality is alleged to validate the user's entered password.	¶51	col. 37:18-19
upon validation, reading a hardware identifier from the user's device	Upon password validation, the Accused Instrumentality is alleged to read a hardware identifier from the mobile device.	¶51	col. 37:20-21
determining whether the hardware identifier was valid or recognized	The Accused Instrumentality is alleged to determine if the read hardware identifier is valid or recognized.	¶51	col. 37:22-23
retrieving a user-agreement identifier corresponding to the user's agreement with Wells Fargo	The complaint alleges the Accused Instrumentality retrieves an identifier related to the user's agreement with the bank.	¶51	col. 37:24-28
creating encrypted user data combining the user-agreement identifier and the hardware identifier	The Accused Instrumentality is alleged to create an encrypted data package combining the agreement and hardware identifiers.	¶51	col. 37:29-32
transmitting the encrypted data to Wells Fargo in a request for an authorization decision	The Accused Instrumentality is alleged to transmit the encrypted data to Wells Fargo's servers for authorization.	¶51	col. 37:33-36

• Identified Points of Contention:
  • Technical Questions: The complaint makes conclusory allegations without providing detailed technical evidence of the Accused Instrumentality's internal operations. A central question will be whether the Plaintiff can produce evidence that the Wells Fargo Mobile app actually performs the specific step of "reading a ... hardware identifier from the user's device" Compl. ¶42 Compl. ¶51 Modern mobile operating systems (iOS and Android) impose significant privacy restrictions that may limit or prevent applications from accessing persistent, unique hardware identifiers.
  • Scope Questions: The dispute may turn on the definition of key terms. For example, what the Accused Instrumentality accesses on the user's device and what the patents mean by "hardware identifier" raises a question of definitional scope. Similarly, the nature of the "user-agreement identifier" or "user identifier" in the accused system versus what is contemplated by the patents will be a potential point of contention.

V. Key Claim Terms for Construction

• The Term: "hardware identifier" / "device-specific hardware identifier"

• Context and Importance: This term is critical because the core of the invention involves binding a transaction to a specific physical device. The feasibility of an application accessing a true "hardware identifier" (like a CPU or motherboard serial number) on modern mobile devices is questionable due to OS-level privacy controls. The case may hinge on whether the identifier allegedly used by Wells Fargo falls within the construed scope of this term.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent specifications provide examples but do not appear to explicitly limit the term to only those examples. A party could argue that any unique device string, even one generated by software but persistent for the device, serves the inventive purpose of identifying the device and thus falls within the claim's scope.
  • Evidence for a Narrower Interpretation: The specification of the related '723 patent provides concrete examples, such as "serial numbers from the motherboard, the hard drives, the processor, etc." '723 Patent, col. 7:13-16 A party may argue these examples of physical, permanent component identifiers define the term's scope, thereby excluding software-based or resettable advertising identifiers commonly used in mobile apps today.

• The Term: "user-agreement identifier" / "user identifier corresponding to the user's agreement"

• Context and Importance: The definition of this term is central to how the user is linked to the transaction. Practitioners may focus on this term because its construction will determine whether a standard username suffices, or if a more specific identifier tied to an explicit contractual agreement is required.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The '713 patent specification describes a "user identifier string" as potentially being a simple "alphabetic, numeric, or alpha-numeric string of characters that the financial institution uses to identify the customer" '713 Patent, col. 29:3-8, which could support interpreting the term to cover a standard username.
  • Evidence for a Narrower Interpretation: The patents repeatedly frame the invention in the context of a binding "agreement" between the user and the verification entity, where the user accepts responsibility for transactions '713 Patent, col. 33:55-67 A party could argue the "user-agreement identifier" must therefore be an identifier that specifically and uniquely represents this binding legal agreement, rather than just a generic username.

VI. Other Allegations

• Indirect Infringement: The complaint alleges both induced and contributory infringement. The inducement theory is based on allegations that Wells Fargo provides the Mobile App and "actively and knowingly encouraged and instructed" customers to use it in an infringing manner Compl. ¶44 Compl. ¶53 Compl. ¶62 The contributory infringement theory is based on allegations that the app is a material component of the invention, is known to be specially made for infringement, and is not a staple article of commerce suitable for substantial non-infringing use Compl. ¶45 Compl. ¶54 Compl. ¶63
• Willful Infringement: The willfulness claim is based on alleged pre-suit knowledge of the patents and the infringement. The complaint alleges this knowledge arises from multiple sources, including: direct licensing discussions between 2009-2013 Compl. ¶27; Wells Fargo's prosecution of its own patents, during which the '723 Patent was cited by the USPTO examiner as prior art Compl. ¶36; and the fact that dozens of patents in Wells Fargo's own portfolio allegedly cite the patents-in-suit Compl. ¶¶38-39

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

• A central issue will be one of claim construction and technical scope: can the term "hardware identifier", which is rooted in the context of 2000-era computer components with accessible serial numbers, be construed to read on the types of device identifiers that a mobile application can access on modern, privacy-hardened operating systems like iOS and Android?
• A key evidentiary question will be one of proof: beyond the conclusory allegations, what technical evidence can the Plaintiff provide to demonstrate that the Wells Fargo Mobile app actually performs each specific, ordered step of the asserted method claims, particularly the reading of a device-specific identifier?
• A significant focus of the litigation may be on willfulness: given the extensive history alleged in the complaint-including direct licensing negotiations and knowledge from Wells Fargo's own patent prosecution-the factual record surrounding Defendant's state of mind and continued use of the accused technology after notice will be a critical and likely contentious aspect of the case.