Status: a settled court judgment
The CFPB brought its Citizens Bank credit-card servicing lawsuit on January 30, 2020. The U.S. District Court for the District of Rhode Island entered a stipulated final judgment on May 23, 2023, including a $9 million civil money penalty. Citizens neither admitted nor denied the complaint’s allegations except as specified for jurisdiction. The settlement did not adjudicate the disputed facts.
The CFPB case page reviewed September 29, 2026 continued to list the judgment; no later modification or termination was identified in the reviewed public materials. This article describes the allegations and settlement accurately as such. It does not assert that the alleged historical practices continue or that the judgment represents findings after a trial.
The alleged failure mechanism
The complaint alleged that Citizens automatically denied certain billing-error and unauthorized-use claims when customers did not return a fraud affidavit. It also alleged incomplete credits for associated fees or finance charges, deficient required notices and problems with the designated credit-counseling information line. The judgment imposed conduct requirements addressing the disputed servicing practices.
The analytical issue is the relationship between internal workflow and external rights. A bank may need information to investigate, but an internal checklist cannot silently replace the legal standard for handling a claim. An incomplete form, a disputed transaction and an unauthorized-use assertion may require different decisions rather than one automatic closure code.
Separate the legal pathways
Credit-card billing-error procedures under Regulation Z and limits on liability for unauthorized use address related but distinct questions. Servicing systems should classify the customer’s issue correctly and identify the applicable requirements. A process designed for one route should not be assumed sufficient for every dispute received through the same phone number or online form.
Operationally, the bank should capture when notice arrived, what the customer reported, what information is still needed and which obligations run independently of an internal document request. Employees need escalation options for cases that do not fit the standard script. Automated decisions should preserve the evidence supporting the applicable rule and the reason for the outcome.
A hypothetical disputed purchase
Assume a customer disputes a $400 card purchase and provides details through a channel the bank accepts for the relevant claim. The bank sends a separate affidavit, but the customer does not return it. A system that simply closes the case after a fixed number of days may fail to consider the information already available and the obligations applicable to that type of dispute.
If the bank later determines that a credit is required, the correction should also examine related interest and fees. Refunding only the purchase amount can leave the account economically worse off than if the error had not occurred. This is an illustrative control example, not a determination of rights in a specific customer’s case or a reconstruction of Citizens’ individual accounts.
Refunds require an account-level reconstruction
A disputed transaction can affect interest calculations, payment allocation, minimum payments and subsequent fees. A remediation calculation should trace those effects rather than assume the principal reversal resolves every consequence. The required correction depends on the facts and applicable law, but the system must be capable of identifying downstream impacts.
Quality assurance should test resolved cases by independently recreating the expected account treatment. A sample that checks only whether a credit entry exists will miss an incorrect amount or effective date. It should also examine denied and abandoned claims, because a workflow barrier can suppress the population that reaches the final refund stage.
Fraud prevention and accessibility
A bank has a legitimate interest in detecting false claims and obtaining reliable information. The tradeoff is not between investigating fraud and complying with dispute rights. It is between a process that gathers useful evidence proportionately and one that treats an administrative obstacle as proof that a claim lacks merit.
Alternative submission methods, clear explanations and staff authority to address exceptions can improve both fraud detection and customer outcomes. They also carry costs. Management should compare those costs with avoidable repeat contacts, erroneous denials and later remediation. Measuring only case closure speed can encourage premature denials that make the headline productivity metric look better while increasing total work.
Training should explain why a requirement exists and when an exception needs review. Employees who understand only the sequence of screens may be unable to recognize that a standard closure reason conflicts with the facts of a particular claim.
Monitoring and what would change the assessment
A useful dashboard separates denials on substantive grounds from closures caused by missing paperwork, shows reopen rates and identifies the full amount of corrections. Complaint analysis should look for customers reporting repeated document requests or inconsistent explanations. The goal is to find whether the workflow creates a systematic barrier, not merely whether employees followed the workflow.
A later court order or official case update would change the legal-status description. Evidence of durable improvement would include independently tested claim handling and accurate account-level corrections, with clear populations and definitions. The general lesson remains that a servicing form is a tool for resolving a dispute; it should not become an unexamined substitute for the rights and standards governing that dispute.
Sources
- CFPB Citizens case page; lawsuit January 30, 2020, judgment May 23, 2023, reviewed September 29, 2026Official source
- Stipulated final judgment, District of Rhode Island; May 23, 2023Official source · PDF
- CFPB settlement announcement; May 23, 2023Official source
- Regulation Z section 1026.13, billing-error resolution; current text reviewed September 29, 2026Official text