GENIUS Act Stablecoin Requirements

What Section 2(22) Classification Means for Your Protocol

by

Teddy Ellison

Blockchain & Tokenization

Summary

The GENIUS Act (the “Act”) created a three-part statutory test (Section 2(22)) that determines whether your token is a "payment stablecoin." If it is, only a permitted payment stablecoin issuer (PPSI) can issue it to US users. Violating the prohibition carries up to $1 million per violation and five years imprisonment. The Act’s effective date is January 18, 2027.


Until the GENIUS Act passed, there was no federal framework for a compliant US stablecoin issuer to follow. Issuers were navigating state money-transmitter licensing rules and SEC staff positions. The Act created a federal licensing pathway, codified reserve standards, and set a compliance deadline. The OCC finalized its implementing rule on October 21, 2026, so teams planning a US stablecoin issuance now have a defined process.

Many protocol teams read "permitted payment stablecoin issuer," decide the label doesn't apply to them, and move on. On the licensing question, that conclusion is usually right. But they skip the Section 2(22) definition test that determines whether a PPSI license is required, and the separate front-end DASP analysis that applies whether or not you are an issuer.

For teams whose token does meet the statutory definition, the pending FinCEN/OFAC rules would extend the issuer's compliance perimeter into secondary-market transactions through smart-contract-level freeze and blocklist controls. Paradigm and the Hyperliquid Policy Center have already argued in public comments that this would push compliant stablecoins out of open DeFi entirely. For teams whose token doesn't meet the definition, the front-end DASP analysis is a separate question, with its own compliance obligations and a July 2028 effective date.

The Section 2(22) three-part test is the classification that splits those two tracks. Issuers must build their capital, governance, and AML programs before it can file with the OCC. The compliance deadline is January 18, 2027 and the OCC application clock alone runs 120 days.

The Section 2(22) test determines which track you're on

Under Section 3(a), only a permitted payment stablecoin issuer can lawfully issue a payment stablecoin in the United States. Criminal penalties under Section 3(f) run up to $1 million per violation and 5 years imprisonment for knowing participation. No decentralization carve-out exists for the issuer.

Whether that applies to your protocol depends on whether your token meets the three-part test in Section 2(22). A "payment stablecoin" under the Act is a digital asset that (1) is, or is designed to be, used as a means of payment or settlement, (2) whose issuer is obligated to convert, redeem, or repurchase it for a fixed monetary value and represents it will maintain, or creates the reasonable expectation that it will maintain, stable value relative to that amount, and (3) is not a national currency, a deposit, or a security.

Whether your token is a security is a separate analysis under the SEC and CFTC framework, which we cover in token launches after the SEC/CFTC interpretation.

Teams often misread part two. The test keys off what the issuer commits to and represents, not what the team calls the token. The statute also captures tokens that “create the reasonable expectation” of stability, so the classification can rest on design and context even without an explicit promise. A protocol that makes a redemption commitment at $1 in the smart contract or the terms of service and distributes a token used for settlement has likely satisfied parts one and two. The word "stablecoin" does not need to appear anywhere.

The issuer compliance build includes the licensing pathway, reserve architecture, AML program, and OCC application process, each with their own lead time. It also raises an unresolved question about secondary-market sanctions: whether issuers will be required to enforce sanctions compliance on secondary-market transactions they have no visibility into.

The licensing pathway

The statute gives three routes to PPSI status: through an insured depository subsidiary, a nonbank federal qualified issuer approved by the OCC, or a state qualified issuer. Most seed-through-Series-B protocol teams opt for the nonbank OCC pathway.

The OCC's implementation NPRM (published March 2, 2026) defines the application process and capital requirements for nonbank issuers. In recent approvals, the OCC has set required capital from $6 million to $25 million, with a $5 million floor during the de novo period, plus a 12-month operational liquidity buffer. The statutory decision clock runs 120 days from a complete application, but application preparation, capital formation, and governance build-out all need to happen before filing.

The reserve architecture

