A payments company preparing to issue digital tokens discovers that calling the instrument a "stablecoin" does not settle whether it is a tokenized deposit, an e-money token or something else entirely. The legal distinction turns on the issuer's identity, the redemption promise and the regime under which the token sits – and each classification carries different capital, safeguarding and licensing consequences. For a bank offering tokenized deposits, deposit-insurance rules apply and the instrument remains on-balance-sheet; for a non-bank issuer of payment stablecoins, segregated reserves and e-money or payment-institution authorisation are the norm. The two instruments look identical to the user but diverge sharply in regulatory treatment.
This page maps the legal boundary between tokenized deposits and payment stablecoins, explains how classification affects issuer duties and user protections, and sets out the decision criteria for a business choosing between the two models. Every figure, threshold and effective date referenced below is drawn from the Verified Facts Registry or stated qualitatively where final rules remain pending.
What is a tokenized deposit?
A tokenized deposit is a claim against a regulated deposit-taking institution – typically a licensed bank – represented as a digital token on a distributed ledger. The holder's position remains a deposit in law: the bank owes the principal amount, deposit-insurance schemes apply where available, and the liability sits on the bank's balance sheet. The token is the medium of transfer, not a separate asset class. Regulatory treatment follows deposit law, not securities or payment-token frameworks, and the issuer must hold a banking licence or equivalent deposit-taking authorisation in the relevant jurisdiction.
Under this model the token is a record of a contractual claim. When a corporate treasurer transfers a tokenized deposit to a supplier, the transaction extinguishes the transferor's deposit claim and creates a new one for the recipient – both claims remain against the same bank. Settlement is instantaneous on-chain, but the economic substance is a deposit transfer, not the creation of a new instrument. The regime governing the bank – capital adequacy, liquidity coverage, resolution planning – applies in full, and regulators in flagship jurisdictions generally treat tokenized deposits as an innovation in payment rails rather than a new product category.
In practice, tokenized deposits are issued by banks that already hold client fiat on deposit and wish to offer programmable, blockchain-based settlement without moving liability off-balance-sheet. The model suits corporate treasury use cases where counterparties trust the issuing bank and value instant settlement over decentralisation. Deposit insurance, where it exists, typically covers the tokenized form to the same limits as traditional deposits, though the precise scope depends on how the relevant insurance scheme defines "deposit" and whether it extends to digital representations. Operators we advise routinely verify coverage with the national deposit-insurance authority before launch, because a gap in insurance materially affects risk disclosure to clients.
What is a payment stablecoin?
A payment stablecoin is a digital token issued by a non-bank entity, redeemable at par into fiat currency and backed by segregated reserves held with a bank or custodian. The stablecoin is not a deposit claim against the issuer; it is a bearer instrument or a contractual right to redemption, depending on the legal structure. Regulatory treatment falls under e-money frameworks (such as the e-money token regime within MiCA in the European Union) or payment-institution rules, and the issuer must obtain a payment-services or e-money licence rather than a banking licence. The reserves backing the stablecoin are held off the issuer's balance sheet in segregated accounts, and no deposit insurance attaches to the token holder's position.
The distinction from a deposit is critical. A payment stablecoin holder has a claim to redemption, not a deposit relationship, and the issuer's insolvency does not trigger deposit-guarantee schemes. Instead, safeguarding rules require the issuer to maintain reserves equal to the outstanding token supply, typically in high-quality liquid assets – central-bank reserves, short-dated government securities or overnight deposits with a credit institution. The reserve composition and the frequency of attestation are set by the relevant payment or e-money regime, and any shortfall is a regulatory breach that can result in licence suspension.
Payment stablecoins issued under MiCA as e-money tokens must comply with ESMA's technical standards on reserve assets, redemption at par and the prohibition on interest. Issuers outside the European Union face varying reserve and redemption rules depending on the jurisdiction: Singapore requires a Major Payment Institution licence for stablecoin issuance above a defined transaction threshold, Hong Kong's regime is emerging under consultation, and the United Kingdom applies e-money rules where the token qualifies as e-money or proposes a separate stablecoin framework. In each case the substance is the same – the issuer is not a bank, the token is not a deposit, and safeguarding replaces deposit insurance as the primary protection mechanism.
How regulators draw the line
Regulators distinguish between tokenized deposits and payment stablecoins on three criteria: the issuer's authorisation, the nature of the holder's claim and the treatment of reserves. If the issuer holds a banking licence and the token represents a deposit liability, the instrument is a tokenized deposit and deposit law applies. If the issuer is a payment institution or e-money institution and the token is a redeemable bearer instrument backed by segregated reserves, the instrument is a payment stablecoin and the payment or e-money regime applies. The label the issuer chooses is irrelevant; regulators look to the substance of the arrangement.
The question becomes acute when a bank partners with a non-bank issuer. If the bank issues the token and retains the liability, the arrangement is a tokenized deposit regardless of the partner's role in distribution. If the non-bank issues the token and holds reserves at the bank, the token is a payment stablecoin and the non-bank requires the payment or e-money licence. A mis-step here – issuing a stablecoin without the correct licence, or treating a deposit as a non-deposit instrument – converts a product launch into an unregistered offering and exposes both parties to enforcement.
In the MiCA context, the framework explicitly separates e-money tokens from other crypto-assets and from deposits. An EMT must be issued by a credit institution authorised under the Capital Requirements Regulation or by an e-money institution authorised under the E-Money Directive, and the holder's claim is a claim for redemption, not a deposit. A bank issuing a tokenized deposit, by contrast, does not issue an EMT; it issues a deposit, and MiCA does not govern the instrument. National banking law and the relevant deposit-insurance scheme do. The boundary is clear in law but requires careful drafting of the token's terms and the issuer's disclosures to avoid classification disputes.
Capital and safeguarding obligations
A bank issuing tokenized deposits must meet the capital adequacy requirements of the banking regime – typically a risk-weighted capital ratio under Basel III or an equivalent framework. The tokenized deposit is a liability like any other deposit, and the capital the bank must hold depends on the balance-sheet composition and the liquidity profile of the deposits. Deposit-insurance levies apply where the jurisdiction operates a deposit-insurance scheme, and the bank must contribute to the fund based on its covered deposits, including tokenized deposits if they fall within the scheme's definition.
A non-bank issuer of payment stablecoins faces a different set of obligations. Under the e-money regime in the European Union, an e-money institution must maintain own funds equal to the higher of a defined base amount or a percentage of average outstanding e-money, and reserves backing the e-money must be held in segregated accounts, invested only in secure, low-risk assets. The issuer cannot lend the reserves or use them for proprietary trading, and any interest earned on the reserves belongs to the issuer, not the token holders. The safeguarding rules are strict: a shortfall in reserves is an immediate breach, and the regulator may suspend new issuance or freeze redemptions until the position is corrected.
In practice, the capital cost of issuing tokenized deposits as a bank is higher than the capital cost of issuing payment stablecoins as an e-money institution, because banks face full prudential capital requirements and resolution-planning obligations. A payment stablecoin issuer avoids those costs but must maintain one-to-one backing and demonstrate to the regulator that the reserves are segregated, liquid and redeemable on demand. The trade-off is between on-balance-sheet deposit-taking with deposit insurance and off-balance-sheet issuance with safeguarding but no insurance. Which model fits depends on the issuer's existing authorisation, the target user base and the commercial appetite for balance-sheet exposure.
Redemption rights and user protection
The holder of a tokenized deposit has the same redemption and withdrawal rights as a holder of a traditional deposit. If the bank becomes insolvent, the deposit-insurance scheme – where it exists – covers the deposit up to the relevant limit, and the holder ranks as a senior creditor in the bank's insolvency. The token itself may be frozen or delisted from the ledger by the bank or by court order, but the underlying deposit claim survives, and the holder retains the protection of deposit law.
The holder of a payment stablecoin has a redemption claim against the issuer, governed by the token's terms and the applicable payment or e-money framework. The holder is not a depositor and receives no deposit insurance. If the issuer becomes insolvent, the holder's claim is to the segregated reserves, and the reserves are held in trust or under a similar arrangement that places them outside the issuer's insolvency estate. The effectiveness of this protection depends on the quality of the segregation and the legal enforceability of the trust or custody arrangement in the relevant jurisdiction. A poorly drafted safeguarding arrangement – where the reserves are not clearly ring-fenced – can leave stablecoin holders ranking as unsecured creditors, a position materially worse than that of a depositor.
Regulators in flagship payment-stablecoin jurisdictions require the issuer to provide clear disclosure of the redemption mechanism, the reserve composition and the absence of deposit insurance. The disclosure must appear in the whitepaper or equivalent offering document and in the user terms. A failure to disclose that the token is not a deposit and carries no deposit insurance is a mis-selling risk and a regulatory breach. Operators we advise pressure-test their disclosure language with local counsel in each distribution jurisdiction before launch, because the classification boundary is a common point of regulatory challenge.
Licensing pathways for issuers
A business that wishes to issue tokenized deposits must obtain a banking licence or partner with a licensed bank willing to issue the tokens on its balance sheet. Obtaining a banking licence is a multi-year, capital-intensive process in every major jurisdiction, and the regulatory expectations – governance, risk management, capital adequacy, liquidity, resolution planning – are those of a full-service bank, not a payments fintech. For most crypto-native businesses, this path is not viable, and the alternative is to partner with a bank that will issue tokenized deposits on behalf of clients or distribute the bank's own tokenized deposits through the business's platform.
A business that wishes to issue payment stablecoins requires an e-money licence, a payment-institution licence or an equivalent authorisation depending on the jurisdiction. In the European Union, an EMT issuer must be a credit institution or an e-money institution authorised under the E-Money Directive, and the issuer must comply with MiCA's technical standards for reserve assets, redemption and whitepaper disclosure. Outside the European Union, the licensing pathway varies: Singapore requires a Major Payment Institution licence for stablecoin issuance above a transaction threshold, the United Kingdom applies e-money rules where applicable, and the United Arab Emirates requires a payment-token licence under VARA or the ADGM framework depending on the emirate. The capital and timeline for an e-money or payment-institution licence are lower than for a banking licence, but the application still requires a full compliance framework, senior management vetting and a detailed reserve-management policy.
A common mistake is to assume that partnering with a bank for reserve custody is equivalent to obtaining a payment licence. It is not. The issuer of the stablecoin is the regulated entity and must hold the payment or e-money licence; the bank holding the reserves is a service provider, not the issuer. If the business issues tokens without the required licence on the theory that "the reserves are with a bank," the issuance is unlicensed payment-service activity or e-money issuance, and the business faces regulatory action in every jurisdiction where it distributes the token. The licensing obligation sits with the issuer, and custody of reserves does not transfer that obligation to the custodian.
For a scoped assessment of the licence, reserve structure and disclosure requirements for a tokenized deposit or payment stablecoin issuance, contact OBOLUS at info@oboluslaw.com.
Cross-border distribution and passporting
The cross-border dimension is where tokenized deposits and payment stablecoins diverge most sharply in practice. A bank issuing tokenized deposits operates under its banking licence, and cross-border distribution of the tokens depends on whether the bank may accept deposits from customers in the target jurisdiction. In the European Union, a bank authorised in one member state may passport deposit-taking across the EU and EEA, and tokenized deposits issued by that bank benefit from the same passport. Outside the European Union, a bank wishing to offer tokenized deposits in a foreign jurisdiction typically requires a branch or subsidiary licence in that jurisdiction, or it must limit distribution to wholesale clients under an exemption for professional counterparties.
A payment stablecoin issuer authorised in one jurisdiction faces a different analysis. Under MiCA, an e-money institution authorised to issue EMTs in one member state may passport that authorisation across the European Union, and the stablecoin may be marketed and redeemed throughout the EU without additional licences. Outside the European Union, no equivalent global passport exists, and the issuer must assess each target jurisdiction's payment-services or e-money regime separately. An EMT authorised under MiCA does not grant rights in the United Kingdom, Singapore, Hong Kong, the UAE or the United States, and distribution into those jurisdictions requires either a local payment licence or structuring the distribution as a wholesale offering exempt from retail payment rules.
The practical consequence is that a bank issuing tokenized deposits faces higher barriers to cross-border retail distribution than a payment stablecoin issuer within a passporting regime like MiCA, but the bank benefits from deposit insurance and an established banking relationship with users. A payment stablecoin issuer can distribute more widely under a single licence where passporting applies, but must navigate a patchwork of payment and e-money regimes outside that zone and cannot offer deposit insurance. Businesses launching either instrument must map the licensing requirement and the user-protection disclosure for each material distribution jurisdiction before going live, because the cost of a mis-step – operating without a licence, or providing misleading redemption assurances – is enforcement and reputational damage that can shut down the project.
Interoperability with traditional payments
Tokenized deposits sit within the traditional banking system by design. A holder can redeem a tokenized deposit into a fiat account at the issuing bank without crossing into a separate payment rail, and the bank's existing correspondent relationships, SWIFT connectivity and domestic payment-system access apply to the fiat leg of any conversion. For corporate users, this means tokenized deposits can be used alongside traditional payments infrastructure – paying suppliers in tokenized deposits on-chain and receiving fiat into the same bank account – without opening accounts at a separate payment institution or navigating cross-border payment rules.
Payment stablecoins, by contrast, exist outside the traditional deposit system and require a bridge to fiat rails at the point of redemption. A user redeeming a stablecoin must instruct the issuer to convert the token into a fiat payment, and that payment is processed through the issuer's bank account, subject to the issuer's relationship with its banking provider. If the issuer's bank closes the account or restricts outbound payments – a risk in some jurisdictions where banks remain cautious about crypto-related flows – stablecoin redemptions can be delayed or suspended, and users are left holding a token they cannot convert into usable fiat.
In practice, payment stablecoins are more portable across blockchains and exchanges than tokenized deposits, because the stablecoin is a bearer instrument and can be transferred peer-to-peer without involving the issuer or a bank. Tokenized deposits require the issuing bank to process each transfer, and the bank may impose know-your-customer or anti-money-laundering checks at the point of transfer that are unnecessary for stablecoins moving between non-custodial wallets. The trade-off is between the deep integration with fiat banking that tokenized deposits offer and the peer-to-peer portability and programmability that payment stablecoins deliver. Which matters more depends on the use case: corporate treasury and payroll favour tokenized deposits for their banking integration; decentralised-finance protocols and cross-border remittances favour payment stablecoins for their portability.
Which model suits which business
A licensed bank with an existing deposit base and a corporate client roster will find tokenized deposits the natural extension of its service offering. The bank already holds the clients' fiat on deposit, the regulatory framework is familiar, and issuing tokenized deposits requires no new licence – only technical infrastructure to represent deposits on a blockchain and manage on-chain settlement. The model works particularly well for banks serving multinational corporates that need instant cross-border settlement between subsidiaries, because the tokenized deposit allows intra-group transfers to settle in seconds rather than days while keeping all balances on the bank's books and within the deposit-insurance safety net.
A fintech or crypto-native business without a banking licence will find payment stablecoins the only viable path, because obtaining a banking licence to issue deposits is neither commercially realistic nor necessary for the target use case. A payment stablecoin backed by segregated reserves and issued under an e-money or payment-institution licence allows the business to offer programmable money without taking on the balance-sheet and prudential obligations of a bank. The model suits businesses focused on retail payments, remittances, decentralised-finance liquidity or exchange settlement, where users value instant, low-cost transfers and do not require deposit insurance or a traditional banking relationship.
The capital and operational cost of each model differ sharply. Issuing tokenized deposits as a bank means absorbing the deposits onto the balance sheet, holding regulatory capital against them, and contributing to deposit-insurance schemes. Issuing payment stablecoins as an e-money institution means holding one-to-one reserves in segregated accounts and meeting the lower capital requirements of the payment-institution regime, but also means forgoing deposit insurance and managing the safeguarding and attestation obligations that payment regulators impose. A business that already holds a banking licence will favour tokenized deposits; a business building a payments product from scratch will favour stablecoins unless it intends to become a bank.
A hybrid model – where a bank issues tokenized deposits and a non-bank partner distributes them – can combine the deposit-insurance benefit with wider distribution, but the regulatory analysis is complex. The bank remains the issuer and the deposit-taker, and the partner acts as a distributor or agent. The partner does not require a payment licence for distribution if it never holds client funds and the deposit relationship is always between the client and the bank, but the partner must comply with any intermediary or tied-agent registration requirements in the relevant jurisdiction. Mis-structuring the relationship so that the partner appears to be the issuer or holds client funds without authorisation is a licence breach, and both parties face enforcement risk. Operators we work with document the allocation of roles – who is the issuer, who holds the funds, who manages redemptions – in a written agreement reviewed by counsel in each distribution jurisdiction before launch.
If the structural and licensing picture above describes your position, write to OBOLUS at info@oboluslaw.com to map the applicable framework and the risk points before you commit to a model.
AML and Travel Rule obligations
Both tokenized deposits and payment stablecoins fall within the anti-money-laundering perimeter, and the issuer must apply customer due diligence, transaction monitoring and suspicious-activity reporting as required by the Financial Action Task Force Recommendations and the implementing regime in the relevant jurisdiction. The Travel Rule – the obligation to pass originator and beneficiary information with a transfer – applies to both instruments where the transfer meets the relevant threshold, though the mechanism for compliance differs.
A bank issuing tokenized deposits applies the Travel Rule through its existing correspondent-banking and payment-messaging infrastructure. When a tokenized deposit moves on-chain between two users at the same bank, the bank already holds KYC data for both parties, and Travel Rule compliance is straightforward. When the deposit moves to a user at a different institution – for example, redemption into a fiat account at another bank – the issuing bank applies the same Travel Rule process it uses for traditional wire transfers, passing originator and beneficiary data through SWIFT or an equivalent messaging layer. The blockchain transfer is visible on the ledger, but the compliance obligation is discharged off-chain through the bank's existing procedures.
A payment stablecoin issuer must build a Travel Rule compliance mechanism that works with on-chain transfers, because the stablecoin can move peer-to-peer without the issuer's involvement at the point of transfer. In practice, this means the issuer relies on virtual-asset service providers – exchanges, wallets, custodians – to exchange originator and beneficiary data using a Travel Rule solution such as those provided by the compliance technology firms active in the crypto sector. The issuer's direct obligation is to apply KYC at the point of issuance and redemption, and to monitor on-chain activity for suspicious patterns, but the issuer cannot enforce Travel Rule compliance on secondary transfers unless the stablecoin is programmed with transfer restrictions that require the sender to prove compliance before the transaction is executed.
The regulatory expectation in flagship jurisdictions is that both models must achieve the same compliance outcome – originator and beneficiary information passing with the transfer where required – but the path to that outcome differs because the instruments sit in different parts of the financial system. A tokenized deposit leverages the bank's existing AML infrastructure; a payment stablecoin requires purpose-built compliance tools for on-chain monitoring and Travel Rule data exchange. Businesses launching either instrument must demonstrate to the regulator that they have a credible plan for meeting Travel Rule obligations in the jurisdictions where they operate, and that demonstration is a standard component of the licence application or the regulatory approval process for the product.
A common assumption is that calling a token "backed by fiat" makes it a stablecoin
Businesses entering this space often believe that marketing a token as "fully backed" or "fiat-collateralised" settles the classification and removes any deposit-regulation concern. It does not. Regulators assess the instrument's legal substance, not its label. If the issuer is a bank, the holder has a deposit claim against the bank, and the token represents that claim, the instrument is a deposit in law regardless of how the marketing material describes it. Conversely, if the issuer is a payment institution, the reserves are segregated, and the holder's claim is to redemption rather than a deposit balance, the instrument is a payment stablecoin even if the issuer uses language associated with deposits.
The distinction matters because deposit regulation and payment-institution regulation impose materially different obligations on the issuer and confer different protections on the holder. A mis-classification – launching a tokenized deposit as if it were a payment stablecoin, or vice versa – results in operating under the wrong regulatory framework, and the enforcement consequence can include suspension of issuance, a requirement to refund holders, and penalties for the unlicensed activity. In our cross-border practice, classification analysis is the first step in any token-issuance matter, conducted before drafting the whitepaper and before engaging with the regulator, because the choice of framework determines the licence requirement, the capital obligation and the entire compliance architecture of the product.
Related at OBOLUS
- Banking, Payments & EMI Onboarding for Digital-Asset Businesses – securing banking and payment rails for crypto-native operators across licensing jurisdictions
- MiCA White Paper: Technical Standards, Templates and Notification – drafting and filing the whitepaper for crypto-asset and e-money token issuance under MiCA
- Corporate Bank Account Opening in Mauritius – banking options for digital-asset businesses in a jurisdiction open to crypto-related accounts
FAQ
Can a crypto firm access banking under this regime?
A crypto firm operating as a virtual-asset service provider or exchange typically cannot issue tokenized deposits, because it does not hold a banking licence. The firm may, however, issue payment stablecoins under an e-money or payment-institution licence, or it may partner with a licensed bank to distribute the bank's tokenized deposits. Access to banking for the firm's own operational accounts – holding client funds, processing redemptions – depends on the firm's licensing status and the bank's risk appetite for crypto-related businesses, and varies significantly by jurisdiction.
What safeguarding applies to client funds?
For tokenized deposits, safeguarding takes the form of deposit insurance where the jurisdiction operates a deposit-guarantee scheme; the deposit is a liability of the bank, and the holder is protected up to the scheme's coverage limit. For payment stablecoins, safeguarding means the issuer must hold reserves equal to the outstanding token supply in segregated accounts, invested in secure, low-risk assets. The reserves are held off the issuer's balance sheet, and the holder's protection depends on the enforceability of the segregation arrangement. Payment stablecoin holders do not receive deposit insurance.
Which payment licence is required?
Issuing tokenized deposits requires a banking licence or equivalent deposit-taking authorisation; no separate payment licence is required because the activity is deposit-taking, not payment-service provision. Issuing payment stablecoins requires an e-money licence or a payment-institution licence, depending on the jurisdiction and the nature of the token. In the European Union under MiCA, e-money tokens must be issued by a credit institution or an e-money institution; in other jurisdictions, the applicable licence may be a major payment institution licence, a stored-value facility licence or a virtual-asset payment-token licence, depending on local law.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across more than seventy jurisdictions, on disputes and on-chain asset recovery across twenty-five forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We assess classification against the substance of rights conferred by the instrument, not the marketing label, and we map the licence, safeguarding and cross-border disclosure requirements before the whitepaper is drafted. To discuss your token-issuance or payment-rails structure, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – advising on payment-token classification, e-money and payment-institution licensing, and the regulatory boundary between deposits and digital bearer instruments across flagship jurisdictions.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.