Credit unions exploring tokenized deposits, member shares or stablecoin services should not start with the label on the product. They should map who would issue it, what the holder can redeem it for, who would market or custody it and which entity would own the compliance evidence. Treasury’s new proposal makes those functions—not branding—the practical boundary to examine.
The U.S. Treasury Department issued proposed regulations on August 17 to implement the GENIUS Act’s rules for the issuance, offer and sale of payment stablecoins. The proposal was published in the Federal Register on August 18, with comments due October 19.
One question is unusually specific to credit unions: should a digital asset redeemable only in credit-union shares be treated as a payment stablecoin? Treasury asks for evidence rather than announcing an answer. It notes that credit-union shares, like bank deposits, are widely convertible to U.S. dollars and asks whether redemption into shares should therefore count as redemption for monetary value.
That distinction matters because the final definition will help determine whether an arrangement falls inside the act’s issuer-licensing, reserve, disclosure and redemption framework. A request for comment is not a final classification, approval or exemption.
The rule draws two implementation dates
The proposal addresses more than the payment-stablecoin definition. It would define when a person “issues” a stablecoin and when an intermediary offers or sells one in the United States. It also describes the treatment of foreign issuers and the conditions under which digital-asset service providers could handle their tokens.
The GENIUS Act is expected to take effect January 18, 2027. From that date, issuing a payment stablecoin in the United States generally would require the appropriate federal or state license. A separate restriction is expected to take effect July 18, 2028: digital-asset service providers generally could not offer or sell a payment stablecoin in the United States unless it was issued by a permitted issuer.
Those dates do not turn the proposed rule into present authority. The rule is not final, and a credit union or credit-union service organization still would need to establish that its proposed role is legally permitted and licensed under the applicable NCUA, Treasury and state framework.
Credit-union subsidiaries sit inside the proposed perimeter
Treasury’s proposed definition of a depository-institution subsidiary refers to subsidiaries of both insured depository institutions and insured credit unions. That aligns with the NCUA’s separate GENIUS Act implementation work.
In its February licensing proposal, the NCUA said its jurisdiction covers stablecoin issuers that are subsidiaries of federally insured credit unions. The agency said that population can include credit-union service organizations with qualifying credit-union ownership or loans and subsidiaries of state-chartered credit unions.
The February proposal would require a permitted payment-stablecoin issuer to hold liquid reserves at least one-to-one against outstanding tokens, publish monthly reserve information and maintain a redemption policy. It also makes clear that payment stablecoins would not be covered by NCUA share insurance.
A separate NCUA operating-standards proposal would add governance, risk-management, reporting, capital and examination requirements. Both NCUA actions remain proposals. Together with Treasury’s new rulemaking, they show why a credit union cannot evaluate a stablecoin program as a single vendor feature.
A five-part perimeter map for credit unions
1. Define the asset and redemption promise. Record what the member or customer receives, the legal claim represented and whether redemption produces dollars, credit-union shares, another digital asset or a combination. Do not rely on terms such as “tokenized deposit” or “digital cash” to decide scope.
2. Assign every regulated function. Identify the entity that mints, distributes, markets, safeguards, transfers, redeems and monitors the asset. If a CUSO or fintech performs a step, document whether it acts as issuer, service provider, agent or vendor—and who remains accountable.
3. Build the licensing dependency map. Separate authority to invest in or provide services around a stablecoin from authority to issue one. List the required NCUA, Treasury and state decisions, the sequence in which they must occur and the assumptions that could invalidate the program.
4. Test the operational evidence chain. Map reserve attestations, reconciliation, redemption timing, sanctions and transaction monitoring, member disclosures, complaints, incident response and third-party access. The related CreditUnionAI News payment-account guardrails report shows how access, settlement and monitoring controls can span multiple institutions.
5. Preserve a controlled exit. Determine how members would be made whole, records exported and responsibilities transferred if a vendor, issuer or network failed. The CreditUnionAI News vendor exit playbook provides a practical model for keeping data, evidence and operating continuity under institutional control.
What credit unions should do now
Payments, legal, compliance, finance and technology leaders should run one cross-functional scoping session before approving a pilot or vendor contract. The output should be a one-page perimeter map covering the asset, redemption promise, responsible entities, licenses, control evidence and exit path.
Teams should also review Treasury’s exact credit-union-share question and decide whether institution-specific evidence would improve the record. The important point is not to assume the final answer. It is to make the product architecture and its regulatory dependencies visible while the rules are still being shaped.