Section 4(a)(1) requires 1:1 reserves held in US currency, demand deposits at insured depository institutions, Treasuries with a remaining or original maturity of 93 days or less, overnight repurchase and reverse repurchase agreements backed by Treasuries, government money-market funds invested in those assets, or other similarly liquid Federal government-issued assets that regulators approve. Section 4(a)(2) prohibits rehypothecation, with narrow exceptions.

Section 4(a)(3) requires monthly reserve attestations certified by the CEO and CFO and examined by a registered accounting firm. The issuer builds custodial relationships, accounting systems, and a certification process before the first attestation is due.

The AML program

The joint FinCEN/OFAC NPRM (published April 10, 2026, comments closed June 9, 2026) would require a written, risk-based AML/CFT program, a US-based compliance officer, SAR filing, and Travel Rule compliance for transfers of $3,000 or more. The FinCEN CIP NPRM (published June 2026, comments closed August 21, 2026) scopes customer identification to the primary market only. Both are still proposed rules, even with the OCC rule final.

The secondary-market sanctions perimeter

The same FinCEN/OFAC proposal would require issuers to maintain block, freeze, and reject technical capability reaching secondary-market addresses via smart contract. Paradigm and the Hyperliquid Policy Center argued in joint comments (June 9, 2026) that this conflicts with Van Loon v. Department of the Treasury (5th Cir., Nov. 26, 2024), which held that immutable smart contracts are not property under IEEPA because they are not capable of being owned.

Issuers facing secondary-market obligations they can't meet, they argue, will deploy only to permissioned environments. The final rule is still pending. Issuers need to engineer the freeze and blocklist capability now, whatever the final rule requires.

The gray zone

Hybrid and partially-backed stable-value tokens (the Frax or Ethena-style architecture) present a specific classification problem. A crypto-collateralized token that is redeemable at a fixed value and used for settlement may satisfy parts one and two of Section 2(22), but it cannot meet the 1:1 HQLA reserve requirement in Section 4(a)(1). Whether that makes it an unlawful payment stablecoin or an unregulated non-payment stablecoin is a question the statute does not answer.

Section 14 ordered a Treasury-led study of "endogenously collateralized" stablecoins. If your token sits on this fault line, the classification question needs a definitive answer before January 2027.

The GENIUS Act may apply even if you don't issue a payment stablecoin 

Even if your token does not meet the Section 2(22) definition, that does not mean your protocol falls outside the GENIUS Act entirely. The Act creates a separate set of obligations for "digital asset service providers" (DASPs) that offer or sell payment stablecoins to US persons, and that prohibition takes effect approximately July 2028 (Section 3(b)). If your protocol operates a front end that facilitates stablecoin transactions, you need to determine whether it falls inside or outside the DASP definition.

The statute excludes five categories from DASP status:

  • Distributed ledger protocols

  • Developing or operating distributed ledger protocols or self-custodial software interfaces

  • Immutable and self-custodial software interfaces,

  • Validating transactions or operating a distributed ledger

  • Participating in a liquidity pool or similar liquidity-provisioning mechanism

These exclusions are narrow and fact-specific. A non-custodial, immutable interface that doesn't earn fees from transfers is likely outside the definition.

A hosted, upgradeable front end that routes stablecoin transactions for compensation, or takes custody of stablecoin balances, requires a closer look at whether the exclusions apply. The statute also directs Treasury to report on how the DASP definition applies to DeFi, which means this boundary could move.

If you're not yet a PPSI and your protocol moves stablecoins as a business, you may still need state money-transmitter licenses under existing law. GENIUS preemption only attaches once you're an approved PPSI.

The July 2028 date matters now because the features that decide whether an exclusion applies (custody model, fee structure, upgradeability) get locked into the product long before any compliance review.

A framework for founders

Knowing which decisions require counsel, which require careful self-review, and which are straightforward is what keeps that gap from opening. Our Tech Founder's DIY Legal Guide offers a general framework for how to approach these decisions, which we've translated to some stablecoin compliance-specific guidance below.

What founders can handle themselves

You don't need a lawyer to run the Section 2(22) classification or map your front end against the DASP definition. The three-part test is public and the statutory text is readable. Pull your token documentation, your smart contract terms, and your terms of service.

