OCC Finalizes GENIUS Act Stablecoin Rules14 min read2,788 words

OCC Finalizes GENIUS Act Stablecoin Rules

The OCC finalized GENIUS Act stablecoin rules on reserves, redemptions and risk. See who is covered, what remains open and how issuers can prepare before 2027.

GENIUS Act stablecoin rulesOCC stablecoin regulationpayment stablecoin issuersstablecoin reserve requirementsstablecoin redemption rules
OCC Finalizes GENIUS Act Stablecoin Rules

The OCC's GENIUS Act Rules Are Final. The Application Window Is Not

The Office of the Comptroller of the Currency (OCC) has finalized its rules for payment stablecoin issuers under its supervision. That gives banks, crypto companies, and other potential issuers a clearer picture of the standards they'll have to meet when the GENIUS Act kicks in on January 18, 2027. What it still does not answer is the question companies are probably asking first: when can they actually apply?

The rule lays out requirements for reserves, redemption, risk management, audits and reporting, custody, capital, and operational safeguards. It also explains how certain state-qualified and foreign issuers fit into the federal framework. Anti-money laundering and sanctions requirements are being handled separately by the Treasury Department, so the OCC's final rule is a major piece of the overall system - but not the whole checklist.

That distinction matters. A finalized rule helps companies plan, but it isn't the same thing as getting permission to issue a stablecoin. Below is what the OCC decided, who the rules cover, and what prospective issuers still need to clarify before the law takes effect.

What the OCC finalized

The OCC issued its final rule on October 21, 2026, to implement the GENIUS Act for payment stablecoin issuers within the agency's jurisdiction. The law is set to take effect on January 18, 2027. In other words, the rule takes broad statutory requirements and turns them into an OCC supervisory framework for the issuers and activities the OCC oversees.

The new regulatory section covers several connected areas: reserve assets, redemption, risk management, audits and reporting, custody, applications, foreign issuers, and capital and operational safeguards. It also addresses how some state-qualified issuers transition into the federal framework and the circumstances under which the OCC can revoke an issuer's approval.

The key point isn't just that the rule lists compliance topics. It places stablecoin issuance inside an ongoing supervisory relationship. That means obligations tied to how an issuer backs its tokens, handles redemption requests, manages operational and financial risks, and reports to regulators. Those pieces have to work together. A reserve policy that looks fine on paper doesn't help if the issuer can't track assets properly or process redemptions reliably.

Reserves and redemption are linked

Reserves and redemption are separate requirements, but they're operationally connected. Reserves cover the assets supporting outstanding payment stablecoins. Redemption covers the process for holders to exchange those tokens under the issuer's stated arrangements and the applicable rules.

For an issuer, that means it needs more than an asset inventory. It needs reliable records, controls over reserve assets, clear responsibilities, and processes that can actually support redemption when customers ask for it. The OCC's announcement confirms that both reserve and redemption standards are included, but it doesn't provide all the technical details a company would need to design a compliant program. Issuers should read the final rule text and any later OCC guidance before treating a specific reserve structure or redemption process as compliant.

This is where headlines can mislead. "Reserve requirements" doesn't tell you which assets qualify, how every operational scenario is handled, or what evidence an examiner will expect. Those specifics are in the full regulatory text and in how the OCC implements and supervises the rule.

The rule extends beyond the reserve account

The OCC also included requirements for risk management, audits, reporting, custody, and a capital and operational backstop. These requirements are about the systems around the token, not only the assets backing it. A stablecoin issuer has to manage operational dependencies and maintain controls so it can identify problems, report accurately, and keep operating when conditions get stressful.

If a firm already runs payment, custody, or other financial services, some of these capabilities may already exist in different parts of the business. That doesn't automatically mean it meets the requirements for a regulated stablecoin operation. The practical job is to map existing controls to the issuer's legal obligations, identify gaps, and define who is accountable for each requirement.

The OCC also said it received hundreds of comments on its proposal from crypto companies, community banks, trade groups, academics, and others. It noted the industry is still developing and said it will monitor changes and adjust its framework where needed. In plain terms, it signals ongoing supervisory attention - not a guarantee that every implementation question is already settled.

Who the rules cover - and what they leave out

The OCC framework applies to payment stablecoin issuers within its jurisdiction. In the agency's bulletin, that includes subsidiaries of national banks and federal savings associations, nonbank issuers approved at the federal level, and some state-qualified issuers. The rule also covers foreign issuers and certain custody activities at OCC-supervised firms.

