In re Checking Account Overdraft Litigation

307 F.R.D. 656, 2015 WL 3551555
CourtDistrict Court, S.D. Florida
DecidedJune 8, 2015
DocketCase No. 1:09-MD-02036-JLK
StatusPublished
Cited by3 cases

This text of 307 F.R.D. 656 (In re Checking Account Overdraft Litigation) is published on Counsel Stack Legal Research, covering District Court, S.D. Florida primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
In re Checking Account Overdraft Litigation, 307 F.R.D. 656, 2015 WL 3551555 (S.D. Fla. 2015).

Opinion

ORDER AND OPINION GRANTING CLASS CERTIFICATION

JAMES LAWRENCE KING, District Judge.

THIS CAUSE is before the Court upon Plaintiffs’ Motion for Class Certification and Incorporated Memorandum of Law (DE 3198) (the “Motion”). The Court has carefully considered the Motion, response, reply, supplemental memoranda, and the documents attached to them, as well as the parties’ voluminous evidentiary submissions and the oral argument of counsel. The Court grants the Motion, for the reasons explained more fully below.

INTRODUCTION

Plaintiffs allege that, through the use of specially designed software, Wachovia Bank, N.A., now known as Wells Fargo Bank, N.A. (‘Wachovia” or the “Bank”), engaged in a systematic scheme to extract the greatest [661]*661possible number of overdraft fees from Plaintiffs and similarly situated consumers across the country. Through the use of this software, Wachovia allegedly collected billions of dollars in excessive overdraft fees, much of it from its most vulnerable customers. Plaintiffs allege that Wachovia disseminated uniform misrepresentations and manipulated debit card transactions by, among other things, paying items even when accounts lacked sufficient funds and employing a bookkeeping device to post debit card transactions from highest-to-lowest dollar amount. Through Wachovia’s use of this standardized computer software, these alleged account manipulations were applied in the same manner to all Class members, which caused customer accounts to be depleted more rapidly and resulted in more overdrafts and, consequently, more overdraft fees. Plaintiffs additionally claim that, in many instances, fees were imposed at times when, but for Wachovia’s manipulations, there were sufficient funds in the consumers’ accounts to cover the transaction.

Plaintiffs have offered evidence showing that Wachovia did not disclose its manipulations, took active steps to keep elements of this scheme secret, misled its customers, and engaged in these manipulations despite recognizing that the scheme harmed its customers. This includes evidence that at all times during the proposed Class Period, Wa-chovia uniformly (i) listed debits in low-to-high order in monthly account statements it sent Class members and in account information made available online and (ii) touted to customers that they could track their accounts in real time online. Wachovia disputes that it has committed any violations of law.

Plaintiffs now seek certification of their common law claims for breach of contract, including breach of the contractual duty of good faith and fair dealing, unjust enrichment, and unconseionability, as well as statutory consumer protection claims under the laws of California and New Jersey.

FACTUAL BACKGROUND1

Without making conclusive findings of fact at this pretrial stage, the following record evidence'is material to the Court’s rigorous analysis of the class certification requirements.

Wachovia merged with Wells Fargo Bank, N.A. effective January 1, 2009, but continued to do business under the Wachovia name as a division of Wells Fargo.2 Before the merger, Wachovia was a wholly-owned subsidiary of Wachovia Corporation and operated in twenty-one states and the District of Columbia. In 2001, the then-existing Wachovia Bank merged into the larger First Union Corporation, retaining the Wachovia name (Ex. 1 at 79:23-80:2). At the time Wachovia and First Union merged, Wachovia posted debit transactions from lowest to highest dollar amount, while First Union posted debit transactions from high-to-low. Ex. 6 at 0100064. Thereafter, the new Wachovia posted all debit transactions from highest to lowest dollar amount. Ex. 7 at 19:13-24. This re-sequencing was formulaic, automated, and applied to all debit transactions. Id.

Debit card transactions are first authorized by Wachovia’s computer system, known as “EZ” when a customer tries to use a debit card. Ex. 8 at 0024406-07; Ex. 9 at 0042827. EZ then compares the transaction amount to a balance calculated in “real-time.” Ex. 10 at 061934-38. If the account lacks sufficient funds, EZ determines whether to authorize the transaction and overdraw the account based on a cap set by the customer’s “shadow” line of credit. Id. at 0061955-60; see also Ex. 9 at 042828-30. As the name implies, the “shadow” line of credit was only [662]*662known to Wachovia and was not disclosed to its customers.

Each authorized transaction is immediately subtracted from the “available balance”—a term of art used by Wachovia to describe the actual balance minus certain approved but unpaid transactions—but does not immediately post to the account. Rather, the posting process takes place each weeknight after midnight. Ex. 11 at 16:20-17:2. After credits are posted, Wachovia’s software reordered debit card transactions from highest to lowest, and then posted those transactions in two rounds. Ex. 12 at 0033507-08; Ex. 13 at 51:9-22. Round one was for transactions covered by sufficient funds. Id. Round two then ran for transactions that overdraw the account; the number and amount of overdraft fees is determined during round two. Id.

Plaintiffs’ evidence shows that Wachovia deliberately adopted and then repeatedly enhanced its high-to-low posting to increase the number of overdrafts so as to generate more overdraft fee revenue. Prior to its merger with Wachovia, First Union’s practice was to decline debit card transactions if there was an insufficient available balance to cover the requested transaction. In 2002, the new Wa-chovia instituted a program it called “authorization into overdraft,” under which the bank authorized transactions that exceeded a customer’s balance. Internally, Wachovia acknowledged that this new program was adopted solely to increase overdraft revenue. Ex. 20 at 0098556 (citing $30 million in additional fees, based on 84,000 additional overdraft items per month, as the only “benefit” of the program). Throughout the Class Period, the entire process of authorizing accounts into overdraft using this “shadow line of credit” was completely automated for all Class members and did not involve any manual decision making. Ex. 1 at 235:6-236:9. Furthermore, the practices used to enhance overdraft revenue were uniform in all states in which Wachovia did business. Id. at 189:9-192:14 (explaining Ex. 17 at 0116655).

Between 2001 and 2008, Wachovia launched a number of initiatives to the way transactions were posted that were designed to increase overdraft revenue.3 For example, in 2003, Wachovia began allowing customers to overdraft at ATMs, and projected this change would increase annual overdraft revenue by $20-40 million. Ex. 71 at 313275; Ex. 15 at 0117034; Ex. 72 at 312579-81. In late 2003, Wachovia began the process of reducing the number of transaction groups or “buckets” into which transactions are categorized at posting so as to achieve a “truer” high-to-low posting, and projected this change would increase annual overdraft revenue by $60-80 million. Ex. 71 at 313276; Ex. 73 at 313647-48; Ex. 74 at 314732. In early 2004, Wachovia instituted a “Priority Posting” initiative designed to result in a more true “high to low” posting process. Ex. 15 at 0117034. This enabled Wachovia to merge a greater number of transaction codes into a single bucket and process them in descending order by dollar amount. Id.; see also Ex. 16 at 0031920; Ex. 70.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
307 F.R.D. 656, 2015 WL 3551555, Counsel Stack Legal Research, https://law.counselstack.com/opinion/in-re-checking-account-overdraft-litigation-flsd-2015.