Invest1 publisher3 min readPublished
Stablecoin applicants must choose a supervisor while the OCC's rules are still proposals
A Sept. 1 overview from Braumiller Law Group says the GENIUS Act rebuild lands in bank back offices, where wallet-level screening has to run on micropayments an AI agent can trigger below reporting thresholds.
The Investor · Invest desk

What happened
- The GENIUS Act, enacted in July 2025, requires permitted payment stablecoin issuers to back every outstanding coin with reserves in specified short-term, dollar-denominated assets.
- Prospective issuers and digital asset custodians are evaluating whether to pursue a state charter or accept federal supervision, according to a Sept. 1 Braumiller Law Group overview.
- Coinbase said in June it was working with Amazon Web Services infrastructure so publishers and API providers on CloudFront and Web Application Firewall could accept x402 payments from AI agents.
- The overview says the customer-facing experience of digital payments will not change much, and that the work lands in back-office compliance, settlement and recordkeeping systems.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- constraint Screening at the level of individual wallets sizes an issuer's compliance capacity to the number of payments it clears, so a customer base that is mostly software clients is budgeted by transaction count.
- exposure An institution accepting agent payments has to be able to say who authorized one, when software could bind its principal and who pays when an agent buys the wrong service.
- cost Crypto-native applicants carry the larger bill, because they are building disclosure, operational and supervisory practices that banks and credit unions already run.
Reserves equal to 100% of outstanding coins, held in the short-term dollar-denominated assets the statute names, leave zero of the balance to lend [1][1]. A deposit-funded bank earns a spread by lending short-dated money out for longer. A permitted payment stablecoin issuer earns whatever the specified assets yield. This is the cheap requirement to satisfy, because it is an instruction about what the balance sheet holds, and it sits alongside published redemption procedures and frequent regulatory reports [2].
The recurring cost sits one layer down. A report that triggers at a threshold does not trigger below it, so screening automated micropayments has to happen at each transaction [2]. The Sept. 1 Braumiller Law Group overview summarized by PYMNTS says compliance systems built around customers initiating discrete transactions may need to monitor thousands of machine-generated payments executed in rapid succession, and that applying those controls below traditional reporting thresholds, with no human in the loop, is the central challenge [12].
The plumbing underneath is ordinary web traffic. Coinbase's x402 protocol uses the existing 402 Payment Required status code so a person or a machine client can pay inside a normal internet request, with no conventional account or session structure [13]. An agent can ask for an API or a piece of proprietary information, receive a payment demand, transfer stablecoins and get the material almost instantly [17]. Institutions then need records establishing each transaction and identity, anti-money-laundering and sanctions checks that run at machine speed, including when payer and recipient sit in different jurisdictions [15].
Two ways this goes. If agent-initiated volume stays small, full reserving is the binding cost, since it caps what balances earn and the monitoring work stays a design exercise. If the volume scales, the reserve rule fades into treasury routine and per-transaction screening becomes the expense that grows with usage. In my view the second is more likely, because reserving is a one-time change to what an issuer owns and screening is a bill that arrives with every payment.
The charter question is priced into that. The OCC's proposals cover federally qualified issuers, certain state and foreign issuers and custody activities, followed by separate proposals on Bank Secrecy Act, anti-money-laundering and sanctions compliance [7]; the FDIC has addressed reserves, redemption, capital, custody, safekeeping, risk management and tokenized deposits [8]; the NCUA has proposed application procedures and risk standards for credit union issuers [9]. An applicant choosing between a state charter and federal supervision is choosing which of three unfinished rulebooks to build its reporting stack against [10][3].
What would break this reading is a final rule that carves out machine payments below a de minimis size, which would take the per-transaction screening cost back out of the model. The overview describes what its clients have to build; it does not count applications, staff or dollars [4].
What to watch
- Whether the OCC's final rules treat machine-initiated payments below a de minimis size differently from customer-initiated ones.
- The first approvals that show whether applicants are landing on state charters or federal supervision.
- Any issuer disclosing what wallet-level monitoring costs per million transactions.