Confirm whether anything in those documents creates a redemption obligation at a fixed monetary value and a stable-value representation. If it does, you're likely inside the definition. If it doesn't, write down why your token doesn't meet the definition, then move to the front-end question.

The front-end analysis is also manageable without counsel at the first pass. Map your interface against the five DASP exclusions listed above. An immutable, non-custodial interface that doesn't earn transfer fees is likely excluded. Put the exclusion map in writing as well.

Where it gets complicated

Legal support becomes important when the Section 2(22) classification doesn't produce a clean answer, and for hybrid token designs it frequently doesn't.

As discussed above, hybrid designs that satisfy the Section 2(22) definition but can't meet the reserve requirements sit in a classification gap the statute doesn't resolve. A team that misreads it in one direction issues without a license. A team that misreads it in the other builds a compliance program the token never required.

Front-end applications that route stablecoin transactions for compensation and don't fall cleanly inside the DASP exclusions are in the same category. If your interface is hosted, upgradeable, or takes any form of custody, the exclusion analysis requires more than a first-pass read of Section 2.

The OCC nonbank federal-qualified PPSI pathway and the capital requirements that flow from it also require legal guidance. Teams that know they are inside the definition and are evaluating the OCC pathway need to understand the capital math before committing to the application timeline.

Where expert counsel becomes mandatory

Outside counsel earns its place when the classification outcome, the PPSI application, and the OFAC technical build all need to land on a timeline that is already compressed.

If your token meets the Section 2(22) definition and you have US users, the PPSI licensing process, the reserve architecture, the AML program build, and the OFAC secondary-market sanctions capability all need to be coordinated against the January 2027 compliance deadline. The OCC decision clock runs 120 days from a complete application, and everything that makes an application complete sits in front of that clock.

If your token design sits in the algorithmic or hybrid gray zone and the Section 14 study has not resolved whether it falls inside or outside the definition, that classification needs a definitive answer before January 2027.

The pending OFAC secondary-market requirement, which would impose block, freeze, and reject controls reaching secondary-market addresses via smart contract, adds a smart-contract engineering build on top of the compliance program. The outcome of the comment process is contested, but the capability needs to be engineered regardless. Serotonin Legal works through this kind of structural classification, pathway sequencing, and compliance build for protocol teams at this stage.

For more on which legal decisions founders can handle on their own and which call for counsel, we answer the questions tech founders ask us most here. 

Final Thoughts

Most protocol teams stopped at the PPSI licensing question and never ran the two analyses that follow from it. If you have a stable-value token with an unclassified redemption commitment, a front end routing stablecoin transactions for compensation, or a token design in the hybrid gray zone, the classification is worth documenting now, with the OCC rule final and the sanctions rulemaking still open.

If you have any questions, reach out and we will give you a clear read on where you stand.


Reach out to set up a free consultation.


This post is for informational purposes only and does not constitute legal advice. The GENIUS Act's implementing rules are all in proposed form as of the date of this post; operative compliance details remain subject to change. Consult qualified legal counsel regarding your specific situation.

FAQs

What is a payment stablecoin under the GENIUS Act?

A payment stablecoin under Section 2(22) of the GENIUS Act is a digital asset that meets three conditions: it is, or is designed to be, used as a means of payment or settlement; the issuer is obligated to convert, redeem, or repurchase it for a fixed monetary value and represents that it will maintain stable value; and it is not a national currency, a deposit, or a security. The definition turns on issuer conduct and representation, not on marketing or token naming. A token that meets all three parts is a payment stablecoin regardless of how the issuer characterizes it. Only a permitted payment stablecoin issuer may issue one to US persons.

What are the reserve requirements for stablecoin issuers under the GENIUS Act?

Section 4(a)(1) requires a PPSI to hold reserves of at least 1:1 with outstanding payment stablecoins, limited to US currency, demand deposits at insured depository institutions, US Treasuries with 93 days or less remaining maturity, overnight repos backed by those Treasuries, or government money-market funds invested in those underlying assets. Section 4(a)(2) prohibits rehypothecation, with narrow exceptions. Monthly reserve attestations certified by the CEO and CFO, examined by a registered accounting firm, are required under Section 4(a)(3). PPSIs above $50 billion outstanding are subject to annual GAAP audited financial statements.

