GENIUS Act pushes stablecoin compliance into banks’ back offices

Banks, credit unions, and crypto-native firms seeking to issue payment stablecoins are redesigning compliance systems as regulators move to implement the GENIUS Act. The 2025 law requires 100% reserve backing and adds new reporting, redemption, and risk management duties, with the biggest operational shift happening in settlement and recordkeeping.

100% reserves and tighter issuer requirements

The GENIUS Act, enacted in July 2025, requires permitted payment stablecoin issuers to maintain reserves equal to 100% of outstanding coins using specified short-term, dollar-denominated assets. Issuers must publish redemption procedures, submit frequent regulatory reports, and make risk management central to operations.

The customer-facing payment flow is expected to stay familiar. Consumers already use debit cards, mobile applications, and online payment services, according to a Sept. 1 overview by Braumiller Law Group.

Regulators build separate rule frameworks

Federal agencies are developing the compliance structure in parts. The Office of the Comptroller of the Currency has proposed rules covering federally qualified issuers, certain state and foreign issuers, and custody activities, followed by proposals addressing Bank Secrecy Act, anti-money laundering, and sanctions compliance.

The Federal Deposit Insurance Corp. has addressed reserves, redemption, capital, custody, safekeeping, risk management, and tokenized deposits. The National Credit Union Administration has proposed application procedures and risk standards for credit union issuers.

As these rules take shape, prospective issuers and digital asset custodians are weighing whether to pursue a state charter or accept federal supervision. They are also preparing for greater transparency and reporting at the level of individual accounts and wallets, including customer identification, sanctions screening, and suspicious activity monitoring.

Monitoring automated micropayments at machine speed

A central compliance challenge is applying controls to automated micropayments that fall below traditional reporting thresholds and occur without human intervention. Systems built around customers initiating discrete transactions may need to monitor thousands of machine-generated payments executed in rapid succession.

The shift is tied to an internet-native payments model. Coinbase’s x402 protocol, for example, uses the web’s existing “402 Payment Required” status code to let people or machine clients make payments through ordinary internet requests without conventional account or session structures.

In June, Coinbase announced work with Amazon Web Services infrastructure that would allow publishers and API providers using AWS CloudFront and Web Application Firewall to accept x402 payments from AI agents.

Legal questions for AI-driven payments

AI agent payments create unresolved legal and compliance issues, including who authorized an agent’s payment, when software can bind its principal, what constitutes consent, and who is responsible if an agent purchases the wrong service. Institutions also need records establishing each transaction and controls capable of running identity, AML, and sanctions checks at machine speed, including when payer and recipient are in different jurisdictions.

The overview frames the broader direction as an architecture combining regulated digital money, blockchain records, decentralized entities, and autonomous software. It points to state-recognized structures, such as decentralized unincorporated nonprofit associations, as potential legal identities for online communities, with smart contracts and payment protocols enabling software to buy and sell services.

Why it matters

The GENIUS Act provides legal legitimacy for payment stablecoins, but whether programmable, automated payments can scale depends on whether compliance systems can keep pace without weakening the safeguards built into the conventional financial system.