FinCEN’s Reported A7 Proposal Raises Hard Questions About Crypto Wallet Attribution
A crypto wallet can reveal where money moved without revealing who controlled it. That gap sits at the heart of FinCEN’s reported A7-related proposal. For banks and compliance teams, the challenge is not simply screening addresses, but proving when a transfer involves a prohibited party—and making that judgment defensibly.
London, England
Oct 5, 2026
A targeted restriction on payments involving the A7 Network’s foreign sub-agents would confront financial institutions with a deceptively difficult question: when does a cryptocurrency address provide sufficient evidence that a transfer involves a prohibited counterparty?
The measure described in a supplied Federal Register citation would prohibit covered domestic financial institutions from maintaining accounts for or on behalf of those sub-agents, and from transmitting funds involving them. Its stated scope includes fiat currency and convertible virtual currency, or CVC, including transactions involving cryptocurrency addresses.
If confirmed and adopted in that form, the measure would bring an operational challenge into sharp focus. Identifying a named business is one task. Establishing who controls a wallet—and whether a particular payment involves that business—is another.
A targeted power, not a blanket crypto ban
The cited legal authority is Section 9714(a) of the Combating Russian Money Laundering Act. That provision gives the Treasury secretary powers to impose special measures concerning specified foreign jurisdictions, financial institutions, classes of transactions or types of accounts associated with Russian illicit finance, following a finding of primary money-laundering concern.
The distinction matters. A measure aimed at transactions involving specified foreign sub-agents would not, merely by including virtual currency, prohibit an entire blockchain or every transaction using a particular token. Its reach would depend on the operative definitions: who qualifies as a sub-agent, what establishes control by the network, and what makes a transfer one “involving” a covered party.
Those are not drafting details. They determine which payments must be stopped and which connections require further investigation rather than an automatic rejection.
An address label is evidence, not a complete answer
Blockchain records can expose transaction histories with a precision unavailable in many conventional payment systems. They do not, on their own, identify the legal or beneficial controller of every address.
A wallet attribution may rest on information supplied by an exchange, an investigative finding, a public disclosure or an analytical inference. Those sources carry different evidential weight. Institutions need to know not only what a screening system reports, but why it reports it—and whether that explanation remains current.
Custodial services complicate the picture. An address may hold funds for numerous customers rather than represent a single counterparty. Conversely, a single operator may use many addresses. A transfer passing through an intermediary also presents a different factual question from a payment sent directly to an address demonstrably controlled by a covered entity.
Effective enforcement therefore requires more than an expanding blacklist. It requires a defensible connection between the legal restriction, the identified party and the transaction under review. An unexplained risk score cannot substitute for that connection.
The opposite failure is equally consequential. Treating every intermediary as a break in the evidence chain can leave institutions unable to recognise prohibited relationships concealed behind additional accounts or wallets.
The payment route matters as much as the customer
The reported distinction between account restrictions and restrictions on transmitting funds would be particularly important. A financial institution might have no direct account relationship with a covered sub-agent yet encounter a payment involving that party through a customer or another provider.
That possibility shifts attention beyond onboarding. Customer identification, pre-transfer checks and ongoing monitoring address different parts of the risk. None is sufficient in isolation: a verified customer can introduce a new wallet, a labelled wallet can be misattributed, and an alert generated after settlement may arrive too late to prevent a transfer.
FinCEN’s existing guidance on business models involving convertible virtual currency provides relevant background. It explains how Bank Secrecy Act obligations can apply to certain virtual-currency activities. It does not establish the scope of an A7-specific restriction or make every crypto business subject to identical requirements.
For institutions assessing a targeted measure, the practical priorities would be clear: preserve the provenance of address intelligence, distinguish direct ownership evidence from indirect exposure, establish escalation procedures and record the factual basis for consequential decisions. These controls protect legitimate customers while making enforcement more credible.
The central test is not whether a firm possesses blockchain analytics. It is whether the firm can turn those analytics into reliable, legally relevant decisions.
Source and status note: The supplied Federal Register link is dated October 5, 2026. Its contents, publication status, definitions and comment deadline have not been independently verified here. The proposal-specific discussion above is therefore conditional on the supplied description being accurate. A notice of proposed rulemaking does not itself make a proposed prohibition effective, and an agency finding is not a criminal conviction of any particular person or entity.