What is the GENIUS Act compliance deadline?

The GENIUS Act (Pub. L. 119-27) takes effect on the earlier of January 18, 2027, or 120 days after final implementing regulations are published. As of the date of this post, all major implementing rules (the OCC nonbank PPSI NPRM, the FDIC implementation NPRM, the Treasury AML/CFT NPRM, and the FinCEN CIP NPRM) remain in proposed form. If any implementing rules finalize before September 2026, the 120-day trigger would pull the effective date forward. The secondary-market DASP prohibition has a separate effective date of approximately July 18, 2028.

Does the GENIUS Act apply to DeFi protocols that don't issue stablecoins?

Issuing a payment stablecoin is the most direct trigger for PPSI obligations, but the Act also creates obligations for digital asset service providers that offer or sell payment stablecoins to US persons. That prohibition takes effect approximately July 2028, three years post-enactment. The Act excludes immutable, non-custodial, self-custodial software interfaces and liquidity pool participation from the DASP definition, but those exclusions are narrow and fact-specific. A DeFi protocol operating a hosted, upgradeable front end that routes stablecoin transactions for compensation may not be excluded. The IRS DeFi broker rule was repealed separately by Public Law No. 119-5 in April 2025.

What happens if I issue a payment stablecoin without PPSI approval?

Section 3(a) makes it unlawful for any person other than a PPSI to issue a payment stablecoin in the United States. Section 3(f) provides criminal penalties of up to $1 million per violation and up to five years imprisonment for knowing participation. Civil enforcement is also available. No decentralization carve-out exempts a distributed protocol if the token it issues meets the Section 2(22) definition. Getting the classification wrong and proceeding to issue is not a gray-area problem once the issuer has been put on notice.

Curious to learn more about Serotonin Legal? —

Get in Touch

GENIUS Act Stablecoin Requirements

What Section 2(22) Classification Means for Your Protocol

by

Teddy Ellison

Blockchain & Tokenization

Summary

The GENIUS Act (the “Act”) created a three-part statutory test (Section 2(22)) that determines whether your token is a "payment stablecoin." If it is, only a permitted payment stablecoin issuer (PPSI) can issue it to US users. Violating the prohibition carries up to $1 million per violation and five years imprisonment. The Act’s effective date is January 18, 2027.


Until the GENIUS Act passed, there was no federal framework for a compliant US stablecoin issuer to follow. Issuers were navigating state money-transmitter licensing rules and SEC staff positions. The Act created a federal licensing pathway, codified reserve standards, and set a compliance deadline. The OCC finalized its implementing rule on October 21, 2026, so teams planning a US stablecoin issuance now have a defined process.

Many protocol teams read "permitted payment stablecoin issuer," decide the label doesn't apply to them, and move on. On the licensing question, that conclusion is usually right. But they skip the Section 2(22) definition test that determines whether a PPSI license is required, and the separate front-end DASP analysis that applies whether or not you are an issuer.

For teams whose token does meet the statutory definition, the pending FinCEN/OFAC rules would extend the issuer's compliance perimeter into secondary-market transactions through smart-contract-level freeze and blocklist controls. Paradigm and the Hyperliquid Policy Center have already argued in public comments that this would push compliant stablecoins out of open DeFi entirely. For teams whose token doesn't meet the definition, the front-end DASP analysis is a separate question, with its own compliance obligations and a July 2028 effective date.

The Section 2(22) three-part test is the classification that splits those two tracks. Issuers must build their capital, governance, and AML programs before it can file with the OCC. The compliance deadline is January 18, 2027 and the OCC application clock alone runs 120 days.

The Section 2(22) test determines which track you're on

Under Section 3(a), only a permitted payment stablecoin issuer can lawfully issue a payment stablecoin in the United States. Criminal penalties under Section 3(f) run up to $1 million per violation and 5 years imprisonment for knowing participation. No decentralization carve-out exists for the issuer.

