Ripple Wins OCC Trust Bank Charter: What It Means for RLUSD Accounting
Ripple has received final approval from the Office of the Comptroller of the Currency (OCC) to operate a national trust bank, the federal charter that will underpin custody and reserve management for its RLUSD stablecoin. With RLUSD's circulating supply reported at approximately $2.6 billion at the time of the announcement, this is not a routine licensing milestone. It is the kind of structural change that affects how accounting teams classify the asset, how compliance officers assess counterparty risk, and how auditors approach reserve attestations. If your firm touches RLUSD in any capacity, the regulatory landscape just changed beneath you.
What the OCC Charter Actually Grants
A national trust bank charter issued by the OCC is distinct from a full commercial banking licence. It does not allow the entity to take retail deposits or make commercial loans in the traditional sense. What it does grant is the authority to act as a federally regulated fiduciary, which includes holding assets in custody, managing trusts, and, critically for Ripple's purposes, holding the reserves that back a stablecoin issuance.
Federal supervision versus state licensing
Before this approval, Ripple's operations relied on a patchwork of state money transmission licences, a structure common across the stablecoin industry. A national trust bank charter supersedes that patchwork with a single federal supervisory relationship. The OCC becomes the primary prudential regulator, with the authority to examine the institution's capital adequacy, liquidity management, internal controls, and AML programme directly. For counterparties, that is a meaningful upgrade in verifiable oversight.
Reserve custody moves in-house
One practical consequence is that Ripple can now self-custody RLUSD reserves within its own federally chartered entity rather than relying entirely on third-party custodians. Whether it chooses to do so fully or partially is an operational decision, but the option itself changes the risk profile. Accounting teams and auditors reviewing RLUSD counterparty arrangements will need to understand where reserves actually sit post-charter, and obtain updated documentation accordingly.
Accounting Classification: Does the Charter Change Anything?
Under US GAAP, stablecoins held by a corporate entity are currently treated as intangible assets subject to impairment testing, absent specific authoritative guidance to the contrary. The FASB's ASU 2023-08, which introduced fair-value measurement for certain crypto assets, applies to assets that meet its scope criteria. Stablecoins pegged to a fiat currency and redeemable on demand at par sit in an arguably different position, and many preparers have historically carried them at cost or as cash equivalents depending on the facts and circumstances.
Issuer regulatory status as a classification input
The OCC charter does not by itself resolve the GAAP classification question. What it does is alter one of the relevant inputs: the regulatory status and supervisory oversight of the issuer. A stablecoin backed by reserves held inside a federally regulated trust bank, subject to OCC examination, is a structurally different instrument from one backed by reserves held in an offshore or lightly regulated vehicle. Preparers who argued for a more favourable classification based on the strength of the issuer's controls now have a stronger factual basis for that position. Conversely, auditors will want to verify the substance of those controls, not merely rely on the existence of the charter.
Practical steps for accounting teams
Firms that hold RLUSD on their balance sheet, or that process it on behalf of clients, should take three immediate steps. First, update the accounting policy memo to reflect the new issuer structure and document the reasoning for the chosen classification. Second, obtain the most recent reserve attestation report issued under the new chartered entity. Third, check whether your existing crypto bookkeeping software captures issuer regulatory status as a field, since that metadata matters for disclosure notes and auditor queries. Digital asset accounting software that treats all stablecoins as identical instruments will produce policy memos that do not reflect the actual facts.
AML and KYC Obligations: A Raised Bar for Counterparties
Federal trust bank charters come with Bank Secrecy Act obligations enforced directly by the OCC. That means Ripple's chartered entity is required to maintain a full AML programme, including customer due diligence, suspicious activity reporting, and transaction monitoring. For firms that transact with RLUSD, this has two effects.
Counterparty due diligence reviews
If your firm has an existing KYC file on Ripple as a stablecoin issuer, that file needs to be refreshed. The legal entity through which RLUSD is now issued or reserves are held has changed structurally. Risk-based due diligence requires you to document the change, assess whether it alters your counterparty risk rating, and update the file accordingly. For accounting firms managing digital asset clients, this is also a prompt to review client-level exposure to RLUSD and ensure underlying KYC documentation is current. The Senate scrutiny of stablecoin lobbying and AML obligations in recent months illustrates how quickly regulatory focus can shift to the issuer layer, not just the user layer.
Transaction monitoring parameters
RLUSD transactions processed through your systems should be reviewed against your existing typology library. A federally chartered issuer with OCC oversight is a lower inherent AML risk than an unregulated issuer, but the risk is not zero. On-chain RLUSD transfers retain the pseudonymous characteristics of any blockchain-based instrument. Firms should confirm that their transaction monitoring rules treat RLUSD as a stablecoin with a known, regulated issuer while still flagging structuring patterns, unusual velocity, or counterparties flagged on OFAC or FinCEN lists.
Tax Reporting Considerations for US Firms
The OCC charter does not alter the IRS's treatment of stablecoins as property for US federal tax purposes. Disposals of RLUSD, including exchanges for other crypto assets or for fiat, remain taxable events. What the charter does affect, in a more indirect way, is the confidence with which tax preparers can document the fair market value of RLUSD at the time of each transaction.
Fair value documentation and the issuer's role
For a stablecoin trading at or very close to its $1 peg, the fair value question is largely academic in normal conditions. But during periods of market stress, a stablecoin's trading price can deviate from par. Having a federally regulated issuer with OCC-supervised reserves provides a stronger basis for asserting that par value is the appropriate fair market value for tax purposes, backed by the regulator's own examination of reserve adequacy. Tax teams should document this reasoning explicitly in their workpapers rather than assuming a $1 valuation is self-evident.
Information reporting for corporate holders
US corporations holding RLUSD at year end will need to assess whether the asset qualifies for any specific reporting treatment under evolving IRS digital asset guidance. The Digital Asset Broker Reporting rules introduced under the Infrastructure Investment and Jobs Act continue to be phased in, and the definition of what constitutes a broker or a reportable transaction remains an active area of regulatory development. Firms using crypto accounting software should verify that their platforms are updated to reflect current IRS guidance and that RLUSD is correctly tagged for reporting purposes.
What Auditors and CFOs Should Prioritise
For audit teams with digital asset clients, the Ripple OCC approval introduces a new data point that should appear in the audit file. Specifically, engagement teams should document the charter approval date, the OCC's role as primary prudential regulator, and the implications for reserve attestation reliance. If a client's financial statements include RLUSD holdings, the auditor's assessment of the completeness and accuracy of the reserve backing now has a federal examination record to reference, in addition to any private attestation reports.
CFOs at firms with RLUSD treasury exposure should raise the charter approval at the next audit committee meeting. The structural improvement in issuer oversight is a positive development for risk management purposes, but it also creates a disclosure expectation: if your firm previously disclosed RLUSD holdings with caveats about the lack of federal oversight of the issuer, those caveats need to be updated. Stale disclosures that do not reflect a material change in the issuer's regulatory status carry their own risk.
For any firm integrating RLUSD into payment workflows or treasury operations, the charter also provides a cleaner legal analysis for board-level approval processes. A nationally chartered trust bank as the counterparty entity is a materially different approval conversation than a state-licensed money transmitter. The stablecoin accounting implications for US firms continue to evolve as federally supervised issuers become more common, and firms that build their accounting and compliance frameworks now, rather than retroactively, will be better positioned for the next round of regulatory developments.
Teams relying on crypto accounting software or digital asset accounting software to manage RLUSD positions should also verify that the issuer metadata in their systems is current, that reserve attestation documents are stored and version-controlled, and that audit trails for RLUSD transactions are complete and exportable in the format your auditors require.
Frequently Asked Questions
Does the OCC charter mean RLUSD is now FDIC-insured?
No. A national trust bank charter granted by the OCC does not carry FDIC deposit insurance. FDIC insurance applies to deposit-taking commercial banks. A trust bank operates under a different charter type and does not accept insured deposits in the traditional sense. RLUSD holders do not benefit from deposit insurance protection.
How should we classify RLUSD under US GAAP after this development?
The OCC charter strengthens the factual basis for certain classification arguments, particularly around issuer reliability and reserve verifiability, but it does not change the applicable GAAP literature. The classification depends on your firm's specific facts, the terms of the instrument, and your accounting policy choices. Review your policy memo in light of the new issuer structure and document your reasoning. If you were previously carrying RLUSD as an intangible asset under ASU 2023-08 scope analysis, that analysis should be revisited with updated facts.
Do we need to update our KYC file for Ripple as a result of this charter?
Yes. A material change in the legal and regulatory structure of a counterparty is a standard trigger for KYC file refresh under risk-based AML programmes. The OCC-chartered entity is a new or restructured legal entity with a different supervisory profile. Update the file, document the change, and reassess the risk rating.
Does the charter affect how we report RLUSD transactions to the IRS?
The IRS treats stablecoins as property regardless of the issuer's regulatory status. The charter does not change the fundamental tax treatment. However, it provides stronger support for par-value documentation in your tax workpapers and may be relevant to future IRS guidance on broker reporting obligations as the digital asset reporting rules continue to develop.
What should our crypto accounting software capture that it may not currently?
Your digital asset accounting software should be able to record issuer regulatory status as a metadata field, store links to reserve attestation reports, and generate audit-ready transaction histories for RLUSD at the lot level. If it treats all USD-pegged stablecoins as identical instruments without distinguishing issuer oversight quality, you will need either a software update or a supplementary manual process to produce compliant financial statements and auditor workpapers.
Source: Decrypt