So yes, this is broader than a single kind of bank. It matters to established institutions considering a stablecoin product, crypto firms seeking federal approval, and some issuers working from state arrangements. But it doesn't mean every token marketed as a stablecoin will follow the same OCC pathway. The law and rule focus on payment stablecoins and on which entities are allowed to issue them or make them available in the United States.

The GENIUS Act, signed into law in July 2025, bars anyone other than a permitted issuer from issuing a payment stablecoin in the United States. It also restricts digital asset service providers from offering or selling stablecoins to Americans unless those stablecoins come from a permitted issuer (or a foreign issuer meeting specified requirements). The exact legal treatment depends on the activity and the issuer category involved, so a company shouldn't assume its status based on a marketing label or token design alone.

State and foreign issuer pathways need close attention

The final rule addresses how certain state-qualified issuers transition into the federal framework, along with the supervision of foreign issuers. That matters because the stablecoin market isn't built around one institution type or one jurisdiction. Your path to market may depend on where you're organized, the approvals you already have, and how your activities are structured.

For state-qualified issuers, transition rules can determine what needs to change and when. For foreign issuers, the framework raises questions about how overseas operations and U.S. distribution interact with federal requirements. The OCC says the final rule covers these issues, but prospective issuers should review the actual provisions for the conditions that apply - rather than assuming an existing state or foreign authorization carries over unchanged.

It also means your legal analysis should include distribution partners. The Act's limits aren't only about the entity that issues the token. They also affect certain digital asset service providers offering or selling tokens to U.S. customers. If your business model involves an exchange, wallet provider, payment processor, or another intermediary, you'll need to map out responsibilities across those participants.

AML and sanctions are a separate workstream

The OCC's final rule does not include requirements under the Bank Secrecy Act, anti-money laundering rules, or sanctions programs. Those are covered through separate rulemaking with the Treasury Department. The source material says Treasury's FinCEN and OFAC proposed requirements separately in April, including anti-money laundering programs, suspicious activity reporting, and sanctions compliance programs.

"Separate" doesn't mean optional. It means you shouldn't treat the OCC rule as the full compliance checklist. An issuer may have to coordinate prudential and operational controls with financial crime controls, while tracking the relevant rulemaking and the final requirements from the appropriate agencies.

In practice, splitting these workstreams across teams without a clear owner can create gaps. Customer onboarding, transaction monitoring, sanctions screening, and redemption operations may depend on the same underlying data and escalation paths. The agencies' rules may be separate, but the systems used to comply have to fit together.

Why the application timeline matters

The OCC says it will announce separately when it starts accepting applications and waiver requests from prospective issuers. That leaves a real gap between the final rule and when the approval process can actually begin.

This isn't a minor detail. A company can use the final rule to estimate its obligations, build controls, and prepare documentation. But it can't assume it can submit an application already - or that the OCC will process it on any particular schedule. The OCC hasn't announced the start date in the materials accompanying the final rule.

The timing is notable because regulators missed the earlier July deadline for finalizing their rules. In August, Comptroller of the Currency Jonathan Gould said the OCC planned to move quickly and aimed to issue a final rule by November so it could begin processing applications within the new year. The rule was finalized on October 21, which was before that stated November target. Still, the application start date remains a separate announcement.

For companies, that creates two planning questions:

  • Can the business meet the substantive standards? That means understanding the reserve, redemption, risk, custody, reporting, and other requirements that apply to its category.
  • When can the business enter the formal process? That depends on the OCC's announcement and the application procedures it publishes.

Mixing these up can lead to bad planning. Hiring and engineering might be reasonable before applications open, but presenting the approval timeline as a certainty isn't. Build a plan with dependencies and contingencies rather than tying a product launch to an approval date that hasn't been announced.

The market impact is about access and execution

A federal framework can reduce uncertainty for institutions evaluating stablecoin issuance. Clearer requirements help legal, compliance, and product teams understand what a regulated offering might involve. It may also make it easier for banks and nonbank firms to compare the cost of entry with the commercial opportunity.

But regulation doesn't automatically produce adoption. A permitted issuer still needs a product that solves a real payment or settlement problem, reliable technology, workable distribution, and a sustainable business model. Compliance is a cost of operating in the market, not proof of product-market fit.

The distinction matters for investors and customers, too. A final rule is a regulatory milestone, not evidence that a particular issuer is approved, a particular token is available, or that all implementation questions are resolved. Those pieces will need to be assessed separately as applications are submitted, approvals are granted, and operational disclosures come out.

How issuers should prepare

Prospective issuers don't have to wait for the application window to start doing the basic readiness work. They do need to separate preparation from approval. A practical approach is to translate the rule into a control map, assign owners, and track open questions until the OCC publishes application procedures or additional guidance.