Whether that applies to your protocol depends on whether your token meets the three-part test in Section 2(22). A "payment stablecoin" under the Act is a digital asset that (1) is, or is designed to be, used as a means of payment or settlement, (2) whose issuer is obligated to convert, redeem, or repurchase it for a fixed monetary value and represents it will maintain, or creates the reasonable expectation that it will maintain, stable value relative to that amount, and (3) is not a national currency, a deposit, or a security.

Whether your token is a security is a separate analysis under the SEC and CFTC framework, which we cover in token launches after the SEC/CFTC interpretation.

Teams often misread part two. The test keys off what the issuer commits to and represents, not what the team calls the token. The statute also captures tokens that “create the reasonable expectation” of stability, so the classification can rest on design and context even without an explicit promise. A protocol that makes a redemption commitment at $1 in the smart contract or the terms of service and distributes a token used for settlement has likely satisfied parts one and two. The word "stablecoin" does not need to appear anywhere.

The issuer compliance build includes the licensing pathway, reserve architecture, AML program, and OCC application process, each with their own lead time. It also raises an unresolved question about secondary-market sanctions: whether issuers will be required to enforce sanctions compliance on secondary-market transactions they have no visibility into.

The licensing pathway

The statute gives three routes to PPSI status: through an insured depository subsidiary, a nonbank federal qualified issuer approved by the OCC, or a state qualified issuer. Most seed-through-Series-B protocol teams opt for the nonbank OCC pathway.

The OCC's implementation NPRM (published March 2, 2026) defines the application process and capital requirements for nonbank issuers. In recent approvals, the OCC has set required capital from $6 million to $25 million, with a $5 million floor during the de novo period, plus a 12-month operational liquidity buffer. The statutory decision clock runs 120 days from a complete application, but application preparation, capital formation, and governance build-out all need to happen before filing.

The reserve architecture

Section 4(a)(1) requires 1:1 reserves held in US currency, demand deposits at insured depository institutions, Treasuries with a remaining or original maturity of 93 days or less, overnight repurchase and reverse repurchase agreements backed by Treasuries, government money-market funds invested in those assets, or other similarly liquid Federal government-issued assets that regulators approve. Section 4(a)(2) prohibits rehypothecation, with narrow exceptions.

Section 4(a)(3) requires monthly reserve attestations certified by the CEO and CFO and examined by a registered accounting firm. The issuer builds custodial relationships, accounting systems, and a certification process before the first attestation is due.

The AML program

The joint FinCEN/OFAC NPRM (published April 10, 2026, comments closed June 9, 2026) would require a written, risk-based AML/CFT program, a US-based compliance officer, SAR filing, and Travel Rule compliance for transfers of $3,000 or more. The FinCEN CIP NPRM (published June 2026, comments closed August 21, 2026) scopes customer identification to the primary market only. Both are still proposed rules, even with the OCC rule final.

The secondary-market sanctions perimeter

The same FinCEN/OFAC proposal would require issuers to maintain block, freeze, and reject technical capability reaching secondary-market addresses via smart contract. Paradigm and the Hyperliquid Policy Center argued in joint comments (June 9, 2026) that this conflicts with Van Loon v. Department of the Treasury (5th Cir., Nov. 26, 2024), which held that immutable smart contracts are not property under IEEPA because they are not capable of being owned.

Issuers facing secondary-market obligations they can't meet, they argue, will deploy only to permissioned environments. The final rule is still pending. Issuers need to engineer the freeze and blocklist capability now, whatever the final rule requires.

The gray zone

Hybrid and partially-backed stable-value tokens (the Frax or Ethena-style architecture) present a specific classification problem. A crypto-collateralized token that is redeemable at a fixed value and used for settlement may satisfy parts one and two of Section 2(22), but it cannot meet the 1:1 HQLA reserve requirement in Section 4(a)(1). Whether that makes it an unlawful payment stablecoin or an unregulated non-payment stablecoin is a question the statute does not answer.

