Skip to main content
§1782 Subpoenas Aren't Just for LitigationPredicate Offenses
5 min readFor FinTech Compliance Teams

§1782 Subpoenas Aren't Just for Litigation

You've probably heard colleagues mention §1782 subpoenas in the context of cross-border litigation. However, if you're designing your fintech's PEP monitoring framework or assessing transaction monitoring gaps, understanding these discovery tools is crucial for AML investigations. The recent approval of §1782 subpoenas targeting Antigua Prime Minister Gaston Browne and associated entities in the Alfa Nero yacht case shows how U.S. courts can reach into international financial networks. Misunderstanding these tools can leave your compliance program exposed.

These misconceptions persist because §1782 is a civil procedure statute, not an AML regulation. It doesn't appear in your BSA training materials or FATF guidance. But when U.S. dollar transactions pass through U.S. banking infrastructure, §1782 becomes a practical enforcement mechanism that affects how you evaluate PEP risk and document beneficial ownership chains.

Myth 1: §1782 Subpoenas Only Apply to Active U.S. Litigation

Reality: Section 1782 of Title 28 authorizes U.S. courts to order discovery "for use in a proceeding in a foreign or international tribunal." An active U.S. lawsuit isn't necessary. The Browne case demonstrates this: four months after the initial application, the court approved subpoenas targeting financial information related to alleged theft from yacht sale proceeds. The proceeding doesn't have to be filed yet, just reasonably contemplated.

For compliance teams, this means your PEP customers can be subject to U.S. court-ordered discovery even when they're not defendants in U.S. courts. If your customer is a foreign official and their transactions touch U.S. correspondent banks, those records can be subpoenaed to support foreign proceedings or investigations. Your obligations under 31 CFR § 1010.520 (formerly 31 CFR § 103.121) to respond to FinCEN requests extend to court-ordered subpoenas, and your response timeline is measured in days, not weeks.

Myth 2: PEP Classification Is Just Enhanced Due Diligence

Reality: PEP status creates a legal predicate for investigative tools you might not anticipate. In the Browne matter, the court's order explicitly references that the Prime Minister, his immediate family members, related corporate entities, and closely associated individuals are "classified as Politically Exposed Persons, or PEPs." This classification was foundational to the subpoena approval.

When you classify a customer as a PEP under your Customer Due Diligence rule (31 CFR § 1010.230), you're not just triggering enhanced monitoring. You're creating a compliance record that can be cited in legal proceedings as evidence of heightened risk. Your PEP designation, your source of wealth documentation, and your transaction pattern analysis become part of a discoverable file. If you've documented that a customer is a senior foreign political figure but failed to identify related entities or family members in your beneficial ownership analysis, that gap becomes evidence of inadequate due diligence.

Myth 3: Procedural Dismissals Close the Case

Reality: Browne publicly stated the case was over when an appellate court struck down an earlier application on procedural grounds. The court's recent order approving the supplemental application proves otherwise. A procedural dismissal doesn't terminate the underlying investigation or prevent refiling with corrected procedure.

This matters for your Suspicious Activity Report decisions. If you've identified suspicious activity involving a PEP and you're aware of related litigation or investigations, don't assume a dismissed case means the risk has resolved. The Browne case remained active despite the earlier procedural ruling. Your ongoing due diligence obligations under 31 CFR § 1020.210 require you to monitor for new developments. If you filed a SAR two years ago and closed your internal case because you saw a dismissal notice, but the investigation continued through amended filings, you've created a gap in your continuing activity SAR analysis.

Myth 4: USD Transactions Only Create Risk When They Clear Through U.S. Banks

Reality: The Browne order specifies that the money involved "was in United States Dollars (USD), and transited the US banking structure, both when payment was made, and when the illegal diversion of funds was funneled through bank accounts located in the U.S." Notice the two touchpoints: the initial payment and the subsequent diversion. Both create U.S. jurisdiction.

If your fintech processes cross-border payments in USD, you can't rely on the "we're not a U.S. bank" defense to minimize sanctions screening or PEP monitoring. When USD moves between foreign parties, it almost always touches a U.S. correspondent account, even if only for milliseconds during SWIFT message settlement. That transit point creates the jurisdictional hook for §1782 discovery and potential money laundering charges under 18 U.S.C. § 1956. Your transaction monitoring rules need to flag USD movements involving PEPs regardless of where your entity is domiciled.

Myth 5: Discovery Applications Are One-Time Events

Reality: The Browne case involved a supplemental application filed after the Prime Minister brought defamation charges against the lawyer representing the yacht's owner. That defamation suit "gave the Court new jurisdiction to approve Discovery" against Browne and associated persons. The court has required a status report by November 9, 2026, indicating ongoing court supervision.

For compliance teams managing long-running PEP relationships, this pattern reveals how investigations evolve. A customer might not be under active investigation when you complete an annual periodic review. But if that customer later initiates litigation that touches U.S. parties or USD transactions, they can trigger new discovery authority. Your documentation practices need to assume that records you're creating today might be subpoenaed three years from now in proceedings that don't exist yet. Retain transaction narratives, risk assessment memos, and escalation decisions with that timeline in mind.

What to Do Instead

Start by mapping your PEP population against USD transaction flows, not just account domicile. If you've classified a customer as a PEP but haven't documented which of their transactions actually touch U.S. correspondent banks, you don't understand your §1782 exposure.

Second, revise your PEP due diligence templates to explicitly identify immediate family members and closely associated entities. The Browne order targets these categories specifically. If your enhanced due diligence file lists the PEP customer but doesn't map their spouse, children, or controlled entities, you haven't completed the analysis.

Third, train your SAR review team to monitor for procedural developments in known investigations. Subscribe to PACER alerts or assign someone to check dockets quarterly for customers with known litigation exposure. A procedural dismissal shouldn't close your internal case file.

Finally, adjust your document retention schedule. If you're purging PEP transaction records after five years because that's your standard retention period, you're destroying potential evidence before the §1782 application might be filed. For PEP relationships involving USD and cross-border flows, consider seven-year retention as a floor, not a ceiling.

The Browne case isn't an outlier. It's a template for how U.S. courts can reach foreign officials whose financial activity touches U.S. banking infrastructure. If your compliance program treats §1782 as someone else's problem, you're designing controls that work until they don't.

You Might Also Like