Status: terminated July 21, 2025
The CFPB issued its Regions Bank overdraft order on September 28, 2022. On July 21, 2025, it terminated the order and waived alleged noncompliance with it. The agency’s current case page states that Regions paid the $50 million civil money penalty and made consumer payments under the redress plan. The original action should not be represented as an outstanding order.
The 2022 action concerned fees on transactions authorized when sufficient funds were available but settled after the available balance had changed. This article examines that historical mechanism and the control questions it raises. Termination changes the order’s legal status; it does not make the timing mechanics irrelevant or create a universal rule for every overdraft scenario.
Authorization and settlement are different moments
A card authorization typically occurs before final settlement. Between those events, other transactions can post, holds can change and the final amount can differ. A consumer making a purchase sees the information available at authorization, while the institution’s fee engine may evaluate a later balance. Those two perspectives can produce materially different expectations.
The important analytical question is which event determines whether the transaction creates a fee and what the customer could reasonably understand at that point. A disclosure describing balances in general terms may not make a complex sequence predictable. Product design and transaction processing therefore matter alongside the written account agreement.
A hypothetical sequence
Assume a customer has $100 available and makes an $80 card purchase that the bank authorizes. Before it settles, a separate $40 payment posts. The purchase then settles when the account lacks enough available funds under the bank’s processing logic. If the bank charges an overdraft fee on the card purchase, the customer may be surprised because the purchase was approved against sufficient funds.
This simplified example omits holds, posting rules and other details that can change actual outcomes. It is not an account from the Regions case. Its value is to isolate the authorization-to-settlement gap and show why testing a fee engine requires complete transaction sequences rather than isolated ledger entries.
Testing the state transitions
A strong test library includes delayed settlement, expired holds, partial reversals, adjusted final amounts and multiple transactions competing for the same balance. The institution should define the expected outcome before running the test and retain enough detail to reproduce it. Otherwise a complex processing result can be accepted simply because it matches the current system configuration.
Testing should compare what the bank knows with what the customer sees. Mobile balances, alerts and transaction descriptions may update on different schedules. A technically correct back-end calculation can still be confusing if the customer interface presents a materially different picture. The institution needs a consistent explanation of which balances are shown and how they relate to potential charges.
Controls beyond a disclosure rewrite
A disclosure change can improve understanding, but it does not necessarily remove a structural surprise in the fee logic. Management should evaluate whether the fee can be suppressed for the relevant transaction pattern, whether alerts arrive early enough to be useful and whether customers can act on the information before a charge becomes unavoidable.
Monitoring should classify fees by the full transaction path, not just the final negative balance. Complaint themes can help identify sequences that the original testing missed. Refunds should be linked to the cause so that repeated goodwill reversals do not hide a systematic design issue. A low complaint rate alone is weak evidence when customers may not understand why they were charged.
Revenue, access and implementation costs
Changing fee logic can reduce revenue and require processor development, data retention and customer communication. Those costs should be visible. At the same time, the institution should consider the expense of disputes, attrition and remediation. A product can appear profitable on gross fee income while imposing substantial servicing costs and damaging the broader account relationship.
Alternative designs can also have tradeoffs. Declining more transactions may avoid some fees but interfere with payments customers want completed. Providing buffers or grace periods can reduce surprises but requires clear eligibility and consistent execution. The design decision should be evaluated using customer outcomes and total economics rather than a single fee-revenue target.
Processor changes deserve regression testing against historical edge cases. A previously corrected sequence can reappear after a platform conversion if the expected customer outcome was never preserved as a testable requirement.
What the termination does and does not show
The CFPB’s termination document and case page are the appropriate sources for the order’s current status. The agency described certain fulfilled obligations and waived alleged noncompliance. Readers should not substitute a broader claim that all historical conduct was judicially approved or that every possible overdraft practice is now permissible. Those conclusions do not follow from termination of this particular instrument.
Future rule changes, court decisions or new enforcement actions could alter the legal context for specific fee practices. For this case, the durable operational lesson is to preserve the transaction history needed to explain the fee. A negative balance at settlement is only the final state; understanding how the customer and bank arrived there is essential to evaluating the outcome.
Sources
- CFPB Regions 2022 case page, including July 21, 2025 termination; reviewed September 29, 2026Official source
- CFPB Regions consent order; September 28, 2022Official source · PDF
- CFPB order terminating Regions consent order; July 21, 2025Official source · PDF