Section 14 ordered a Treasury-led study of "endogenously collateralized" stablecoins. If your token sits on this fault line, the classification question needs a definitive answer before January 2027.

The GENIUS Act may apply even if you don't issue a payment stablecoin 

Even if your token does not meet the Section 2(22) definition, that does not mean your protocol falls outside the GENIUS Act entirely. The Act creates a separate set of obligations for "digital asset service providers" (DASPs) that offer or sell payment stablecoins to US persons, and that prohibition takes effect approximately July 2028 (Section 3(b)). If your protocol operates a front end that facilitates stablecoin transactions, you need to determine whether it falls inside or outside the DASP definition.

The statute excludes five categories from DASP status:

  • Distributed ledger protocols

  • Developing or operating distributed ledger protocols or self-custodial software interfaces

  • Immutable and self-custodial software interfaces,

  • Validating transactions or operating a distributed ledger

  • Participating in a liquidity pool or similar liquidity-provisioning mechanism

These exclusions are narrow and fact-specific. A non-custodial, immutable interface that doesn't earn fees from transfers is likely outside the definition.

A hosted, upgradeable front end that routes stablecoin transactions for compensation, or takes custody of stablecoin balances, requires a closer look at whether the exclusions apply. The statute also directs Treasury to report on how the DASP definition applies to DeFi, which means this boundary could move.

If you're not yet a PPSI and your protocol moves stablecoins as a business, you may still need state money-transmitter licenses under existing law. GENIUS preemption only attaches once you're an approved PPSI.

The July 2028 date matters now because the features that decide whether an exclusion applies (custody model, fee structure, upgradeability) get locked into the product long before any compliance review.

A framework for founders

Knowing which decisions require counsel, which require careful self-review, and which are straightforward is what keeps that gap from opening. Our Tech Founder's DIY Legal Guide offers a general framework for how to approach these decisions, which we've translated to some stablecoin compliance-specific guidance below.

What founders can handle themselves

You don't need a lawyer to run the Section 2(22) classification or map your front end against the DASP definition. The three-part test is public and the statutory text is readable. Pull your token documentation, your smart contract terms, and your terms of service.

Confirm whether anything in those documents creates a redemption obligation at a fixed monetary value and a stable-value representation. If it does, you're likely inside the definition. If it doesn't, write down why your token doesn't meet the definition, then move to the front-end question.

The front-end analysis is also manageable without counsel at the first pass. Map your interface against the five DASP exclusions listed above. An immutable, non-custodial interface that doesn't earn transfer fees is likely excluded. Put the exclusion map in writing as well.

Where it gets complicated

Legal support becomes important when the Section 2(22) classification doesn't produce a clean answer, and for hybrid token designs it frequently doesn't.

As discussed above, hybrid designs that satisfy the Section 2(22) definition but can't meet the reserve requirements sit in a classification gap the statute doesn't resolve. A team that misreads it in one direction issues without a license. A team that misreads it in the other builds a compliance program the token never required.

Front-end applications that route stablecoin transactions for compensation and don't fall cleanly inside the DASP exclusions are in the same category. If your interface is hosted, upgradeable, or takes any form of custody, the exclusion analysis requires more than a first-pass read of Section 2.

The OCC nonbank federal-qualified PPSI pathway and the capital requirements that flow from it also require legal guidance. Teams that know they are inside the definition and are evaluating the OCC pathway need to understand the capital math before committing to the application timeline.

Where expert counsel becomes mandatory

Outside counsel earns its place when the classification outcome, the PPSI application, and the OFAC technical build all need to land on a timeline that is already compressed.

If your token meets the Section 2(22) definition and you have US users, the PPSI licensing process, the reserve architecture, the AML program build, and the OFAC secondary-market sanctions capability all need to be coordinated against the January 2027 compliance deadline. The OCC decision clock runs 120 days from a complete application, and everything that makes an application complete sits in front of that clock.

If your token design sits in the algorithmic or hybrid gray zone and the Section 14 study has not resolved whether it falls inside or outside the definition, that classification needs a definitive answer before January 2027.

