The stablecoin identity rule covers issuance and redemption, not what happens next
Blog post from Didit
Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.
Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.
This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.
Five U.S. financial regulators have jointly proposed customer identification requirements for permitted payment stablecoin issuers under the GENIUS Act, with comments due by 21 August 2026 and a potential final-rule effective date 12 months after issuance. Modelled on bank customer identification rules, the proposal would require issuers to collect customers’ names, birth or formation dates, physical and mailing addresses, and identification numbers; verify identities; screen against designated terrorist lists; and retain relevant records for five years. The requirements would apply only to direct issuer-customer relationships in the primary market, including issuance, redemption, conversion, custody, and related services, while transactions among other stablecoin holders in the secondary market would remain outside the rule as drafted. Federal Reserve Governor Michael Barr supported the proposal but warned that the framework may not sufficiently address illicit-finance risks in secondary-market activity, making its possible expansion a central question for public comment. The proposal is one of five separate stablecoin-related rulemakings issued by federal agencies between May and July 2026, and FinCEN estimates that it would initially affect about 50 issuers with approximately 1,000 customers each.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.