Skip to content
Finality

Crypto protocol and market news

OCC leaves stablecoin rewards open to case-by-case review

The OCC finalized its GENIUS Act rules without a blanket ban on exchange-paid stablecoin rewards, but issuer-linked payments can still breach the yield prohibition.

The Finality Desk3 min read#205c33

OCC leaves stablecoin rewards open to case-by-case review

The Office of the Comptroller of the Currency finalized rules for payment stablecoin issuers on Oct. 23, leaving crypto platforms able to offer some interest-like rewards while preserving the ban on issuers paying yield to holders. The OCC’s final rule in the Federal Register takes effect Jan. 18, 2027. It does not create a general exemption for rewards: arrangements turn on who pays, whether the issuer directed or funded the payment, and whether it is made solely because a customer holds, uses or retains a payment stablecoin.

What does the rule prohibit issuers from paying?

Section 4(a)(11) of the GENIUS Act bars a permitted payment stablecoin issuer from paying a holder interest or yield, in cash, tokens or other consideration, solely in connection with holding, using or retaining the stablecoin. The restriction applies to issuer payments, including payments made through an agent acting on the issuer’s behalf. Routing the payment through an intermediary does not change who is paying if the intermediary acts for the issuer.

The OCC declined to define “interest” and “yield” or to publish a list of permitted reward arrangements. It says those terms will be interpreted under their generally understood meanings and applied to the facts and circumstances. Calling a payment a reward does not settle its treatment; the agency says labels cannot make interest cease to be interest.

Why can an exchange still pay a reward?

The statute’s prohibition applies to stablecoin issuers. It does not categorically bar another company from paying customers who hold the issuer’s stablecoin. That distinction leaves room for exchange-funded rewards, but it is not a blanket safe harbor. The OCC removed a proposed rebuttable presumption that would have treated certain issuer arrangements with affiliates or related third parties as violations. It retained its authority to address evasion of the statutory ban.

The practical boundary is the payment arrangement. If an issuer pays an affiliate or related third party and that party pays holders solely for holding the issuer’s stablecoin, regulators can assess whether the issuer is paying indirectly or using the structure to evade the prohibition. Where the payment has another basis, such as services or transactions, its treatment depends on the circumstances. The OCC declined to adopt a general safe harbor for rewards, white-label arrangements or payments for services.

What remains uncertain for platforms?

The final rule provides no advance clearance for a platform’s particular program. The OCC says it will assess arrangements under the statute and all relevant facts and circumstances. It also says the agency may exercise enforcement discretion based on those facts. That leaves platforms to assess who funds a reward, the parties’ contracts and whether eligibility or payment depends solely on holding, using or retaining a stablecoin.

The rule also does not treat all digital-dollar balances alike. The GENIUS Act excludes deposits, including deposits recorded on distributed ledger technology, from its definition of payment stablecoin. The OCC says the yield prohibition therefore does not reach interest paid on those deposits. A tokenized deposit and a payment stablecoin may look similar in an app, but the rule applies according to their legal status.

For issuers, the direct yield ban remains. For exchanges and other platforms, rewards remain possible when the issuer is not the payor, but the OCC has not drawn a categorical boundary around those programs. The rule settles the regulator’s approach: assess the payment’s substance and structure case by case, while retaining scrutiny of arrangements that may route issuer-funded yield through another entity.

Sources and documents