GENIUS Act rulebook: what regulated dollars mean for paying agents

The dollar an agent spends over x402 is about to become a licensed product. The GENIUS Act takes effect no later than January 18, 2027, five federal proposals are on the table, and none is final. This post reads the statute and the proposed rules as an operator would: which definitions catch a payment gateway, what the freeze obligation does to a stablecoin contract, and where the x402 stack is blind to it.

We have written about stablecoins as plumbing for months: EIP-3009 authorizations, SPL settlement on Solana, chains built for machine payments. Every one of those posts treated the token as a given. The Guiding and Establishing National Innovation for U.S. Stablecoins Act, Public Law 119-27, signed on July 18, 2025, changes that premise. From its effective date, the asset in the PAYMENT-SIGNATURE header is either issued by a permitted issuer or it is contraband for anyone in the business of offering it to a person in the United States.

Everything below is sourced from the enrolled statute, the agencies' own notices, and code we read ourselves. It is analysis, not legal advice.

Where the rulebook stands on September 11, 2026

Section 20 of the Act sets the effective date as the earlier of eighteen months after enactment or 120 days after the primary federal regulators issue final regulations. Eighteen months is January 18, 2027. The statute also told regulators to finish their rules within one year, by July 18, 2026. That deadline passed with everything still in proposed form. Because the 120-day trigger only runs from final rules, and none exist, the January date is the operative one unless finals land before late September, which nobody is promising.

Five proposals define the shape of the regime today.

OCC, February 25, 2026. The Office of the Comptroller of the Currency proposed a new 12 CFR Part 15 covering applications, permitted activities, reserves, redemption, custody, capital and wind-down for national banks, federal savings associations, nonbank federal qualified issuers and foreign issuers. Comments closed May 1. The proposal asked 211 numbered questions.

Treasury, April 3, 2026. Broad-based principles for deciding when a state regime is "substantially similar" to the federal one, which governs whether an issuer under $10 billion outstanding can stay state-supervised.

FinCEN and OFAC, April 8, 2026. A joint proposal that treats permitted issuers as financial institutions under the Bank Secrecy Act, with full AML programs and a sanctions compliance program.

FDIC, April 7, 2026. A prudential framework for FDIC-supervised issuers, redemption within two business days, and one clarification agents should note: deposits held as reserves "would not be insured to payment stablecoin holders on a pass-through basis."

Treasury, August 18, 2026. The most recent and, for anyone outside the issuer business, the most consequential: a proposed rule implementing Section 3, published at 91 Fed. Reg. 53368 with comments due October 19, 2026. It defines who is issuing, who is selling, and who is located in the United States.

On August 19 Comptroller Jonathan Gould told an audience in Wyoming: "So we are very intent on moving quickly and getting a final rule out by November so that we will be able to start processing applications within the new year." We could not locate a Federal Reserve proposal for state member bank subsidiaries as of this writing. The framework will therefore go live in January with at least one agency still writing.

Three definitions that decide whether the law touches you

The Act is drafted around three terms. Reading them precisely matters more than reading the press.

Payment stablecoin. Section 2(22): a digital asset "that is, or is designed to be, used as a means of payment or settlement," whose issuer "is obligated to convert, redeem, or repurchase for a fixed amount of monetary value" and represents that it will maintain a stable value. USDC and USDT are squarely inside. Deposits and national currency are carved out.

Digital asset service provider. Section 2(7) means a person that, "for compensation or profit, engages in the business in the United States" of exchanging digital assets for monetary value or other digital assets, "transferring digital assets to a third party," "acting as a digital asset custodian," or "participating in financial services relating to digital asset issuance." The exclusions are the interesting part. A DASP does not include "a distributed ledger protocol," the business of "developing distributed ledger protocols or self-custodial software interfaces," "an immutable and self-custodial software interface," validators, or "participating in a liquidity pool."

Lawful order. Section 2(16): any final and valid writ, order, rule or decree under federal law from a court or authorized agency that "requires a person to seize, freeze, burn, or prevent the transfer of payment stablecoins issued by the person," specifies the coins or accounts "with reasonable particularity," and is subject to review.

Put those together and the architecture question for an agent platform is not rhetorical. A gateway that holds agent balances in a per-agent deposit address and debits them per call is plausibly "acting as a digital asset custodian" and "transferring digital assets to a third party." A gateway that only returns 402 challenges and lets a facilitator submit the agent's own signed authorization to the token contract looks much more like a self-custodial interface. Same product, different statutory box.

The three prohibitions and their dates

