Federal Agencies Propose Strict Bank-Grade CIP Rules for Stablecoin Issuers

**What the Proposed Rule Requires**

The joint proposal lays out three obligations that map cleanly onto the CIP framework banks have run for two decades. First, issuers must apply risk-based procedures to establish and verify each customer's identity at account opening. Second, they must keep immutable records of the user data they collect and of every verification log, so an examiner can reconstruct how an identity decision was made. Third, every customer must be checked through automated comparison against federal watchlists, including terrorist and sanctions lists.

Read together, these requirements close the gap between crypto-native onboarding and the Bank Secrecy Act. An issuer can no longer treat a wallet address as a customer. It now has to know who controls that wallet, prove it knew, and screen that person before any value moves. The proposal removes the option of clearing activity under anonymous or unverified parameters entirely.

**The Secondary-Market Question Is Still Open**

The most consequential part of the proposal may be what it has not yet decided. Fed Governor Michael S. Barr noted that the agencies will examine public commentary on whether to extend identification obligations into secondary-market blockchain transactions — the peer-to-peer transfers that happen after a coin is minted.

That is a much larger surface. CIP at issuance covers the front door. Extending verification to secondary transfers would reach deep into how stablecoins actually circulate, and it would force issuers to think about identity assurance for parties they never directly onboarded. Comment letters on this point will shape whether the rule stays at the perimeter or moves into the transaction graph itself.

**Why This Raises the Onboarding Bar**

Bank-grade CIP across five agencies is not a checkbox. It demands document and biometric verification, durable audit trails, and live sanctions screening — all delivered without driving away the users an issuer is trying to convert. That tension between compliance depth and conversion is the same one every fintech faces when it scales. The difference is that stablecoin issuers now have to clear it across multiple regulators at once.

**How deepidv Closes the CIP Gap**

deepidv is built for exactly this kind of multi-agency mandate. The Arc gateway processes decentralized verifiable credentials and runs sub-150ms client-edge device-posture audits, so an issuer can establish and verify identity at wallet creation without the user drop-off that kills crypto onboarding funnels. Identity assurance happens at the edge, in well under a second, before any wallet is authorized.

Underneath Arc, deepidv's verification engine handles the rest of the CIP stack: risk-based identity checks, immutable verification logs, and automated screening against federal watchlists in a single flow. Issuers get the record-keeping an examiner will ask for and the live sanctions comparison the rule requires, without stitching together separate vendors. For teams already scaling fintech onboarding, the same engine that clears bank KYC clears stablecoin CIP — one pipeline, one audit trail, both regulated workloads.