GENIUS Act reserve requirements: what issuers hold and what a counterparty should verify

The GENIUS Act reserve requirements are the part of the law a payment institution touches first. A regulated payment stablecoin is a claim on its issuer. Its usefulness in settlement depends on whether that claim is backed, and on whether the backing can be checked by someone outside the issuer. The GENIUS Act, signed into United States law in July 2025, sets out what a permitted payment stablecoin issuer must hold, how often it must report, and who examines the report. This article explains the rule, the limits of a monthly attestation, and the diligence a bank, credit union or licensed money service business should run before it accepts a stablecoin for settlement.

What are the GENIUS Act reserve requirements?

The core rule is simple to state. A permitted payment stablecoin issuer must back its outstanding stablecoins with reserves on at least a one to one basis. One token outstanding, one dollar of permitted reserve asset behind it. There is no fractional model, and no allowance for a maturity mismatch buffer.

The word permitted carries the weight. Reserves are not whatever safe asset the issuer prefers. The GENIUS Act lists the categories that qualify. Anything outside that list does not count toward the ratio, however sound it may look.

Two further rules sit alongside the ratio. An issuer may not pay interest or yield to holders of the stablecoin. And in an issuer failure, holder claims on the reserves rank ahead of other creditors. Together these push the instrument away from a deposit substitute that pays a return, and toward a plain claim on a segregated pool.

Which assets count as permitted reserves?

The permitted list is deliberately short, and deliberately short dated. Cash and central bank reserve deposits qualify. So do demand deposits at insured depository institutions. Treasury bills qualify where the remaining maturity is 93 days or less under the GENIUS Act. Repurchase agreements backed by Treasuries qualify at short tenors, as do government money market funds that invest in the same instruments. Tokenised versions of those assets are contemplated as well.

Notice what is absent. Corporate bonds, commercial paper, equities, loans and other digital assets do not qualify. Neither does an uninsured balance parked with a bank outside the regime. The list is built to survive a redemption run, not to earn a return.

Composition matters as much as the headline ratio. Two issuers can both report full backing while holding very different liquidity. A book of Treasury bills maturing inside three months behaves differently under stress from a large deposit balance at a single bank. Read the composition table, not only the total.

What can an issuer not do with the reserves?

Reuse is restricted. Under the GENIUS Act an issuer may not lend out, pledge or otherwise rehypothecate reserve assets, subject to narrow exceptions such as raising short term liquidity to meet redemptions or posting the assets in a repurchase agreement.

That restriction is the difference between a reserve and a balance sheet. A bank funds lending with deposits by design, and supervision is built around that fact. A payment stablecoin issuer funds nothing with reserves. The pool exists to be returned.

Redemption policy is the other side of the same rule. An issuer must publish a clear redemption policy and honour it. For a counterparty this is the operational question that matters most. Settlement speed means little if converting the token back to fiat takes days, or if the route runs through a single venue with its own limits.

How does monthly attestation work, and what does it prove?

The GENIUS Act requires a permitted issuer to publish the composition of its reserves every month. That monthly report must be examined by a registered public accounting firm. The chief executive and the chief financial officer must certify its accuracy, and a false certification carries criminal exposure. Larger issuers carry more: the GENIUS Act requires an issuer with more than 50 billion dollars of outstanding stablecoins to produce annual audited financial statements.

Now the limits, because they are where counterparty risk actually lives. A monthly examination is a point in time exercise. It reports what the reserve pool held on the reporting date. It says nothing about the other days of the month. It is not a full audit of the issuer, and it does not test the operational controls, the custody arrangements or the parent company behind the issuer.

There is a second gap, on the liability side. Backing is a ratio between reserves and tokens outstanding. Tokens outstanding is a blockchain figure. A stablecoin issued on several chains is the sum of its supply across all of them, including bridged representations. A report that reconciles reserves to a complete, chain by chain supply figure is worth considerably more than one that reports a single number.

A reserve report tells you what was true on the reporting date. Your own controls have to tell you what is true on the day you settle.

What should a counterparty verify before accepting a stablecoin?

Diligence here is a repeatable file, not a one off judgement. The work resembles counterparty review of any other short term instrument, and it belongs in the same cycle. Run these steps in order and keep the output.

• Confirm issuer status first. Establish whether the issuer is a permitted payment stablecoin issuer, and which authority approved it: a federal banking agency, the OCC as a federal qualified nonbank issuer, or a qualifying state regime.
• Read the latest monthly reserve report in full, including the composition table, and record the examining accounting firm by name.
• Check the reporting date against your settlement date, and decide in advance how stale a report you will accept before you reduce limits.
• Reconcile tokens outstanding against on chain supply across every chain the token is issued on, not only the chain you settle on.
• Test the redemption path yourself. Redeem a small amount, record the elapsed time and the fee, and keep the evidence in the file.
• Set exposure limits per issuer and per chain, including an intraday balance cap, and review them on the same schedule as other counterparty limits.
• Write the conclusion into your risk assessment, with the date you reviewed each attestation and the name of the person who approved the exposure.

None of this is exotic. It is the same discipline a treasury team applies to a money market fund or a correspondent bank line, applied to a new instrument and recorded so an examiner can follow it.

When do the GENIUS Act reserve requirements actually bite?

The law was signed in July 2025, but the obligations phase in. The GENIUS Act makes its main requirements effective on the earlier of 18 months after enactment or 120 days after the primary federal regulators issue final implementing rules. Rulemaking is therefore the date to watch, not the signing.

A separate date governs distribution. Three years after enactment, a digital asset service provider may not offer or sell a payment stablecoin in the United States unless it was issued by a permitted issuer. An institution that intends to hold or move stablecoins should be on the permitted side of that line well before the deadline, because switching an issuer mid programme means repapering, re testing and reopening the risk assessment.

Scale decides the supervisor. Under the GENIUS Act a state qualified issuer whose outstanding issuance passes 10 billion dollars must move to the federal regime or obtain a waiver. For a counterparty that threshold is a useful early warning. An issuer approaching it is facing a supervisory transition, and transitions are when reporting practice and redemption service tend to change.

Detail will still move as final rules land. Treat any summary of the GENIUS Act reserve requirements, including this one, as a floor to verify against the statute and the regulators own text rather than as a settled operating manual.

Where StableNet fits

StableNet, built by SpendTheBits, is a cross border B2B payment and settlement platform for banks, credit unions, licensed money service businesses, exchange houses and remittance fintechs. Settlement is in regulated stablecoins such as USDC and USDT on public blockchains, completing in minutes with on chain auditability, so the supply side of the ratio is observable rather than asserted. The platform is ISO 20022 native, with pacs.008 customer credit transfers, pacs.009 interbank legs, pacs.002 status reports and pacs.004 returns inside head.001 envelopes, tracked end to end by UETR, which lets a settled payment be tied back to the issuer, the chain and the date it was accepted. Compliance is built in, with KYB and KYC onboarding, KYT, sanctions and PEP screening, FATF Travel Rule data in IVMS101 form, a compliance workbench and a tamper evident audit trail, so issuer diligence sits in the same record as the payment it justified. SpendTheBits is a Bank of Canada registered payment service provider and a named finalist in the Swift Hackathon 2026 Technical Challenge.