The Credential That Forgets You: How FinCEN, the GENIUS Act, and a Mobile Driver's License Are Quietly Rewriting KYC
ZoeLion
The document that matters is nine pages long and reads like an afterthought. FinCEN issued guidance permitting banks to satisfy their Customer Identification Program obligations by relying on government-issued digital credentials β mobile driver's licenses among the acceptable instruments. There was no press tour, no ribbon, no televised handshake. Just a line in a rulebook and a quiet recomposition of what "know your customer" is allowed to mean.
Now sit with a smaller scene. On a Tuesday morning, a compliance analyst at a mid-sized American bank types a date of birth into a screen and waits. What returns is not a name, not an address, not a photograph laminated onto a polycarbonate rectangle. It is a single bit. Over twenty-one, or not. On a sanctions list, or not. A resident of this jurisdiction, or something else. The rest of the person β the nine digits that have trailed them through every credit check, every lease application, every emergency room intake form β remains inside a chip in a phone, unspoken and unharvested. That is the silence between transactions I have spent the better part of a decade trying to hear. And for the first time, the architecture of American financial compliance has begun to make room for it.
The context here matters more than the announcement. The Bank Secrecy Act is a fifty-year-old instrument built on an assumption that has never been audited in a court of constitutional law: that the safest way to prevent financial crime is to force intermediaries to accumulate their customers' most sensitive facts and hold them, forever, in databases that grow heavier with every passing quarter. Under that doctrine, a bank is not merely a gatekeeper. It is a warehouse. Its vaults hold not only money but identity β names, dates of birth, residential addresses, identification numbers, the connective tissue of a person's public existence. The Customer Identification Program is the intake mechanism for that warehouse, and for two generations it has been treated as the price of admission to the dollar system.
Then the warehouse caught fire, twice, in public.
Coinbase disclosed a breach affecting 69,461 customers β a precise, almost forensic number that suggests the company knows exactly which files left the building. Names, addresses, partial Social Security numbers, and enough context to weaponize all of it. Passwords and private keys were not taken; the loss was not of access but of identity, which is in some ways worse, because identity is the raw material of social engineering, impersonation, and the slow extortion of people who never chose to be custodians of their own risk. The company's chief executive responded not with a compliance mea culpa but with a broader provocation: that Congress should reconsider the Bank Secrecy Act and its anti-money-laundering apparatus altogether, and that the constitutionality of compelled data retention is itself an open question.
Revolut, meanwhile, supplied the second data point in the same grim series. A different platform, a different architecture, the same structural failure mode. The pattern is no longer anecdotal. It is a property of the design.
Into this breach-scarred landscape walks Hester Peirce, the SEC commissioner who has spent years as the agency's most consistent internal dissent on matters of digital assets. Her proposal is not about trading, custody, or tokens. It is about identity. She wants widespread adoption of reusable digital credentials β attribute-based instruments that can prove a predicate about a person without disclosing the person. That someone is of legal age. That someone holds a particular nationality. That someone appears, or does not appear, on a sanctions list. The verifier learns the answer and nothing else. The subject discloses a fact and retains the rest.
She was careful to note that these are her own views, not the formal position of the Commission. That caveat is doing a great deal of work, and I want to be precise about it: this is an influential internal signal, not official policy. But signals from inside the machinery of American securities regulation do not float free of the machinery. FinCEN's guidance landed in the same window. And the proposed rules under the GENIUS Act β the legislative framework that would formally pull dollar-pegged stablecoin issuers into the Bank Secrecy Act's definition of a financial institution β already contemplate digital credentials as one permissible component of identity verification. Three separate organs of the American state, moving in the same direction, at different speeds, with different levels of conviction.
I have watched enough policy cycles to be suspicious of convergence. Convergence is often coincidence wearing a suit. But this is not coincidence. It is a recognition, arriving late and reluctantly, that the data-hoarding model of compliance has become the single largest uninsured liability in the financial system.
The technical substance deserves more rigor than the headlines gave it. Attribute-based credentials are not a new cryptographic idea. They sit in the same conceptual neighborhood as the W3C's verifiable credentials and decentralized identifier work β a lineage of standards that has been gestating for years in academic cryptography and enterprise identity circles without ever finding a mass-market forcing function. The forcing function has now arrived, and it is not ideological. It is actuarial. Every year a firm holds a customer's unredacted identity, it is accruing a liability that no insurance market prices correctly, because the tail risk of a breach is correlated across every firm that stores the same facts in the same shape. When Coinbase and Revolut fail in the same way within the same news cycle, they are not two unlucky companies. They are two instances of one design.
What the credential model changes is where the raw data lives. In the current regime, the verifying institution collects, stores, and reconciles original documents β the passport scan, the utility bill, the nine digits. It must be able to reproduce them on demand for auditors, subpoenas, and law enforcement. The information is an asset on the balance sheet of trust and a liability on the balance sheet of risk, and American banks have spent forty years pretending the second ledger does not exist. Under the credential model, the verification institution never touches the original. It receives a cryptographic assertion, checks its authenticity against the issuer's public key, and discards it. The phrase that circulates in identity-engineering circles is verify-then-forget. I prefer, privately, to call it the architecture of useful amnesia.
The compliance consequences for stablecoin issuers are where the concrete money sits, and this is the part the market has not priced. The GENIUS Act's proposed rules, as parsed from the underlying materials, require issuers to maintain a Customer Identification Program, to obtain the familiar quartet of name, date of birth, address, and identification number, and β this is the sentence that should be read twice β to retain identity information for five years, including periods after an account closes. Under the current draft logic, stablecoin issuers are positioned as financial institutions under the Bank Secrecy Act, which extends to them not only the intake obligation but the downstream apparatus: suspicious activity reporting, counter-terrorist financing duties, and the whole intelligence role that banks have quietly performed as unpaid auxiliaries of the state since 1970.
So we arrive at a genuinely strange juncture. The same regulatory moment that opens the door to digital credentials also codifies five years of compelled retention. These two impulses are not reconciled. They are stacked.
The practical result is a dual-track transition, and I have seen enough of these to know how they behave in the wild. Large issuers will run their legacy KYC stack alongside a credential-verification pilot, because no compliance officer in history has ever been fired for keeping the old system running. Small issuers will face the arithmetic differently. Five years of identity retention plus five years of verification records, plus the security engineering required to defend both, plus the human review layer β this is not a rounding error. It is a fixed cost, and fixed costs are how markets concentrate. The stablecoin sector, which likes to imagine itself as permissionless by nature, is about to discover a permissioning mechanism it did not vote for: the actuarial cost of holding other people's secrets.
Here is the insight I would flag for anyone who thinks this is purely a privacy story. It is not. It is a value-capture story. If verification replaces collection, the economic center of gravity in compliance shifts from the firms that aggregate identity data β the KYC vendors, the document-verification suites, the database operators whose product is essentially a well-guarded pile of other people's facts β toward a different layer entirely: the issuers of credentials and the verifiers of credential status. The moat moves from custody to cryptography. The business of knowing your customer becomes, structurally, the business of not knowing them.
And that is where the contrarian reading becomes unavoidable.
Because verify-then-forget does not abolish surveillance. It relocates it. When a verifier no longer holds the data, the data must still exist somewhere, and that somewhere is the issuer β almost certainly a government, since the only credentials worth trusting at scale are the ones backed by a state's monopoly on authoritative records. Peirce's framing celebrates the disappearance of the intermediary's data hoard. But the trust anchor simply migrates upward, to the entity that signs the credential and the entity that maintains the status registry. And a status registry is a list. A list of who is valid and who has been revoked. A list that must be queried in real time, which means the act of verification itself becomes observable β a signal leaking, transaction by transaction, into infrastructure that nobody elected.
This is the paradox of transparency in a cashless society, and it does not vanish just because the mechanism becomes elegant. A selective-disclosure proof is still a disclosure. It is a smaller one, a more disciplined one, one that refuses to surrender the whole person in exchange for a single predicate. That is real progress. But progress is not absolution. If the United States Treasury can confirm whether a given cryptographic assertion corresponds to an individual on a sanctions list without ever learning the individual's name, it has gained a monitoring capability that is simultaneously more privacy-preserving and more penetrating than anything the current regime offers. Both things are true. Neither cancels the other.
The technical dependencies are also being ignored, and I say this from the particular vantage of someone who has spent months inside the guts of a sovereign digital currency pilot and emerged with a habit I cannot shake: looking for the parts of the diagram that have no vendor. Attribute-based credentials need a public key infrastructure to bind issuers to keys. They need revocation lists and status endpoints, because credentials expire, get lost, get stolen, and get clawed back when a court orders it. They need clock synchronization and availability guarantees, because a verification endpoint that goes down is a bank that stops opening accounts. None of this appears in the policy discussion. The conversation is happening at the level of principle, while the failure modes live at the level of plumbing. I have seen a three-day outage in a national payments rail produce more human damage than a decade of theoretical debates about decentralization.
And the current mechanism, as the parsed materials make clear, does not yet reach the portable model Peirce describes. What is being proposed is a hybrid: conventional collection running alongside credential verification, with the two systems required to trust each other's outputs. Hybrids are where standards go to die. They persist for a decade because every participant has an incentive to keep both doors open, and the cost of the redundancy is paid by users who are asked to prove themselves twice.
There is one more asymmetry worth naming, and it should worry American policymakers more than any privacy advocacy group ever will. If licensed, onshore issuers bear the full weight of Customer Identification Programs, five-year retention, and verification-record obligations, while offshore or unlicensed issuers bear none of it, then the regulatory perimeter becomes a competitive disadvantage. The dollar-pegged stablecoin market has always had an offshore reflex. Compliance arbitrage is not a hypothetical; it is a business model. And the strange outcome of a well-intentioned reform could be that the most regulated dollar tokens lose share to the least regulated ones β which is, if you squint, a description of how the eurodollar system was born.
I keep returning to something I learned auditing yield-bearing instruments that promised stability and delivered maturity mismatch. The lesson was not that the instruments were fraudulent. It was that structural fragility hides inside well-designed components, because every component works exactly as specified right up until the moment the system's assumptions stop holding. Compelled retention worked as specified. Until the breach. Credential revocation works as specified. Until the registry becomes the target.
So where does this leave the cycle? Peirce's proposal, FinCEN's guidance, and the GENIUS Act's draft provisions are not a revolution. They are the first honest admission, from inside the American state, that the cost of knowing everything has exceeded its benefit β and that a system which verifies without collecting might, at last, be cheaper to run and safer to hold. That admission is a shift of real significance, and I do not want to understate it. Reusable credentials backed by government-issued instruments, recognized by a financial regulator, are the closest the industry has come in a decade to a compliance architecture that treats privacy as an engineering constraint rather than a public-relations posture.
But the takeover is not complete, and the mechanism that will decide the outcome is unglamorous: the revocation list. Whoever maintains it holds the switch. Whoever queries it leaves a trace. Whether that switch is public, permissionless, auditable, and resistant to quiet administrative expansion will determine whether verify-then-forget becomes a genuine reduction of surveillance or simply its more elegant successor. The cryptography is the easy part. It always is.
The harder question, the one I cannot answer and will not pretend to, is this: in a system where the state issues the credential, the state knows when the credential is revoked, and the state controls the registry that every transaction must consult β have we minimized the data, or have we simply moved the hoard somewhere we cannot see it? I have been listening to the silence between transactions for a long time. What I hear now is quieter than before. I am not yet certain that quieter means emptier.