Fiserv Lawsuit: Judge Lets Credit Union Claims Proceed
A California federal judge refused Fiserv’s bid to toss a suit filed by a credit union, which says the payments company misled customers about its security safeguards. The dispute lands amid broader public scrutiny of how large payments vendors describe cybersecurity capabilities, allocate security responsibilities in contracts, and respond when customers say promised safeguards did not materialize.
On Thursday, Judge Walter of the federal district court in Los Angeles cleared eight claims to advance.
Judge Walter also vacated a Monday hearing as unnecessary. He said Polam Federal Credit Union could better press its arguments at summary judgment, after evidence is developed.
A ruling that keeps core claims alive can shape the leverage of both sides, because it moves the fight from pleadings to evidence and tests whether the vendor’s security promises match what customers reasonably relied on.
Allegations Over Cybersecurity and Contract Breach
According to the complaint, Fiserv breached its agreement with the institution by touting but not delivering adequate cybersecurity, leaving systems and member data exposed to unauthorized entry. The filing points generally to alleged gaps in baseline controls—such as access restrictions, monitoring, and other safeguards the credit union says were represented as in place—and frames the harm as exposure to unauthorized access and the costs of responding, remediating, and operating under heightened risk.
The lawsuit is part of a broader wave by multiple credit unions.
| Credit Union | State | Status of Lawsuit |
|---|---|---|
| Self-Help Credit Union | North Carolina | Filed; pending |
| FiCare Federal Credit Union | Florida | Filed; pending |
| Other credit union plaintiffs | New York | Pending |
| Other credit union plaintiffs | Indiana | Pending |
Across the group of cases, the claims described in the pleadings center on cybersecurity representations and alleged contract failures, and some filings also raise billing disputes, including allegations of unexpected or disputed charges connected to services, remediation, or security-related costs.
This was the first decision on a dismissal motion among that cluster of filings.
The cases described here are brought as separate credit-union suits rather than as a consolidated consumer class action, and the order does not indicate that class-action status has been granted or sought in this matter.
Polam CEO Jennifer Audette said small credit unions already face heavy burdens and shouldn’t have to fight a vendor to ensure secure systems for members.
She added the organization viewed litigation as a last resort and hopes the order shows a small cooperative can stand up to a global payments provider.
Vendor Response and Settlement Outlook
Fiserv disputes the accusations; a spokesperson has said the company disagrees with the claims and will defend the case vigorously. The company declined to discuss the newest court development.
Settlement discussions typically occur privately, and an unfavorable order can shift their tone.
In a March filing, Polam said Fiserv promised to safeguard the credit union’s information using protections equal to those applied to its own data, yet failed to do so and fell short of baseline security controls.
- Damages.
- Indemnification for losses.
- Reimbursement of contract payments.
- Attorneys’ fees.
Plaintiffs’ attorney Charles Nerko said litigation can convert vendor-related frustrations into recoveries and predicted the ruling may embolden others considering similar claims against Fiserv.
For would-be claimants asking how to join a Fiserv “class action,” the record described here does not point to a court-certified class or an open sign-up process tied to these credit-union complaints. Participation typically depends on whether you are a named plaintiff in a filed case or have counsel evaluate and bring a separate claim; potential claimants generally start by reviewing the public complaint and contacting the attorneys listed for the plaintiffs in the relevant case filings.
As for the current status of any Fiserv class action, the court development described here is a denial of dismissal in an individual credit-union case, with the next expected steps being discovery and later summary judgment briefing. The order does not provide a schedule of class-related deadlines because it does not describe a class case.
Questions about what to expect from a “class action settlement payout” are also not answered by this order. In disputes like this, any settlement amount—if one occurs—typically depends on proven losses, contract terms, causation, and the scope of any release, and outcomes can range from limited reimbursements to larger negotiated recoveries depending on documented damages and litigation risk.
Separate questions sometimes raised about “Lyons” leaving Fiserv are not addressed in the filings or court order discussed here, and the materials summarized do not identify who Lyons is in relation to Fiserv or the reason for any departure.
The court order also does not address executive compensation. The materials summarized here do not name Fiserv’s current CEO or provide the most recent annual compensation figure.