A stablecoin strategy needs more than a token and a launch date. It needs an answer to the awkward questions about reserves, capital, permissions, and who is accountable when something goes wrong.
On September 24, the Federal Reserve requested public comment on two proposals establishing a regulatory framework for Board-supervised payment stablecoin issuers under the GENIUS Act. The proposals address operating standards and an application process; they are not final rules or an approval for any particular bank to start issuing stablecoins.
For U.S. financial institution executives, the opportunity is to assess the operating model before enthusiasm hardens into an implementation plan. “We can build it” and “we can run it responsibly” are different statements.
Two proposals, distinct jobs
The first proposal would require covered issuers to fully back their payment stablecoins with permissible reserve assets, including short-term Treasury bills and certain other high-quality liquid assets. It would also establish standardized capital requirements for certain credit and operational risks, risk-management standards, rules for safekeeping reserve assets, and clarification of permissible bank activities.
The second proposal would establish an application process for Board-supervised insured depository institutions seeking approval for a subsidiary to issue payment stablecoins, with business plans, financial information, and procedures for appeals and determinations.
The scope is important. These are the Fed's proposals within its supervisory responsibilities, not a single announcement that settles every stablecoin obligation for every US institution.
Policy is the moat
The strategic implication is straightforward: evaluate a stablecoin project as an operating business, not just an integration. Model the cost of reserve operations, control ownership, monitoring, reconciliations, and change management alongside the intended payment benefits.
Ask who owns the reserve record, who authorizes issuance-related actions, and how operational risk is reported to management. Require precise answers about the systems and people behind each control.
That exercise is useful even if the institution ultimately chooses partnership rather than issuance. Buying access to technology should not mean buying uncertainty about responsibility.
The Fed's announcement explicitly includes reserves, capital, and risk management within the proposed framework. The executive response should be a joined-up review by treasury, risk, finance, legal, and technology, not a project passed between departments until someone volunteers to own it.
Compare participation models before choosing a platform
Start by defining the role the institution actually wants. Is the strategic interest issuance, reserve safekeeping, a payment partnership, or simply understanding a changing market?
Those choices should lead to different diligence questions. An issuance case should explain the full operating model; a partner case should explain responsibilities, dependencies, and exit arrangements.
Do not let the technology selection quietly make the business decision. A platform can be technically impressive and still be the wrong answer to the institution's objective.
For CIOs and CTOs, build on existing infrastructure where it can meet the required controls. Test whether existing identity, access, recordkeeping and reconciliation systems can support the intended activity before adding another disconnected operational layer.
Test the policy before changing production
Use a controlled representation of the proposed workflow to examine failure paths. For example, test a mismatch in reserve records, an unavailable service, a rejected instruction, and a recovery that must not create a duplicate transaction.
This is a digital-twinning exercise, not an argument for pooling customer data. Synthetic cases and appropriately protected operational data can help teams examine sequencing and accountability without treating production as the test environment.
Keep a decision log that separates current obligations, proposed changes, and the institution's own risk choices. That distinction helps prevent a draft proposal from becoming an accidental production rule.
Use the comment window for real operating questions
The comment period closes 60 days after publication in the Federal Register, according to the Fed. Do not calculate a submission deadline from the September 24 press release alone.
Assign an owner to review the proposals and supporting notices, identify implementation questions, and coordinate feedback through legal and compliance. Avoid building a cost case around a provision that has not yet been finalized.
The useful outcome is not a louder stablecoin strategy. It is a strategy that can explain its controls as clearly as its ambition.
FAQs
Are these final stablecoin rules?
No. The September 24 announcement requests public comment on two proposals, rather than announcing finalized requirements (Federal Reserve announcement).
Do these proposals cover every US stablecoin issuer?
The release concerns Board-supervised payment stablecoin issuers and related activities within the Fed's supervisory remit. Institutions should assess the relevant regulator and legal structure rather than assume this announcement applies uniformly across the market (Federal Reserve announcement).
What would the reserve and capital proposal require?
The Fed proposes full backing with permissible reserve assets, standardized capital requirements addressing certain credit and operational risks, and risk-management standards. The detailed proposal should be reviewed before drawing conclusions about a particular business model (Federal Reserve announcement).
When does the comment period end?
It ends 60 days after publication in the Federal Register. The press release does not give a calendar deadline; confirm the applicable publication record before scheduling a submission (Federal Reserve announcement).