Section 3 stacks three bans with different clocks.

Section 3(a), effective with the Act: "It shall be unlawful for any person other than a permitted payment stablecoin issuer to issue a payment stablecoin in the United States."

Section 3(b)(1), effective three years after enactment, July 18, 2028: unlawful for a DASP "to offer or sell a payment stablecoin to a person in the United States, unless the payment stablecoin is issued by a permitted payment stablecoin issuer."

Section 3(b)(2), effective with the Act and easy to miss: unlawful for any DASP "to offer, sell, or otherwise make available in the United States a payment stablecoin issued by a foreign payment stablecoin issuer unless the foreign payment stablecoin issuer has the technological capability to comply, and will comply, with the terms of any lawful order and any reciprocal arrangement pursuant to section 18."

The 2028 date gets the headlines. The January 2027 date is the one that bites first, because the foreign-issuer clause does not wait three years. From the effective date, a DASP making a foreign-issued coin "available" in the United States needs the issuer to be capable of, and committed to, freezing on order. Section 3(e) states the intent to reach extraterritorially whenever conduct "involves the offer or sale of a payment stablecoin to a person located in the United States," and Section 3(f) attaches a fine of up to $1,000,000 per violation and up to five years imprisonment for knowing participation in unlawful issuance.

Section 3(g) adds a quieter penalty. A stablecoin not issued by a permitted issuer "shall not be treated as cash or as a cash equivalent for accounting purposes," is not eligible as margin for broker-dealers and clearing organizations, and is not "acceptable as a settlement asset to facilitate wholesale payments between banking organizations." For a treasury that books agent spend, the asset class of the balance on the books is decided by the issuer's license.

What Treasury's Section 3 proposal actually defines

The statute left "issue" undefined. The August proposal fills it: issuance is "the first transfer of a payment stablecoin by the issuer" that "results or will result in a person other than the issuer having the right to use or transfer" it. A person issues in the United States if the person is located here or issues to a person located here. For entities, "located in the United States" means organized under U.S. or state law or having a principal place of business here; for individuals it is physical presence unless "merely temporary."

A foreign issuer gets a four-part safe harbor: not located in the United States, a reasonable belief that no recipient is, policies and controls "reasonably designed to avoid issuing" to U.S. persons, and no advertising that targets or "could be reasonably expected to have the effect of targeting" them. Treasury also says plainly that issuers and DASPs "are not mutually exclusive categories." One entity can be both, and both restrictions apply.

Two things the proposal does not do are worth the same attention. It does not, in the material we could read, draw the line for custodial wallet providers or payment intermediaries with any more precision than the statute. And it does not address how coins issued before the effective date are treated once it passes. Both are open in the comment docket until October 19.

The freeze becomes a licensing condition

This is the section that changes how a payment path should be engineered.

Section 4(a)(6)(B) is one sentence: "A permitted payment stablecoin issuer may issue payment stablecoins only if the issuer has the technological capability to comply, and will comply, with the terms of any lawful order." Section 4(a)(6)(A) tells Treasury to coordinate with issuers before blocking a foreign person's property "to ensure that the permitted payment stablecoin issuer is able to effectively block a payment stablecoin of the foreign person," while noting the Secretary "is not required to notify any permitted payment stablecoin issuer" in advance.

Until now, an issuer's freeze function was a policy choice disclosed in risk factors. Circle's USDC risk factors say the company "reserves the right to block the transfer of USDC to and from an address on chain in extraordinary circumstances exclusively per the terms of the blacklisting policy," and that it "may also be forced to freeze USDC and/or surrender associated U.S. Dollars" on "a legal order from a valid government authority." After January, the same capability is a precondition of the license. An issuer that removed it would be issuing unlawfully.

The capability is already in production. We read the contracts in Circle's stablecoin-evm repository. The role lives in Blacklistable.sol:

modifier notBlacklisted(address _account) {
    require(
        !_isBlacklisted(_account),
        "Blacklistable: account is blacklisted"
    );
    _;
}

function blacklist(address _account) external onlyBlacklister {
    _blacklist(_account);
    emit Blacklisted(_account);
}

Version 2.2 of the token folded the flag into the balance slot. FiatTokenV2_2 stores each account's balance in the low 255 bits of a single word and uses bit 255 as the blacklist marker:

function _isBlacklisted(address _account) internal view returns (bool) {
    return balanceAndBlacklistStates[_account] >> 255 == 1;
}

