Blockchain Association presses for a narrower stablecoin KYC perimeter as GENIUS Act rules move ahead

The U.S. stablecoin policy debate is moving out of the legislative phase and into a more operational fight over where compliance should actually sit. In a comment letter submitted to federal agencies, Blockchain Association backed the basic structure of the proposed customer-identification rules for permitted payment stablecoin issuers under the GENIUS Act, while urging regulators to keep those obligations tied to direct issuer relationships rather than trying to extend them across the full life of every token in circulation. That is a narrower question than the one Congress answered when it passed the law, but it is the one that will determine how issuers, exchanges, wallets and distribution partners have to build in practice.

The proposal at issue comes from a joint rulemaking involving Treasury’s Financial Crimes Enforcement Network, the Office of the Comptroller of the Currency, the Federal Reserve, the FDIC and the NCUA. Under the GENIUS Act framework, permitted payment stablecoin issuers are treated as financial institutions for Bank Secrecy Act purposes and must maintain an effective customer identification program. In plain terms, the agencies are now translating that statutory mandate into a stablecoin-specific rulebook: who counts as a customer, what counts as an account, when identity verification has to occur, and how those obligations should interact with the rest of the anti-money-laundering stack.

Blockchain Association’s clearest point is that the agencies should preserve the proposal’s current decision to keep CIP obligations focused on primary-market activity. That means the issuer’s direct touchpoints with a user or institutional counterparty such as minting, redeeming, repurchasing, burning, reissuing and reserve-linked account activity. The trade group argues that this is not just the most workable approach but also the one most faithful to the statute, because stablecoin issuers have real operational control at those points and do not have the information needed to identify every address or end user involved in peer-to-peer transfers and secondary-market trading. If regulators tried to force issuer-level KYC across all downstream token movement, the result would be a globally expansive obligation with limited practical enforceability and a high risk of breaking open-network transferability.

The letter also drills into definitions that could matter far more than they look on first read. Blockchain Association wants regulators to clarify that a one-off redemption request from someone who is not already an account holder should not automatically create a formal account relationship. It also wants clearer boundaries around the terms account, customer and digital asset service provider so that vendors, oracle providers, analytics firms, infrastructure partners and other service relationships do not get swept into issuer CIP logic simply because they support a stablecoin business operationally. Just as importantly, the group argues that if a stablecoin issuer also operates other regulated digital-asset services, those separate activities should not be folded wholesale into the issuer-specific customer-ID regime created by the GENIUS Act.

Another important theme is reliance and implementation flexibility. The filing supports allowing a permitted issuer to rely on customer-identification work performed by other federally regulated financial institutions that already run their own CIP programs, provided the framework is clear and the issuer’s reliance is reasonable. It also asks regulators to confirm that customer information can be collected electronically and indirectly rather than only through a rigid direct-submission model. That matters because the proposed rule is being built at a moment when digital identity tooling, verifiable credentials and privacy-preserving verification methods are becoming more realistic parts of financial onboarding. The comment letter explicitly points to the need for a technology-neutral regime that can accept modern verification methods instead of hard-coding an older paper-era workflow into the stablecoin stack.

The timing issue is also significant. Blockchain Association is urging agencies to align the effective date of the customer-identification rule with the separate GENIUS Act rulemakings covering anti-money-laundering, counter-terrorist-financing and sanctions compliance. That request reflects a practical concern more than an ideological one. If the customer-ID rule goes live on a different timetable from the broader AML and sanctions framework, issuers could be forced to build compliance systems in stages, revise them again after the next rule lands, and absorb avoidable duplication in staffing, controls, vendor selection and audit design. For a sector that is supposed to be moving toward a clearer federal operating perimeter, staggered compliance dates would create a messy build sequence right when firms are trying to standardize.

For the stablecoin market itself, the stakes are larger than the narrow legal language suggests. Large issuers and distribution partners are already positioning for a world in which regulated dollar tokens are treated less like a lightly supervised crypto product and more like a distinct payments-and-cash-management category. Rules that keep KYC responsibility centered on the issuer’s direct account relationships would still impose a serious compliance burden, but they would preserve room for exchanges, custodians, wallets and other intermediaries to handle their own customer obligations within their own regulated perimeters. Rules that blur those lines too aggressively, by contrast, could make stablecoin distribution harder to scale and raise fresh questions about whether open secondary transferability can coexist with bank-style oversight.

What this filing really shows is that the GENIUS Act’s next phase will be won or lost in implementation detail. Congress already settled the basic direction of travel by putting payment stablecoins inside a federal framework with redemption, reserve and compliance expectations. Now the agencies have to decide whether that framework will be applied in a way that targets the issuer edge, where control is strongest, or in a way that reaches much further into downstream market structure. The comment letter does not challenge the idea that stablecoin issuers should run robust customer-identification controls. It argues instead that the controls should be mapped to the parts of the system issuers can actually supervise. If regulators hold that line, the result could be a more workable path for compliant stablecoin growth in the U.S.; if they do not, the industry’s federal rulebook could become much harder to operationalize than the statute itself suggests.