Stablecoin rulemaking reaches the KYC boundary, with industry pushing to keep peer transfers outside issuer CIP duties
A new industry comment letter backs bank-style customer identification for stablecoin issuers at issuance and redemption, but warns regulators not to extend those duties into peer-to-peer transfers. The dispute goes to the heart of whether U.S. stablecoin rules preserve open circulation once tokens leave the primary market.

The next important stablecoin fight in Washington is no longer about whether issuers will face bank-style compliance obligations. That answer is increasingly yes. The live question is where those obligations stop. In a new comment letter on the federal government’s proposed customer-identification rules for permitted payment stablecoin issuers, Blockchain Association urged regulators to preserve a clear boundary between primary-market relationships, where issuers directly onboard and redeem customers, and secondary-market activity, where tokens circulate between wallets, exchanges and applications without the issuer acting as the transactional counterparty. For stablecoin markets, that line is operationally critical.
The proposed rule itself is already substantial. Under a joint June rulemaking led by FinCEN alongside the OCC, Federal Reserve, FDIC and NCUA, permitted payment stablecoin issuers would be treated as financial institutions for Bank Secrecy Act purposes and required to maintain an effective customer identification program. In other words, the U.S. is moving from broad stablecoin legislation into the detailed compliance architecture that will determine how issuance, redemption, custody and account opening actually work in practice. That implementation layer matters just as much as the statute because it shapes which product designs remain commercially workable after the headline law is passed.
Blockchain Association’s August 21 filing does not argue against issuer KYC in general. In fact, the group explicitly supports a customer-identification framework for stablecoin issuers that is broadly comparable to the existing approach applied to other regulated financial institutions. Its main argument is narrower and more consequential: the agencies should keep those obligations tied to direct, formal relationships between an issuer and its own customers, rather than trying to push the same framework into downstream wallet-to-wallet transfers or other secondary-market activity. The letter argues that this is both what the GENIUS Act contemplates and what good policy would require, because compliance works best at points where an issuer has real operational control.
That framing leads to a series of practical requests that are easy to miss but highly relevant for product design. The filing asks regulators to clarify that a one-off redemption request from a non-account holder should not automatically create an issuer “account” for customer-identification purposes. It also asks agencies not to treat ordinary vendor relationships, software infrastructure providers, analytics partners or other commercial service arrangements as relationships that trigger issuer CIP duties. And it argues that when a redemption flows through another regulated financial institution or exchange, the issuer should not suddenly be treated as having a direct customer relationship with the downstream end user. All of those points are really about containing compliance obligations to the places where the issuer can realistically execute them.
The letter also spends considerable time on reliance and digital identity mechanics, which may prove just as important as the primary-versus-secondary debate. Blockchain Association says an issuer that reasonably relies on another federally regulated institution’s customer-identification procedures should not inherit liability for that institution’s failures simply because the issuer relied on it. It also asks agencies to confirm that required customer information can be collected electronically and indirectly, including through wallets, application interfaces, verifiable credentials and third-party data flows authorized by the user. That matters because stablecoin businesses are being built for digital onboarding from day one. A rulebook that assumes paper-era identity collection methods would undercut much of the efficiency the product category is supposed to deliver.
From a market perspective, the policy stakes are straightforward. If regulators keep CIP obligations concentrated at issuance, redemption and other direct account relationships, stablecoins can still function as transferable settlement assets once they enter circulation. If the agencies stretch those duties into peer transfers, secondary markets and smart-contract-based movement, the compliance overhead rises sharply for issuers and could reduce the usefulness of stablecoins as neutral transaction rails inside trading, payments and tokenized-asset workflows. Even critics of the industry’s position should recognize the product implication: a stablecoin that carries issuer-level onboarding friction every time it changes hands is a very different instrument from one that is tightly controlled at the edges but freely transferable within the network.
That is why this rulemaking matters far beyond legal specialists. Stablecoins increasingly serve as the cash leg for tokenized treasuries, onchain credit products, exchange settlement, cross-border payments and other real-world-asset activity. The final rule will signal whether U.S. policy is trying to preserve that utility while imposing stronger controls on issuers, or whether it is prepared to accept more friction across the full transfer chain. The industry has now put down a clear marker in favor of primary-market KYC and secondary-market openness. Regulators still have to decide whether that boundary will hold when the GENIUS Act is translated into enforceable operating rules.