The pending OFAC secondary-market requirement, which would impose block, freeze, and reject controls reaching secondary-market addresses via smart contract, adds a smart-contract engineering build on top of the compliance program. The outcome of the comment process is contested, but the capability needs to be engineered regardless. Serotonin Legal works through this kind of structural classification, pathway sequencing, and compliance build for protocol teams at this stage.

For more on which legal decisions founders can handle on their own and which call for counsel, we answer the questions tech founders ask us most here. 

Final Thoughts

Most protocol teams stopped at the PPSI licensing question and never ran the two analyses that follow from it. If you have a stable-value token with an unclassified redemption commitment, a front end routing stablecoin transactions for compensation, or a token design in the hybrid gray zone, the classification is worth documenting now, with the OCC rule final and the sanctions rulemaking still open.

If you have any questions, reach out and we will give you a clear read on where you stand.


Reach out to set up a free consultation.


This post is for informational purposes only and does not constitute legal advice. The GENIUS Act's implementing rules are all in proposed form as of the date of this post; operative compliance details remain subject to change. Consult qualified legal counsel regarding your specific situation.

FAQs

What is a payment stablecoin under the GENIUS Act?

A payment stablecoin under Section 2(22) of the GENIUS Act is a digital asset that meets three conditions: it is, or is designed to be, used as a means of payment or settlement; the issuer is obligated to convert, redeem, or repurchase it for a fixed monetary value and represents that it will maintain stable value; and it is not a national currency, a deposit, or a security. The definition turns on issuer conduct and representation, not on marketing or token naming. A token that meets all three parts is a payment stablecoin regardless of how the issuer characterizes it. Only a permitted payment stablecoin issuer may issue one to US persons.

What are the reserve requirements for stablecoin issuers under the GENIUS Act?

Section 4(a)(1) requires a PPSI to hold reserves of at least 1:1 with outstanding payment stablecoins, limited to US currency, demand deposits at insured depository institutions, US Treasuries with 93 days or less remaining maturity, overnight repos backed by those Treasuries, or government money-market funds invested in those underlying assets. Section 4(a)(2) prohibits rehypothecation, with narrow exceptions. Monthly reserve attestations certified by the CEO and CFO, examined by a registered accounting firm, are required under Section 4(a)(3). PPSIs above $50 billion outstanding are subject to annual GAAP audited financial statements.

What is the GENIUS Act compliance deadline?

The GENIUS Act (Pub. L. 119-27) takes effect on the earlier of January 18, 2027, or 120 days after final implementing regulations are published. As of the date of this post, all major implementing rules (the OCC nonbank PPSI NPRM, the FDIC implementation NPRM, the Treasury AML/CFT NPRM, and the FinCEN CIP NPRM) remain in proposed form. If any implementing rules finalize before September 2026, the 120-day trigger would pull the effective date forward. The secondary-market DASP prohibition has a separate effective date of approximately July 18, 2028.

Does the GENIUS Act apply to DeFi protocols that don't issue stablecoins?

Issuing a payment stablecoin is the most direct trigger for PPSI obligations, but the Act also creates obligations for digital asset service providers that offer or sell payment stablecoins to US persons. That prohibition takes effect approximately July 2028, three years post-enactment. The Act excludes immutable, non-custodial, self-custodial software interfaces and liquidity pool participation from the DASP definition, but those exclusions are narrow and fact-specific. A DeFi protocol operating a hosted, upgradeable front end that routes stablecoin transactions for compensation may not be excluded. The IRS DeFi broker rule was repealed separately by Public Law No. 119-5 in April 2025.

What happens if I issue a payment stablecoin without PPSI approval?

Section 3(a) makes it unlawful for any person other than a PPSI to issue a payment stablecoin in the United States. Section 3(f) provides criminal penalties of up to $1 million per violation and up to five years imprisonment for knowing participation. Civil enforcement is also available. No decentralization carve-out exempts a distributed protocol if the token it issues meets the Section 2(22) definition. Getting the classification wrong and proceeding to issue is not a gray-area problem once the issuer has been put on notice.

Curious to learn more about Serotonin Legal?

Get in Touch