An app’s stablecoin reward can look identical to a customer even when the money behind it follows very different routes. The app might finance a promotion itself. It might instead deliver payments funded by the token’s issuer. The OCC’s finalized approach examines the arrangement’s substance rather than treating the word “rewards” as an answer.
The change announced on October 21, 2026, removes a proposed rebuttable presumption concerning certain intermediary arrangements. It retains the issuer-yield prohibition and the agency’s authority to address evasion. It does not approve every exchange or app program. The announced effective date is January 18, 2027.
Begin with the law’s actual prohibition
Section 4(a)(11) of the GENIUS Act bars permitted payment stablecoin issuers and foreign payment stablecoin issuers from paying holders interest or yield solely in connection with holding, using or retaining a payment stablecoin. The restriction covers value delivered in cash, tokens or other consideration.
Two distinctions matter. First, the provision identifies the issuers to which it applies. Second, it concerns interest or yield paid for the specified connection to a stablecoin. A payment’s name does not determine its character. The word “solely” also belongs in the analysis; removing it would describe a different rule.
A dollar denomination answers neither question. It describes the token’s intended monetary unit, not the legal basis of every benefit associated with it. A reserve-backed token, a platform custody account and a reward promise are separate things to understand.
What was proposed, and what was dropped
The OCC’s final-rule explanation, particularly pages 96–111, sets out the rewards discussion. The earlier proposal would have presumed that certain linked arrangements amounted to prohibited issuer yield. Broadly, an issuer would arrange payments to an affiliate or specified related third party, which would have an arrangement to pay holders yield in connection with the token.
“Rebuttable” meant the issuer could submit written material to challenge that starting assumption. It was a proposed treatment of defined relationships, rather than an already effective universal ban on third-party promotions.
The final approach removes that presumption and examines particular arrangements through applications and supervision. The agency explains that a presumption could be both overinclusive and underinclusive: permissible activity might face an unnecessary rebuttal process, while other prohibited arrangements might appear safe simply because they fell outside the test.
Dropping the test does not eliminate the underlying statutory restriction. It changes the way the agency addresses a disputed boundary.
Follow an invented reward through two companies
Consider a hypothetical token issuer, Mint Company, and a separate distributor, App Company. A customer sees a stablecoin balance and a reward offer inside App Company’s software. These are fictional businesses; neither example below is an approved structure.
Compare the funding records behind the same-looking interface:
| Fictional arrangement | Fact to investigate |
|---|---|
| App Company pays from its own revenue | What the payment is for and whether the issuer is involved |
| Mint Company reimburses App Company for rewards | Whether the intermediary is paying on the issuer’s behalf or facilitating evasion |
Neither row is an approved structure. The table identifies questions about contracts, funding, and purpose that the customer interface cannot answer.
The OCC says an agent paying holders on an issuer’s behalf can fall within the prohibition. Merely paying someone else to make an otherwise forbidden issuer payment can also constitute evasion. Changing the name shown on the credit does not resolve that problem.
Genuine service payments require their own analysis. The agency says bona fide payments for services generally would not be prohibited absent contrary facts, because they generally are not interest or yield solely connected to holding, using or retaining the token. It nevertheless declines to create a general services safe harbor. A contract headed “marketing” cannot substitute for examining what the parties actually do.
Three tempting shortcuts do not settle it
The final rule declines to presume that programs predating the GENIUS Act comply with it. Longevity is therefore not automatic grandfathering. Congress’s awareness of a practice does not establish that it approved every example of that practice.
Nor does a small payment automatically qualify for an exemption. The OCC declines a general safe harbor for minimal payments. Size may form part of the facts, but the rule does not turn every small reward into an approved one.
Finally, connecting a reward to a transaction does not end the inquiry. The statute includes use of a stablecoin. The OCC explains that a transaction-based payment must still be assessed for whether it is interest or yield and whether it is paid solely in the specified connection. The final rule provides no universal list of permissible rewards arrangements.
These points prevent a shortcut from replacing the actual question. They do not mean every promotion is necessarily prohibited.
The app ledger is another layer
Suppose the customer transfers tokens to a wallet controlled by App Company. The company can then display a customer balance and add reward credits in its own records. In this example, a reward credit need not be a separate blockchain transfer. Withdrawal requires the platform to process an outgoing transfer.
This is a custody illustration, separate from the legal rewards test. The SEC staff’s custody bulletin explains that third-party custodians control access to private keys and that customers can lose access when a custodian fails. It also discusses commingling and other uses of customer assets.
Our guide to custodial and self-custody wallets follows that signing authority in more detail. A visible reward rate cannot tell you who controls withdrawal. Equally, a completed transfer cannot prove whether the reward’s funding complies with the issuer-yield restriction.
Keep the calendar and approvals separate
The October 21 announcement identifies January 18, 2027, as the effective date. Finalization and effectiveness are different events. The announcement also says that Bank Secrecy Act, anti-money-laundering and sanctions regulations are being addressed separately with Treasury.
The OCC’s application guidance describes a separate opening for applications after approval of the information collection by the Office of Management and Budget. It also explains waiver requests for eligible applicants. A request is not a granted waiver, and a waiver concerning prior approval is not blanket permission for a rewards arrangement.
The practical reading questions are specific: who issues the token, who funds the benefit, who promises payment, and what is it paid for? Then ask who controls the assets and what approvals actually exist. The final framework leaves room for those facts to matter. An app’s branding cannot supply them.