Start with the entity and activity. Identify which legal entity would issue the token, where it would operate, how it would reach U.S. users, and whether it's likely to fall under OCC supervision. If the business depends on state qualification, a foreign issuer, or third-party service providers, document how those relationships affect the pathway. Don't assume one group company's license or controls automatically cover another entity's activities.

Then map the operational requirements. At a minimum, the work plan should cover:

  • Reserves: how reserve assets are identified, recorded, controlled, and reconciled against outstanding payment stablecoins.
  • Redemption: how requests are received, validated, processed, and communicated, including ownership of exceptions and escalations.
  • Risk management: how financial, operational, and technology risks are identified, monitored, and addressed.
  • Audit and reporting: what information must be maintained, how it is reviewed, and who is responsible for accurate reporting.
  • Custody: which parties control relevant assets or keys, and what oversight and separation of responsibilities apply.
  • Capital and continuity: how the issuer will meet the rule's capital and operational backstop requirements.
  • Financial crime controls: how the business will handle applicable AML, suspicious activity reporting, and sanctions obligations as those rules are finalized.

This isn't a substitute for legal advice or a complete interpretation of the rule. It's a way to surface dependencies early. For each area, write down the rule references, the control owner, the evidence the company expects to retain, and any open interpretation or implementation questions.

Build for examination, not just launch

One common mistake in regulated product work is treating compliance like a launch checklist. That can produce a tidy first impression and a fragile operating model. A stablecoin issuer needs controls that keep working as supply changes, transaction volumes shift, vendors change, and staff rotate.

For example, reserve reconciliation done manually for a small pilot might be manageable once. If the same process has to run repeatedly - complete with review evidence and reliable escalation - manual steps can start becoming a source of delay and errors. Automation can help, but only if the underlying data, ownership, and exception handling are solid. Automating a messy process usually just speeds up how fast it breaks.

The same is true for redemption. A policy document isn't enough if customer support, treasury operations, and technical systems each assume someone else owns the failure. Run operational scenarios before launch. What happens when a redemption request can't be matched? When a service provider is unavailable? When records don't agree? When something needs escalation? The goal isn't to predict every event. It's to make responsibilities and recovery paths explicit.

Keep a regulatory change log

The OCC has said it may adjust its framework as the industry develops. At the same time, Treasury's AML and sanctions rulemaking remains a separate workstream. Issuers should keep a change log that distinguishes confirmed requirements from proposals, agency statements, and unresolved questions.

That helps you avoid two opposite mistakes: treating a proposal like it's already final, or assuming a likely requirement can wait until later. Assign someone to monitor official updates, translate their implications into your control map, and decide whether a change affects product design, launch timing, or operating cost.

And yes, proportionality matters here. A large institution and a smaller prospective issuer may have different resources, but neither benefits from a compliance design that only exists on paper. Start with the risks and obligations that apply, then choose controls you can actually operate and evidence consistently. The best framework isn't necessarily the most elaborate - it's the one the business can sustain.

Conclusion

The OCC has finalized a major part of the GENIUS Act framework, laying out standards for reserves, redemption, risk, and the systems around payment stablecoin issuance. That gives prospective issuers a stronger basis for planning - but two pieces remain separate: the OCC hasn't announced when applications will open, and Treasury's AML and sanctions requirements are being developed on a different timeline.

For companies, the sensible next step isn't to sit back and assume approval is around the corner. Map the applicable issuer pathway, translate the final rule into operational controls, and keep tracking the remaining rulemaking and application guidance. For investors and customers, treat the final rule as a regulatory milestone - not as proof that a specific stablecoin or issuer is already approved.

Read the OCC's announcement and rule information, then review the official rule text before making decisions about a specific business or product.

Frequently Asked Questions

The GENIUS Act is scheduled to take effect on January 18, 2027. The OCC’s final rule sets requirements for payment stablecoin issuers under its jurisdiction ahead of that date.
The OCC has not announced when it will begin accepting applications or waiver requests. It said it would provide that information separately, so prospective issuers should not assume that the application window is open.
The rule covers reserves, redemption, risk management, audits and reporting, custody, applications, foreign issuers, capital and operational safeguards. It also addresses certain state-qualified issuers and the OCC’s authority to revoke approval.
No. The OCC left Bank Secrecy Act, anti-money laundering and sanctions requirements to separate rulemaking with the Treasury Department. Issuers need to track that workstream alongside the OCC’s prudential and operational requirements.
No. It applies to payment stablecoin issuers and related activities within the OCC’s jurisdiction, including specified bank subsidiaries, federally approved nonbank issuers, some state-qualified issuers and foreign issuers. The applicable pathway depends on the entity and its activities.

Related articles