function _setBlacklistState(address _account, bool _shouldBlacklist) internal {
    balanceAndBlacklistStates[_account] = _shouldBlacklist
        ? balanceAndBlacklistStates[_account] | (1 << 255)
        : _balanceOf(_account);
}

And the function every x402 exact settlement on EVM calls carries the modifier on both ends:

function transferWithAuthorization(
    address from, address to, uint256 value,
    uint256 validAfter, uint256 validBefore,
    bytes32 nonce, bytes memory signature
) external whenNotPaused notBlacklisted(from) notBlacklisted(to) { ... }

The consequence is mechanical. If either the agent's address or the seller's payout address is blacklisted, the authorization the agent signed is valid, the nonce is fresh, the balance is sufficient, and the transfer still reverts with a fixed string. On Solana the mechanism is the mint's freeze authority acting on token accounts rather than a bit in a balance; Circle has used it, including on roughly $58 million in Solana USDC accounts in May 2025.

Scale matters for risk modelling. An AMLBot analysis of on-chain data snapshotted on October 7, 2025 counted 7,268 blacklisted USDT addresses holding $3.29 billion against 372 USDC addresses holding $109 million, a roughly thirtyfold gap in both count and value. Those are issuer decisions under two very different policies. The Act does not narrow either one. It requires the capability and defines the orders an issuer must obey; it says nothing about the orders an issuer may choose to obey.

Where x402 is blind to it

We checked how the reference facilitator behaves when the freeze lands. Clone of x402-foundation/x402 at HEAD 3c2ddfb, September 9, 2026.

Verification of an EIP-3009 payment runs the transfer through eth_call. When the simulation fails, diagnoseEip3009SimulationFailure issues one multicall with four probes: balanceOf, name, version and authorizationState. Those map to specific reason codes for an unsupported token, a spent nonce, a domain mismatch, or an insufficient balance. There is no isBlacklisted probe. A frozen payer or payee falls through to the generic ErrEip3009SimulationFailed, with the raw revert string attached as invalidMessage, because the code makes a point of carrying it:

// Carry the raw revert text so the concrete reason survives the mapping to a code.
const rawMessage =
  simError instanceof Error ? simError.message : simError ? String(simError) : undefined;
return {
  response: rawMessage ? { ...diagnosis, invalidMessage: rawMessage } : diagnosis,
  classification,
};

So the information exists, as a substring of a message, for a client that greps for "Blacklistable". No agent SDK we know of does. The agent sees a payment that fails verification for no reason it can categorise, retries with a new nonce, and fails again.

The second gap is timing. As we found in the ERC-6492 audit, simulateInSettle defaults to false; the single authoritative pre-check is in verify. A blacklist transaction that lands between verify and settle produces a reverted settlement whose gas the facilitator pays. The two-phase gap we mapped for free-riding now has a regulatory trigger as well as an adversarial one.

The third gap is on the seller side. A 402 response advertises a payTo address. If that address is frozen, every buyer's payment fails at notBlacklisted(to). Nothing in the protocol lets a seller learn this from its own traffic except a sudden run of verification failures. None of the mechanisms in the repository, EVM, SVM or the TON-based TVM package, probes issuer-level freeze state; the TVM package checks a frozen account status, but that is the chain's account lifecycle, not an issuer blacklist.

No yield, ever

Section 4(a)(11): no permitted or foreign issuer "shall pay the holder of any payment stablecoin any form of interest or yield (whether in cash, tokens, or other consideration) solely in connection with the holding, use, or retention of such payment stablecoin."

For an agent operator this settles a design question we raised in funding agents with stablecoins. A prefunded balance is dead capital by law, not just by product choice. The reserve behind it, per Section 4(a)(1), is Treasury bills of 93 days or less, overnight repo, Fed balances and insured deposits, and the issuer keeps that income. Every dollar sitting in a deposit address waiting for the next inference call is a dollar earning nothing that could have stayed in a money market fund until the moment of the call. Pay-per-request over x402, where the authorization is signed at call time from a wallet that is otherwise invested elsewhere, is the treasury-efficient shape as well as the protocol-native one.

Who is actually going to be permitted

The OCC proposal shows the operating envelope a permitted issuer will live in: daily liquidity of at least 10% of reserves and weekly liquidity of at least 30%, a weighted average maturity of no more than 20 days, no more than 40% of reserves at any one institution, redemption "within two business days," extendable to seven calendar days if redemptions exceed 10% of outstanding issuance in 24 hours, a $5 million capital floor for de novo issuers and an operational backstop of twelve months of expenses. Applications are deemed approved 120 days after receipt unless denied. State issuers crossing $10 billion outstanding get 360 days to transition to federal supervision.

