One payment, several legal routes
On November 19, 2012, the FDIC and FinCEN announced concurrent $15 million civil money penalties against First Bank of Delaware. The agencies determined that its anti-money-laundering program did not adequately address third-party payment processors. The same $15 million Treasury payment satisfied the related Justice Department settlement. It was not a $45 million aggregate fine. A separate $500,000 account was reserved for consumer claims. [1][2]
The legal distinctions matter. FinCEN’s assessment contains agency determinations accepted in a consent resolution without the bank admitting or denying them, apart from jurisdiction. The Justice Department’s civil complaint alleged fraud-related conduct under the Financial Institutions Reform, Recovery and Enforcement Act, or FIRREA. A settlement of that complaint is not a criminal conviction or a trial judgment establishing every allegation. [2][3]
The business chain behind the case
A payment processor can connect many merchants to a bank through one institutional relationship. The bank supplies access to payment collection, while the processor supplies merchant distribution and transaction files. That arrangement can reduce the work each merchant needs to begin accepting payments. It also places more than one organization between the customer who is debited and the bank that originates the collection.
The economic problem is that the visible account holder and the underlying source of transactions are different. Processor-level balances can look adequate while a particular merchant generates disputed withdrawals. A bank can have a solvent processor customer and still participate in a payment stream that raises consumer-protection or suspicious-activity concerns. Credit exposure to the processor, therefore, does not fully describe the relationship’s risk.
The Justice Department alleged that First Bank originated hundreds of thousands of debits for processors and fraudulent merchants during 2009–2011, including remotely created checks. It alleged that the bank knew of, or was willfully blind to, fraud and disregarded warning signs such as high returns. Those are the government’s allegations, rather than a finding that every merchant or every debit passing through the bank was fraudulent. [2]
What the supervisory record adds
FinCEN’s November 2012 assessment focused on weaknesses in the bank’s BSA program and oversight of processor relationships. Its significance is the connection between knowing a processor and understanding the activity that processor introduces. The consent posture leaves the agency’s determinations intact as the basis of its action but does not convert them into admissions. [3]
A separate FTC action announced in January 2012 provides contemporaneous context. The FTC alleged that Landmark Clearing processed more than 110,000 remotely created payment orders, exceeding $5.3 million, through First Bank for one merchant; more than 70% were rejected and returned. The FTC settlement imposed restrictions on Landmark and its principals. That proceeding involved different respondents and remedies, so its figures cannot be treated as a measurement of all losses in the bank case. [4]
The difference between an individual processor case and a bank-wide program case is substantial. The first can identify a transaction population and a particular customer authorization problem. The second concerns whether the bank’s information, monitoring and response were adequate across the relationships it maintained. A striking processor example supports context; it does not supply a universal loss rate.
Why a return rate is information rather than a verdict
A returned debit says that an attempted collection did not complete or did not remain settled. Its meaning depends on the reason, the denominator and the observation period. Insufficient funds, a closed account, a duplicate entry and a claimed lack of authorization are not interchangeable. Even an unusually high aggregate rate does not by itself prove intentional fraud.
A hypothetical processor with 100,000 attempted debits and 12,000 returns has a 12% count-based return rate. If 10,000 returns belong to one small merchant, the processor average conceals concentration. If the returned items are much larger than successful items, a dollar-based measure can show greater exposure than the count-based measure. These are illustrative calculations, not reconstructed First Bank results.
Returns also arrive after origination. If merchant funds have already been released, the bank or processor can face a cash obligation before it recovers from the merchant. A reserve changes who finances that interval; it does not establish whether the original debit was authorized. The distinction explains why financial protection through collateral cannot substitute for knowing what transactions represent.
There is a second information problem when a problematic merchant changes names or moves between processors. Looking at each account independently can make persistent behavior appear to be a series of new relationships. Conversely, merging unrelated merchants merely because they share a processor can overstate concentration. Reliable interpretation depends on identity and transaction context, not simply a longer list of flagged accounts.
Guidance, closure and the present-day record
The FDIC’s January 31, 2012 processor guidance described diligence and monitoring considerations. Its currently posted version records revisions in July 2014 and February 2026, with the February 3, 2026 change removing reputation-risk references. That later edited text is useful current context but should not be presented as the exact document available throughout the conduct period. Guidance also differs from the bank-specific settlement obligations. [5]
Delaware’s 2012 banking annual report records First Bank of Delaware’s dissolution effective November 16, 2012. The announcement of the enforcement settlement followed three days later. This was an institutional exit, not evidence that the bank continued operating under the same name until a recent termination. The source does not justify calling the exit an FDIC receivership failure. [6]
The October 4, 2026 status check located the original agency records and the state’s dissolution record, but no later official reversal of the 2012 settlement. That is a bounded finding from the records reviewed, not a claim that every associated private dispute has been examined. No recovery total beyond the documented settlement provisions is inferred.
The financial meaning of the case
The case illustrates a basic asymmetry in intermediated payments. Distribution can scale by adding merchants through a processor, while the bank’s exposure travels through transaction details that are less visible than the processor’s own balance sheet. Revenue can accrue on successfully submitted payments before complaints, returns or investigations reveal the cost of problematic activity.
This does not mean processor banking is inherently improper, or that high-risk activity and illegal activity are synonyms. It means that commercial distance from the merchant does not create equivalent distance from the payment consequences. The historically important outcome was a coordinated use of bank supervision, BSA enforcement and civil fraud authority, with distinct legal claims but an expressly shared monetary payment.
Sources
- FDIC / FinCEN — coordinated penalty announcement, November 19, 2012Official releaseBack to text: ↑
- DOJ — civil settlement announcement, November 19, 2012Official releaseBack to text: ↑1↑2↑3
- FinCEN — assessment 2012-01, November 2012Official source · PDFBack to text: ↑1↑2
- FTC — Landmark payment-processor settlement, January 2012Official releaseBack to text: ↑
- FDIC — processor guidance, January 31, 2012; amended February 3, 2026Official sourceBack to text: ↑
- Delaware State Bank Commissioner — 2012 annual reportFiling / report · PDFBack to text: ↑