USDT live
Supply 112.4B +0.8%
Tron share 53.2%
ETH share 38.4%
TRC20 gas $0.95 -2.1%
ERC20 gas $4.20
24h volume $48.2B
English · 中文

Fed Joins Regulators to Release GENIUS Act Stablecoin KYC Draft Rules: What Happens to Your USDT Card?

2026-06-19

The Federal Reserve (FRB), together with other financial regulators, has released a draft regulatory framework for payment stablecoin issuers, making clear that, pursuant to the implementation of the GENIUS Act, issuers will be required to perform identity verification (KYC) at a level equivalent to banks. This is the first time since the GENIUS Act was passed that regulators have put “what standard issuers must use to identify customers” into concrete draft rule text. The first outlet to report this was Japanese media outlet CoinPost; for the authoritative English-language draft text, readers should go directly to the Federal Reserve press release page (editor’s note: CoinPost’s report is a secondary account — for the specific provisions and the closing date of the public comment window discussed in this article, the Federal Reserve’s original text should be treated as the final authority).

What this means for USDT cardholders

The bottom line first: this news constrains stablecoin issuers (minting/redemption entities such as Circle and Tether), not your card directly. But as KYC tightens upstream at the issuer level, that pressure will propagate down the funding chain.

The degree of impact varies by position in the chain, in three tiers:

Expected timeline:

  1. Within 7 days — No card will change its account-opening or top-up process because of this draft. It is a draft, not an enacted rule.
  2. Within 30 days — Watch for whether issuers (especially Circle) release compliance statements, and whether a public comment period opens.
  3. Within 90 days — Cards operating on US-compliant rails may update user agreements and tighten requirements for proof-of-address / source-of-funds documentation.

Historical comparison: how does this differ from MiCAR or the USDC de-peg

Placing this draft on a timeline makes the picture clearer:

EventTimingNatureCore requirement for issuers
USDC de-pegMarch 2023Market risk eventExposed reserve bank exposure, no new rules
MiCAR stablecoin provisionsPhased effect from mid-2024EU statutory lawReserves, whitepaper, authorized issuance
GENIUS Act KYC draftJune 2026US draft ruleBank-level identity verification

Similarities: all three point in the same direction — regulatory treatment of stablecoin issuers is shifting from “marginal tolerance” to “held to financial-institution standards.”

Differences:

Compliance boundaries: what is and isn’t allowed right now

For ordinary cardholders, the current legal status is:

Rules vary substantially by jurisdiction; Asia-Pacific users can consult the Hong Kong compliance guide, the Singapore compliance guide, and the Japan compliance guide to understand local boundaries for card issuance and holding; US users should watch for updates to the US compliance guide.

Key milestones worth watching next

  1. The public comment period deadline — Federal Reserve drafts typically come with a comment window, and the deadline determines how quickly the rule is finalized (per the official release page).
  2. Official responses from Circle / Tether — Who states a position first, and what that position says, will signal which compliance path proves easier to follow.
  3. Updated user agreements from US-market card issuers — Whether Coinbase and Crypto.com adjust their KYC documentation requirements is the most direct “temperature gauge.”
  4. Signs of convergence between MiCAR and GENIUS standards — Once the two major jurisdictions align on KYC, issuers worldwide will face unified pressure.

Editorial recommendations

This is a compliance upgrade at the issuer level, and for disciplined cardholders it is a neutral-to-positive signal — the clearer the regulation, the more stable long-term usability becomes. The people who actually need to adjust their behavior are the small subset of users relying on US-compliant rails.