The candidates are lining up. On December 12, 2025 the OCC conditionally approved five national trust bank charters: First National Digital Currency Bank and Ripple National Trust Bank as de novo banks, and conversions for BitGo Bank & Trust, Fidelity Digital Assets and Paxos Trust Company. On July 10, 2026 Circle received final approval for First National Digital Currency Bank, N.A., operating as Circle National Trust. It opens with fiduciary custody for Circle and its affiliates; management of the USDC reserve is described as a future capability, not a launch one.

Tether took the other route. On January 27, 2026 it launched USAT, a separate token issued by Anchorage Digital Bank, N.A., with Cantor Fitzgerald as reserve custodian and primary dealer and Bo Hines as CEO of Tether USAT. Anchorage's first attestation, reported on March 2, showed $17,604,716 in reserves against 17,501,391 tokens as of January 31. The launch text says USDT "continues to operate globally" and is "progressing towards GENIUS Act compliance." That is a statement of intent, not a status.

USDT's path into the U.S. market runs through Section 18: a Treasury determination that the issuer's home regulator is "comparable," registration with the Comptroller, reserves "in a United States financial institution sufficient to meet liquidity demands of United States customers," and a home jurisdiction not under comprehensive sanctions. Treasury must decide a request within 210 days of a substantially complete filing. No such determination has been published for any jurisdiction that we could find.

What it means for LLM4Agents

Our billing accepts USDT and USDC on Solana and Polygon into a per-agent deposit address, and our roadmap is x402 per-call settlement over an OpenAI-compatible gateway. The Act touches both halves differently.

The deposit model is the exposed one. Holding agent balances and debiting them per request maps onto "acting as a digital asset custodian" in the DASP definition. If that reading holds, the July 18, 2028 ban on offering non-permitted stablecoins applies to us, and the January 18, 2027 foreign-issuer clause applies sooner for any coin whose issuer is not a permitted one. USDC has a clear route to permitted status. USDT does not yet. Our asset list is a compliance decision with a date on it.

The x402 model is the sheltered one. When the agent signs an EIP-3009 authorization from its own wallet and a facilitator submits it, we never hold the asset; we return a challenge and verify a receipt. That is far closer to the "self-custodial software interface" the statute carves out. The regulatory gradient and the protocol gradient point the same way: move value from balances we hold to authorizations agents sign. The reserve, proxy, settle pipeline becomes a compliance boundary as well as a billing one.

The freeze obligation is a new failure mode in our reliability model. Today a blacklisted agent address produces a generic verification failure, an unclassified error at our gateway, and a retry storm. A blacklisted payout address produces the same for every customer at once. We treat model outages with fallback chains; we have no equivalent for a payment rail that has been switched off for one address by court order.

The interest ban is an argument for our architecture. A platform that requires prefunding asks the customer to hold a zero-yield asset; a platform that settles per call from a wallet the customer controls does not. That is a pricing point against subscription and credit-balance competitors, and it is written into federal law.

Staying on the frontier

Concrete steps, in order:

1. Classify the platform under Section 2(7) before January 18, 2027. Document, with counsel, which of our flows are custody and transfer and which are self-custodial interface. Design the x402 path so the answer for it is unambiguous: no pooled balances, agent-signed authorizations only, receipts not ledgers.
2. Add freeze-state probes to verification and propose them upstream. Extend the diagnostic multicall in the EVM facilitator with isBlacklisted(from) and isBlacklisted(to), and check token-account freeze state on Solana, so a frozen address returns a specific reason code instead of a substring in invalidMessage. Open the pull request against x402-foundation/x402 so every client benefits.
3. Watch our own addresses. Subscribe to Blacklisted events on every USDC contract we settle on and to freeze instructions on our Solana token accounts. A frozen payout address should rotate automatically and the 402 challenge should advertise the new one within a block.
4. Publish an asset policy with dates. USDC and USAT as permitted-issuer assets; USDT flagged as contingent on a Section 18 determination or a Tether license; revisit the moment the OCC's final rule appears, which the Comptroller has targeted for November.
5. Default to just-in-time funding. Make per-call x402 the primary billing path and the deposit balance a legacy option, so customers are never asked to park capital in an asset that cannot pay them.
6. File a comment by October 19. Treasury's Section 3 docket is the place to ask for an explicit safe harbor for non-custodial payment interfaces that pass agent-signed authorizations to a facilitator. Silence now is an interpretation risk later.