Last week turned several abstract debates about digital money into concrete rules and permission models. The US proposed reserve, capital, and approval requirements for federally supervised stablecoin issuers. The European Banking Authority (EBA) asked MiCA reviewers to address multi-issuer stablecoins and crypto lending more directly. On the product side, scoped wallet permissions enabled subscriptions without a fresh signature for every charge, while native hardware signing reached shielded Zcash. Tokenized deposits also moved beyond isolated pilots toward integration with existing bank messaging and payment networks.
This brief covers announcements and developments from September 21–27, 2026, in Korea Standard Time.
1. The Federal Reserve proposes GENIUS Act rules for stablecoin issuers
On September 24, the Federal Reserve Board opened comment on two proposals implementing the GENIUS Act. The first would require Board-supervised payment stablecoin issuers to back all outstanding tokens with permitted high-quality liquid assets, including short-term Treasury bills. It also introduces standardized capital requirements for credit and operational risk, risk-management standards, obligations for Board-supervised reserve custodians, and clarification of permissible stablecoin activities for banks.
The second proposal creates a tailored application process for a Board-supervised state member bank that wants a subsidiary to issue payment stablecoins. An applicant would submit a business plan and financial information, with proposed procedures for appeals, hearings, and final decisions. Neither proposal is final. The comment period runs for 60 days after publication in the Federal Register.
Matching reserve book value to tokens outstanding is not enough if an issuer cannot deliver par redemption during stress. Federal Reserve Governor Michael Barr separately called for clear universal redemption rights and closer attention to interest-rate and foreign-exchange risk. That puts issuance, redemption, reserve management, and custody on distinct operational boundaries.
2. Polygon OMS adds recurring stablecoin payments with one approval
Polygon Labs introduced recurring stablecoin payment rules in Open Money Stack (OMS) on September 21. A user approves a maximum charge, allowed contracts and actions, billing period, and expiry. When a service backend later requests payment, the wallet's onchain Sessions Module checks the request against those terms and rejects out-of-scope calls at the contract level. The user can revoke future payments.
The experience resembles a stored-card subscription, but the authorization model differs. A merchant does not hold the payment instrument, and a server does not receive general wallet access. Instead, a remote backend operates through a bounded session. Polygon's Smart Sessions documentation says sessions are time-limited and revocable, and operate within approved native-token or ERC-20 transfer grants. The session key remains inside an enclave, and the backend cannot widen its own permissions.
Removing a signature from every billing cycle does not make the flow trustless. Wallet-as-a-Service (WaaS) manages session signers and configuration updates, so enclave and backend availability still affect payment execution. Revocation immediately stops WaaS from using a session, while removal of its onchain configuration entry occurs during a subsequent wallet execution. Products need to distinguish the revocation state a user sees from the state recorded onchain.
3. Ledger Wallet brings shielded Zcash into the hardware-signer flow
Ledger announced native shielded Zcash support in Ledger Wallet Desktop on September 23. Managing shielded ZEC with a Ledger device previously required a separate companion wallet. Users can now add, send, and receive shielded balances in the desktop application. The integration supports Ironwood, the shielded pool activated in July 2026; mobile support is not yet available.
ZEC can move through a transparent pool, where addresses, balances, and transaction details are public much like Bitcoin, or through a shielded pool, where zero-knowledge proofs validate transactions without publicly revealing addresses and amounts. Shielded Zcash uses the same ZEC in a privacy-preserving pool. This release brings the Ironwood shielded pool into Ledger Wallet.
The boundary in which private keys remain on the device while the computer handles transaction computation is the general hardware-wallet model Ledger already uses for transparent ZEC. The shielded-specific work puts zero-knowledge proof computation on the computer while extending the Ledger device to understand the new cryptographic curves, address formats, and Ironwood transaction structure before displaying and signing a transfer. Ledger says the integration included on-device transaction parsing and security audits. Users can also grant read-only transaction-history access to a tax adviser or compliance officer without granting spending authority.
Bringing privacy into the primary wallet changes more than a feature checklist. A public explorer cannot reveal the recipient and amount of a shielded transfer, which makes wallet history, backups, and audit exports more important evidence. Conversely, an overbroad viewing capability can reveal an entire history that remains private onchain.
4. The EBA asks MiCA reviewers to prioritize multi-issuer stablecoins and DeFi lending
MiCA, the Markets in Crypto-Assets Regulation, is the EU-wide framework for crypto-assets and related services not already covered by other Union financial-services laws. It governs issuance, disclosure, admission to trading, authorization and supervision of service providers and stablecoin issuers, customer protection, and market-abuse controls. It treats stablecoins linked to one official currency as e-money tokens (EMTs), while tokens linked to other assets or a basket of assets are asset-referenced tokens (ARTs).
On September 24, the EBA published its formal response to the European Commission's MiCA review consultation. It found the current framework for ART and EMT issuers broadly appropriate, but recommended stronger treatment of third-country multi-issuer stablecoin arrangements. It also proposed revisiting minimum bank-deposit allocations within issuer reserves while preserving effective risk management.
In a multi-issuer structure, one token brand may be issued by different legal entities or in different jurisdictions. The assets can look interchangeable in a product while carrying different issuers, reserve pools, redemption claims, and loss-bearing entities. The EBA also said ambiguity in crypto-asset classification creates avoidable cost and launch delays, and called for clearer MiCA definitions and scope.
The response further asks the Commission to consider regulating crypto-asset lending, including cases in which a crypto-asset service provider facilitates access to decentralized lending protocols. As of September 1, 39 EMTs had been issued under MiCA and no ART had been authorized. This is a supervisory recommendation to the Commission's review—not an amended law or an immediately applicable rule.
5. Tokenized deposits connect to Swift and US bank payment rails
Two September 24 announcements showed tokenized deposits moving from isolated blockchain pilots into existing bank operations. IBM launched a beta Digital Asset Haven connection to Swift's shared ledger. Its ISO 20022 Messaging Adapter lets institutions instruct tokenized-deposit transactions using established message formats and compliance processes. Swift lists 17 banks in the initial live-transaction cohort.
IBM also introduced an on-premises Digital Asset Haven beta for IBM Z and LinuxONE. Institutions can keep the solution and key-management layers in their own data centers, using Crypto Express HSMs and confidential computing to separate environments. IBM says the same APIs and workflows span SaaS, hybrid, and on-premises deployments, allowing institutions to move workloads without changing application code.
The same day, The Clearing House selected Quant to provide technology for its On-Chain Money Initiative, a US bank network for clearing and settling tokenized deposits. Quant will supply interoperability, orchestration, and transaction management while connecting existing RTP and CHIPS rails. Availability to participating institutions is targeted for the first half of 2027.
Neither announcement is a public stablecoin launch. A tokenized deposit represents a bank deposit and remains inside the bank's access, ledger, and compliance perimeter. IBM's description also says tokenized assets can move around the clock ahead of final settlement through existing systems. An onchain record, a bank-ledger posting, and final fiat settlement remain distinct states.
This brief is based on analysis generated with Codex each Monday. It is published only after the blog operator's direct review and approval.