Standard Chartered to Hold and Trade Ripple's RLUSD in Dubai
Standard Chartered's Dubai entity has confirmed it will custody Ripple's RLUSD stablecoin and allow institutional clients to execute transactions directly against those holdings, without the stablecoin needing to leave the bank's custody infrastructure. The arrangement, reported on 12 October 2026, marks one of the clearest examples yet of a globally systemic bank integrating a regulated stablecoin into its core institutional service stack, and it lands squarely in the UAE, a jurisdiction that has moved faster than most to regulate virtual assets. For accounting firms, CFOs, and compliance teams operating in or settling through the region, the model carries immediate implications for stablecoin accounting policy, custody classification, and transaction-level AML controls.
What Standard Chartered Is Actually Doing
The key distinction in this arrangement is custody combined with in-place trading. Typically, a client wanting to use a stablecoin for settlement would transfer it from a third-party wallet or exchange, use it, then receive or send the proceeds elsewhere. Standard Chartered's Dubai model removes that step: the bank holds RLUSD on behalf of clients, and clients can transact with it while it remains within the bank's custody perimeter.
Why "in-place" trading changes the accounting picture
When a stablecoin moves between unconnected wallets, each transfer is a discrete event that most accounting frameworks treat as a disposal or at minimum a derecognition of the outgoing asset and recognition of the incoming one. An in-place trading model, where the stablecoin stays within the same custodian's infrastructure, compresses that sequence. The question for accounting teams is whether the transaction still triggers derecognition under IFRS 9 (if the asset is classified as a financial instrument) or whether the custodied balance is better characterised as a cash equivalent or a deposit-like instrument, in which case different recognition rules apply.
RLUSD is Ripple's US dollar-pegged stablecoin. It is designed to maintain a one-to-one peg with the US dollar, backed by dollar-denominated reserves. That peg matters for accounting classification: a stablecoin with a reliable, independently verified dollar peg and institutional-grade redemption rights reads differently under IAS 7 and IFRS 9 than an algorithmic stablecoin or one with opaque reserves. Firms will need to assess RLUSD's specific reserve disclosure and redemption terms before settling on a classification.
The VARA regulatory context
Standard Chartered is operating in Dubai under the oversight of the Virtual Asset Regulatory Authority, or VARA, which has published detailed rules for virtual asset service providers including custody and brokerage activities. VARA's framework requires licensed entities to hold client virtual assets in segregated accounts, maintain specific capital buffers, and implement AML and CFT controls aligned with FATF standards. The fact that a bank of Standard Chartered's standing is bringing RLUSD into a VARA-regulated custody structure gives the arrangement regulatory grounding that purely offshore or exchange-based stablecoin custody arrangements lack.
For counterparties dealing with Standard Chartered Dubai, this means the custodied RLUSD sits inside a regulated perimeter, not a self-custody or exchange-custody arrangement. That distinction matters for counterparty due diligence assessments and for firms' own internal risk classifications of their stablecoin exposures.
Stablecoin Accounting: The Classification Questions That Now Need Answers
The Standard Chartered announcement accelerates a classification debate that accounting teams at banks, corporates, and asset managers have been working through for the past two years. There is still no single authoritative IFRS or US GAAP standard specifically addressing stablecoins. The IASB's agenda decision from June 2023 concluded that certain crypto-assets, including some stablecoins, should be accounted for under IAS 38 (intangible assets) unless they meet the definition of a financial asset, in which case IFRS 9 applies. The FASB's ASU 2023-08, effective for fiscal years beginning after 15 December 2024, requires in-scope crypto assets to be measured at fair value with changes recognised in net income, but that standard applies to assets held for own account, not necessarily to custodied client assets.
How custodied stablecoins sit on the balance sheet
If Standard Chartered holds RLUSD as a custodian, the stablecoin does not sit on the bank's own balance sheet as an asset: the bank holds legal title or a contractual right on behalf of the client, and the client retains the economic exposure. For the bank, the custody obligation is an off-balance-sheet fiduciary arrangement, disclosed in notes but not consolidated into assets and liabilities in the conventional sense, subject to the specific terms of the custody agreement and applicable local GAAP or IFRS guidance.
For the client, however, the custodied RLUSD remains on their balance sheet. The client must classify it: as a financial asset under IFRS 9 if RLUSD qualifies as a contractual right to receive cash; as an intangible asset under IAS 38 if it does not; or potentially as a cash equivalent under IAS 7 if it is readily convertible to a known amount of cash and subject to an insignificant risk of changes in value. That last classification is the most favourable from a treasury management perspective, but it requires robust evidence of convertibility and peg stability.
Transaction recognition when the asset stays in place
The in-place trading feature creates a specific recognition challenge. If a client uses custodied RLUSD to pay a counterparty, and that counterparty is also a Standard Chartered Dubai client whose RLUSD balance is simply credited within the same custody infrastructure, the question arises: has the paying client disposed of an asset, or has the bank merely updated internal ledger entries? The answer depends on whether legal and beneficial ownership has transferred, which in turn depends on the custody agreement's terms. Accounting teams should obtain a copy of the custody agreement and map each transaction type to a recognition event before any volume runs through the structure.
AML and Compliance Implications for Firms Using the Structure
Stablecoin custody inside a VARA-licensed bank does not remove a firm's own AML obligations; it layers them. Standard Chartered will apply its own customer due diligence, transaction monitoring, and suspicious activity reporting processes. But the firm that is the bank's client must still conduct its own CDD on the counterparties it transacts with using the custodied RLUSD, and it must ensure its own transaction monitoring systems capture the activity.
Travel Rule considerations
The FATF Travel Rule requires that originator and beneficiary information travel with virtual asset transfers above certain thresholds. If both sides of a transaction are within Standard Chartered's custody perimeter, the bank is both the originating and receiving virtual asset service provider, which simplifies Travel Rule compliance but does not eliminate it: the bank still needs to capture and retain the required data. For firms whose counterparties are outside the bank's perimeter, standard Travel Rule mechanics apply, and the firm's compliance team should confirm how Standard Chartered surfaces that data to clients for their own records.
For a broader framework on what banks and financial institutions owe under stablecoin AML rules, our analysis of stablecoin AML obligations for banks and financial institutions sets out the key FATF-aligned requirements in detail.
What This Means for CFOs and Finance Teams in the UAE and Beyond
The Standard Chartered Dubai model is not an isolated experiment. It signals that institutional stablecoin infrastructure in the UAE is maturing quickly, and that firms which have deferred stablecoin accounting policy decisions may find themselves caught short when a counterparty or treasury counterpart expects them to transact in this way.
Policy gaps to close before transacting
Finance teams should work through at least three policy areas before using a structure like this. First, asset classification: decide in advance whether RLUSD will be classified as a financial asset, intangible, or cash equivalent, document the rationale, and align it with the firm's existing crypto accounting policy. Second, derecognition triggers: define precisely which events cause the firm to derecognise the stablecoin balance, whether that is a change in legal ownership, a settlement instruction, or something else, and ensure the definition is consistent with the custody agreement. Third, disclosure: IFRS 7 and IAS 1 both require disclosure of significant accounting judgements and financial instrument risks; a custodied stablecoin balance used for settlement is a financial instrument risk that needs to be disclosed clearly.
The regulatory uncertainty that still surrounds stablecoin classification in some jurisdictions is explored in depth in our piece on how the CLARITY Act's failure shapes stablecoin accounting treatment, which covers the agency-rule landscape that now fills the gap in the US and its ripple effects on global firms.
Practical steps for accounting firms advising UAE-based clients
Accounting firms working with UAE corporates or financial institutions should treat this development as a prompt to review client exposure to custodied stablecoin arrangements. Key actions include confirming whether any client already holds or plans to hold stablecoins through a regulated bank custodian in the UAE; reviewing whether the client's accounting policy covers custodied digital assets as distinct from self-custodied ones; checking whether the client's ERP or digital asset accounting software captures the custody layer and not just the on-chain transaction; and assessing whether the client's auditors have agreed on the balance sheet classification for any stablecoin balances that will appear in the next set of financial statements.
Robust digital asset accounting software that can ingest custody account data feeds, map transactions to recognition events, and produce audit-ready schedules will be essential as these arrangements scale. Manual reconciliation of custodied stablecoin balances against bank statements is workable at low volume but becomes a material audit risk as transaction counts grow.
The Broader Market Structure Signal
Standard Chartered's move in Dubai follows a pattern visible across several major jurisdictions: banks are no longer treating stablecoins as peripheral or experimental. They are building custody, settlement, and client-facing products around regulated stablecoins, and they are doing so inside regulated perimeters where the rules, however evolving, provide a clearer basis for operation than exchange or DeFi-adjacent structures.
For the stablecoin market specifically, bank-grade custody of RLUSD in Dubai alongside existing USD Coin and other stablecoin custody offerings from various institutions means corporate treasurers and fund managers in the region will face genuine multi-stablecoin choice in the near term. That choice introduces a new layer of accounting complexity: firms may hold balances in more than one stablecoin, each with different reserve structures, redemption terms, and potentially different accounting classifications. A consistent, documented classification framework applied at the firm level, rather than asset by asset, will become a governance expectation rather than a nice-to-have.
Frequently Asked Questions
How should a corporate client classify custodied RLUSD on its balance sheet?
The classification depends on RLUSD's contractual terms. If the stablecoin gives the holder a contractual right to receive a fixed amount of US dollars on demand, it may qualify as a financial asset under IFRS 9 and potentially as a cash equivalent under IAS 7. If those conditions are not clearly met, IAS 38 treatment as an intangible asset is the fallback. Firms should obtain the stablecoin's reserve disclosure documents and redemption terms and apply their classification criteria consistently before any balances appear in financial statements.
Does Standard Chartered's custody remove the client's AML obligations?
No. The bank applies its own AML and CFT controls as a VARA-licensed custodian, but the client retains independent obligations to conduct due diligence on its own counterparties, monitor transactions, and file suspicious activity reports where required. Using a regulated bank custodian reduces counterparty risk on the custody side but does not substitute for the client's own compliance programme.
What triggers derecognition when stablecoins are traded in-place?
Derecognition under IFRS 9 occurs when the contractual rights to cash flows from the asset expire or the asset is transferred and substantially all risks and rewards pass to another party. In an in-place trading model, the key question is whether a completed transaction instruction constitutes a transfer of legal and beneficial ownership. This depends on the custody agreement's terms. Firms should map each transaction type to a specific derecognition event in their accounting policy before go-live.
How does VARA's framework affect counterparty due diligence assessments?
VARA requires licensed entities to maintain segregated client assets, apply FATF-aligned AML controls, and hold appropriate capital. For counterparties assessing Standard Chartered Dubai as a custodian, VARA licensing provides a regulatory baseline that supports a lower inherent risk classification compared with unlicensed or offshore custodians. However, firms should still obtain and review the bank's VARA licensing documentation and any relevant regulatory disclosures as part of their vendor due diligence process.
Do firms need to update their crypto accounting software to handle custodied stablecoin balances?
Most firms will need to verify that their existing digital asset accounting software can ingest custody account data directly from the custodian's reporting feeds, rather than relying solely on on-chain transaction records. Custodied assets may not always generate on-chain events for every internal settlement, so the software needs to reconcile off-chain custody ledger entries against the firm's own general ledger. Firms should confirm this capability with their software provider before the first transaction settles.
Source: Decrypt