The Office of the Comptroller of the Currency (OCC) wants to see the receipts for every stablecoin trade, from the serial number on a tokenized Treasury bond to the wallet address of a large holder, every single week. And America's banks are pushing back hard.
Comment letters filed by the Bank Policy Institute (BPI), the American Bankers Association (ABA), and others reveal a deep rift over how the country's first federal stablecoin regulation will work in practice. As PYMNTS reports, the pushback focuses on crushing operational demands, not the principle of oversight.
This isn't a debate about transparency. It's a fight over whether the OCC can demand a live surveillance feed of a financial product's entire ecosystem. The outcome will determine if a U.S.-chartered stablecoin can ever compete on speed or cost.
A Compliance Auditor in Your Server Room
The OCC's proposed weekly reports are not simple balance sheets. They are a minute-by-minute accounting of market mechanics, designed to let regulators peer directly into the engine of a stablecoin.
The proposed forms cover more than the composition of reserves. Weekly reports would include issuance and redemption activity, exchanges, trading volume, large wallet holders and counterparties, along with detailed information about the assets backing each stablecoin.
For Treasury securities held in reserves, the OCC wants individual CUSIP numbers, fair value, remaining maturity, coupon rates, custodians, and details on any encumbered assets — a data-intensive approach that contrasts with other central banks' focus on using digital assets for broader financial innovation like the Bank of England's crypto trade finance plans. The bank groups call the demand for individual CUSIPs a "substantial burden" and argue for aggregated data instead.
They also question a requirement to identify tokenized reserves separately, arguing for a "technology-neutral approach" since a tokenized Treasury represents the same government claim. If the rule stands, they want reporting in percentage ranges.
On the activity side, Schedule A would reveal large holders by wallet address and major counterparties. Schedule B tracks issuance, redemptions, and secondary market prices. This data aims to let the OCC monitor "primary and secondary markets, including during periods of stress."
The banks' core objection isn't to transparency, but to a weekly cadence that offers little risk management benefit for its immense cost. Stress events in finance rarely unfold within a seven day window. This is a compliance exercise disguised as crisis prevention.
The FDIC's Lighter Touch Highlights the Burden
The bureaucratic burden becomes stark when you compare the OCC's plan to a fellow regulator's approach. The Federal Deposit Insurance Corp. (FDIC) has a tiered proposal.
For issuers with less than $1 billion in outstanding issuance and less than $100 million in average daily transaction volume, the FDIC would collect far less weekly data. The bank groups seized on this, urging the OCC to make its requirements "substantially similar" to other federal regulators.
The Conference of State Bank Supervisors also favors common reporting rules. This lack of coordination itself creates a compliance trap.
| Reporting Aspect | OCC Proposed Weekly Form | Traditional Bank Call Report / FDIC Approach |
|---|---|---|
| Frequency | Weekly (52 reports/year) | Quarterly (4 reports/year) |
| Reserve Detail | Individual CUSIPs for Treasuries | Aggregated asset categories |
| Activity Tracking | Wallet-level holder data, exchanges, counterparties | High-level transaction volumes |
| Applicability | All issuers, regardless of size | Tiered thresholds for smaller entities |
The table shows the OCC's plan is an order of magnitude more granular and frequent than traditional bank reporting. It treats a stablecoin issuer not as a bank, but as a constant systemic threat requiring a live data feed.
The Practical Toll on Banks and the Market
The immediate casualty of this rulemaking is speed. Banks warn the weekly deadline leaves insufficient time to prepare and validate reports. They seek "additional time" and recommend reducing duplication by auto-populating common data fields from existing systems.
The format debate is also critical. The OCC plans to keep weekly reports confidential but publish quarterly financial condition reports. XBRL US, in a separate April comment, argued all data should be public and machine-readable (like XBRL) to allow for automated validation and market alerts.
Operational friction has direct market consequences. As we've seen in other fintech sectors where regulation adds friction, costs are ultimately passed to users. If the OCC's rule stands, it will cement a two track system: agile, state-chartered or offshore issuers will operate with a massive cost and speed advantage over federally-regulated ones.
It also signals that Washington's top banking regulator views stablecoins through a lens of containment, not innovation. This chills development beyond pure issuance. Why would a federally-regulated bank build a stablecoin product knowing it invites a compliance auditor into its data warehouse every Monday morning?
XOOMAR Analysis: The Likely Compromise and What to Watch
The OCC is unlikely to abandon its core demand for granular data. Its stated goal is "visibility" into reserves and activity during stress. The industry's win will be on frequency and format, not substance. Here is what to watch as the rulemaking process continues:
First, the sequencing. The BPI and ABA explicitly stated the OCC should finalize the underlying GENIUS Act rules first, then repropose reporting forms. The OCC itself acknowledged the current forms may need modification. Any movement to decouple the reporting proposal from the main rule's finalization would be a major concession.
Second, the compromise on timing. A shift from a rigid weekly deadline to a threshold-based or event-driven reporting trigger is the most likely outcome. For example, issuers might report detailed data only when reserve composition changes by a certain percentage or trading volume spikes. This aligns more closely with the FDIC's tiered approach.
Third, the data format. The push for machine-readable standards like XBRL is strong and logical. It allows for reuse of data from existing Call Reports and enables the automation banks desperately need. The OCC adopting a structured data mandate would be a win for efficiency, even as it locks in the compliance overhead.
The final shape of this rule will determine the practical reality of federally-regulated stablecoins. If the weekly burden stands, it will act as a powerful market concentrator, favoring only the largest, best-resourced institutions. If a smarter, risk-based framework emerges, it could provide the clarity needed for responsible innovation to flourish under a U.S. charter.
For the broader digital asset ecosystem, this fight is a bellwether. It shows that even with enabling legislation like the GENIUS Act, the details of implementation can create a regulatory moat. Developers and investors should watch the final OCC reporting rules as closely as the law itself. The future of private sector digital dollars may depend on it.
Disclaimer: This XOOMAR analysis is for informational and educational purposes only. It is not financial, investment, legal, tax, or professional advice. It does not provide buy, sell, hold, price-target, portfolio, or personalized recommendations. Verify information independently and consult qualified professionals before making decisions.
Impact Analysis
- This regulatory battle will set the operational and cost framework for U.S.-chartered stablecoins, determining their ability to compete globally.
- The outcome directly affects banks' compliance costs and regulatory burden, potentially stifling innovation or enabling safer, faster products.
- It establishes a precedent for how deeply regulators can surveil digital asset ecosystems, balancing transparency with operational feasibility.
Originally published on XOOMAR. For more news and analysis, visit XOOMAR.
