A bank-controlled deposit ledger becomes preferable when the company needs continuous transfers between admitted accounts that its existing service cannot support. A transferable bank token becomes relevant when the recipient needs to receive and hold the bank claim on an approved blockchain. Each choice requires a different contract review. Programmable money for enterprises starts with the right the company acquires and the person obliged to perform.
Identify the claim before connecting the treasury system
The first design automates a payment instruction. The company remains the account holder and instructs its account bank through an agreed mandate, interface and rule. The rule determines when the bank should act. Counsel should identify the bank’s account debt separately from its obligation to execute an authorised payment.
The second design records a deposit on a bank-controlled ledger. The legal question is whether the ledger constitutes the account record or represents a balance recorded elsewhere. The terms must name the deposit debtor, account creditor and authoritative register. An employee operating a wallet may have instruction authority while the company retains the claim. If several records coexist, a priority and reconciliation clause must determine which entry changes the debt.
The third design allows a bank-issued token to move between admitted wallets. Counsel must identify how a transfer changes the person entitled to claim against the issuer. The contract may recognise each admitted transferee as the bank’s creditor, require additional registration or place an intermediary between the company and the bank. Those outcomes produce different rights. Key control alone leaves the identity of the legal claimant unresolved.
For every design, map the receiving side. A payment to another bank can extinguish or reduce the sender’s account claim and create a separate claim against the recipient’s bank. A token transfer can instead move an existing issuer claim if the applicable law and terms give it that effect. The European Banking Authority’s (EBA) December 2024 report, paragraphs 37–41 and Table 2, describes the ordinary account-based distinction and expressly acknowledges some transfers with bank consent.
Apply the EU deposit test to the actual instrument
MiCA Article 2(4)(b) excludes crypto-assets that qualify as deposits, including structured deposits. Article 3(1)(50) imports the deposit definition in Article 2(1)(3) of the Deposit Guarantee Schemes Directive (DGSD). The starting point is a credit balance arising from money left in an account or temporary situations from normal banking transactions, which a credit institution must repay under the applicable legal and contractual conditions.
The DGSD definition excludes specified balances: those whose existence is evidenced only by a financial instrument, subject to a narrow legacy savings-certificate exception; those with principal not repayable at par; and those repayable at par only under a particular guarantee or agreement. Counsel should test the claim and its evidence against those conditions before relying on the MiCA exclusion.
The date matters. Directive (EU) 2026/804, Articles 1(2), 3 and 4, entered into force on 10 May 2026. It adds wording concerning banking transactions habitually carried out by credit institutions in their business. The relevant national measures must apply from 11 May 2028. The three exclusions remain unchanged; counsel must still classify the actual account or token rights.
Transferability requires a further question: what moves? Assignment of a deposit claim can preserve its character. Capital-market negotiability can instead point towards a financial instrument. Article 4(1)(15), (17) and (44), and Annex I Section C of the second Markets in Financial Instruments Directive (MiFID II) distinguish financial instruments, money-market instruments and transferable securities. MiCA has a separate financial-instrument exclusion in Article 2(4)(a).
For an asset within MiCA’s scope that fails those exclusions, the one-official-currency stable-value test in Article 3(1)(7) can lead to e-money-token classification. Articles 48–50 then govern the relevant issuer, holder-claim and redemption regime. Apply those criteria even where the issuer is a bank and wallet access is restricted. The EBA’s 2024 comparison expressly describes an account-based deposit model and also recognises restrictions on e-money-token transfers.
Later official analysis reinforces the need to examine the claim. The EBA’s September 2026 MiCA-review response, Questions 76–78, pages 35–37, distinguishes a deposit recorded directly on a distributed ledger from a separate token representing a claim concerning a traditionally recorded balance. The latter needs closer classification. The September 2026 response of the European System of Central Banks (ESCB), section 6.3, pages 45–48, recognises contractually permitted deposit transfers and distinguishes transferability from negotiability. These consultation positions assist interpretation; their reform proposals require legislation to change the rules.
Apply this EU analysis to the issuance, offering or service within MiCA’s Union scope. The company’s EU incorporation alone cannot determine the law governing a US or Asian bank account. Deposit classification also leaves scheme protection to a separate enquiry: DGSD Articles 2, 5 and 6 distinguish deposits, eligible deposits and covered amounts. Counsel must check the booked bank, branch, holder category and applicable national scheme.
If the selected asset follows the stablecoin route, use Licentium’s stablecoin payments guide for business treasury and customer services for that separate activity and permission analysis.
Read the bank examples at their published scope
HSBC records an underlying account deposit
As at 18 November 2026, HSBC’s Tokenised Deposit Service description calls its tokens digital records of underlying cash deposits. It describes organisational wallets, one-to-one representation, and creation, transfer and destruction on a private HSBC blockchain. Participating locations and local eligibility determine access. Its network-wide currency list includes EUR, GBP, HKD, SGD and USD; the onboarding schedule must confirm the selected currency and corridor.
The status has developed. The 22 May 2025 Hong Kong introduction described a controlled live pilot and an Ant International transaction. Initial client-wallet transfers involved HKD and USD. The named bank was The Hongkong and Shanghai Banking Corporation Limited, incorporated in Hong Kong.
By 13 April 2026, HSBC announced US commercial availability for eligible corporate and institutional clients, subject to approvals, documentation and onboarding. The US product disclaimer names HSBC Bank USA, N.A. as the deposit provider. Singapore’s corporate site identifies The Hongkong and Shanghai Banking Corporation Limited, Singapore Branch. These identities distinguish the US bank from the Hong Kong corporation and its Singapore branch. The selected account agreement must confirm the actual booking and governing law.
For onboarding, obtain the clause linking wallet entries to the company’s repayable account balance. It should state who may instruct token destruction, when cash becomes available and which record prevails. If the recipient is outside the admitted network, approve a defined conversion and bank-payment route or separately documented interoperability service.
J.P. Morgan separates the deposit account from token minting
As at 18 November 2026, J.P. Morgan’s Blockchain Deposit Accounts (BDA) page describes a commercial bank-ledger service. Its FAQ distinguishes payments to and from conventional demand deposit accounts, including accounts outside J.P. Morgan, from separately minting JPM Coin. The 29 June 2026 expansion announcement lists eight supported BDA currencies. It also discloses a weekly legacy-account funding interruption. Continuous ledger operation therefore requires a separate check of the intended entry and exit hours.
There is a precise booking example. The 14 April 2025 GBP launch places those accounts at JPMorgan Chase Bank, N.A.’s London branch. That is a US bank operating through a UK branch. A different currency or product needs its own booking confirmation.
The separate JPM Coin product, ticker JPMD, is a USD deposit token available to vetted institutional counterparties. The published sequence is to fund a BDA, mint the token, transfer it between admitted wallets and redeem into USD in a BDA. Commercial institutional availability was announced on 12 November 2025, following a proof of concept. The 19 October 2026 announcement added Ethereum alongside the Base network. Both appear on the product page as at 18 November 2026.
Before approving JPM Coin, obtain the issuance and redemption terms naming the issuing bank, relevant branch, governing law and recognised holder. If an admitted transferee obtains a direct bank claim, counsel can assess that claim. If redemption belongs only to an intermediary or requires further account admission, the company must approve that dependency expressly. The product’s collateral capability needs its own legal approval before any pledge or security use.
Separate customer money from interbank settlement
The Hong Kong Monetary Authority’s (HKMA) 13 November 2025 EnsembleTX launch began controlled real-value transactions, initially using HKD real-time gross settlement. The 2 November 2026 update added round-the-clock interbank settlement in tokenised central-bank money within the pilot. Its dated annex identifies 12 participating banks and 20 industry pioneers. The central-bank asset serves settlement between participating banks. The corporate customer’s asset must still be identified through its commercial-bank relationship.
The 16 November 2026 HKMA–Swift announcement concerns further exploration of interoperability between Swift’s ledger and the Ensemble settlement layer. It names Bank of China (Hong Kong) Limited, Standard Chartered Bank (Hong Kong) Limited and The Hongkong and Shanghai Banking Corporation Limited among the participants. The intended function is multicurrency cross-border tokenised-deposit payments. For the first payment, obtain service terms confirming admission, currency and corridor.
A separate Swift initiative had already reached controlled live deployment. Swift’s 9 July 2026 announcement covered 17 banks and orchestration of obligations recorded on bank infrastructures. HSBC and UOB reported HKD transactions on 27 August 2026. Their release describes matching and netting before final settlement through existing systems. A successful transaction supports that identified deployment; customer access requires the relevant service terms.
For securities transactions, Licentium’s Pontes analysis of central-bank cash and securities finality addresses the additional settlement questions. Fund eligibility has its own context in the Hong Kong Securities and Futures Commission treatment of stablecoins and tokenised deposits.
Make the first transfer match the signed documents
Treasury and counsel should assemble one transaction schedule. Record the company, account holder, bank legal entity and branch, currency, receiving legal person, receiving bank or wallet, and the proposed amount cap. Obtain the bank’s acceptance of that exact use. A public product page establishes published functionality; admission and enforceable rights come from the applicable law and operative agreements.
Counsel should then connect the account agreement to the platform, API, token and network terms. Record their precedence, effective versions and governing law. A direct deposit claim supports the deposit analysis above. A separately issued claim, custody arrangement or transferable instrument requires its own classification before the same approval can cover it.
Treasury’s authorised signatories must approve the rule and its amendment process. Specify the triggering data, approved recipient, amount, expiry, available balance and person permitted to pause execution. Separate the technical administrator’s access from legal authority to move funds. Require additional approval for a rule change that expands the recipient, amount or purpose.
Where EU payment-services law applies, Articles 64 and 78–80 of the second Payment Services Directive (PSD2) address consent, receipt, refusal and irrevocability. Articles 38 and 61 allow specified contractual variations for non-consumer users. Counsel should check the applicable national implementation and agreed corporate terms before stating a cancellation or refund right.
Operations must establish what happens if funds are insufficient, a recipient loses eligibility or a transfer remains queued. The operating terms should identify the accepted, rejected, pending and completed states; who can cancel or retry; when funds are released; and who bears an erroneous instruction. Approve a fallback bank rail with a check that prevents paying the same obligation twice.
Finally, agree the completion evidence with the bank and the supplier. A rule-trigger log records the evaluated condition; a network confirmation records the reported network event. The payment schedule should identify the bank’s completion event under the applicable law and service terms. The supplier contract should separately state whether discharge requires available credit in its designated bank account or an effective transfer of an accepted token. Retain the corresponding bank or holder-register evidence. If these events occur at different times, the first-use approval must identify the intervening exposure and its limit.
Compare the three onboarding choices
- Payment instruction. Customer’s legal right and debtor: Company retains its claim against the named account bank and gives an authorised payment order. The account terms identify the balance record and correction rights. Permitted recipient: Recipient allowed by the account mandate, payment service and chosen rail, including another bank where supported. Cash-out route: Funds remain in the account until paid; normal withdrawal or payment terms apply. Document to obtain: Account agreement, payment mandate and programmable-rule schedule, including receipt and completion rules.
- Ledger-recorded deposit. Customer’s legal right and debtor: Company is the recognised deposit creditor of the named booked bank, if the account and ledger terms preserve that relationship. The terms select the authoritative register. Permitted recipient: Admitted accounts or wallets within the approved bank network; an external recipient needs a supported bank rail or interoperability arrangement. Cash-out route: Use the account’s agreed withdrawal or payment route; detokenise or release a separate token first where the product requires it. Document to obtain: Deposit/account terms plus ledger schedule covering record priority, recipients, cash availability and reconciliation.
- Transferable bank-issued token. Customer’s legal right and debtor: Recognised holder has the issuer claim specified by law and the issuance terms. An intermediary arrangement can change whom the company claims against. Permitted recipient: Eligible transferee at an admitted address on a supported network; another bank’s customer needs the required admission and redemption rights. Cash-out route: Eligible claimant redeems with the named issuer into the permitted account; confirm currency, timing and fees. Document to obtain: Issuance, transfer and redemption terms, holder register, custody/control agreement and recipient-admission rules.
One-page onboarding decision
Decision requested. Authorise one automated supplier payment from an existing company account, in one currency, after the approved invoice is released. The board records the account, bank entity and branch, supplier, amount cap and approval expiry. Release is conditional on the evidence below. Treasury must return for approval of recurring execution or an expanded use.
Counsel’s release conditions. The signed account and service documents identify the company’s claim, its debtor and governing law. They recognise the approved instruction and rule version, allocate authority to amend or stop it, and specify receipt, refusal, pending status and completion. The supplier’s agreed payment terms recognise the selected method and discharge event. Any token or ledger step has a documented claimant, controlling record and cash-out right.
Treasury’s release conditions. The bank accepts the company, currency, corridor and recipient. Authorised signatories approve the rule, amount cap and expiry. The funding and exit windows fit the payment deadline. The agreed fallback rail can be used after the original transfer’s status is resolved. A payment reference links the instruction, bank record and invoice.
Operations’ first-use evidence. Complete a controlled test of the rule, permissions, recipient validation, insufficient-funds response and cancellation process. For the first authorised live transfer, retain the approved rule version, instruction acknowledgement, debit and receiving-credit or holder-register evidence, and supplier reconciliation. Pause further execution until treasury confirms the result.
Choose a ledger deposit instead when the existing service cannot provide the required continuous movement between admitted accounts and the signed terms preserve an acceptable bank claim. Approve its account, authoritative ledger, entry and exit mechanism separately. Choose a transferable token instead when the recipient needs the token itself and the issuance terms establish an acceptable claim, transferable entitlement and workable redemption route for that recipient.
Defer release if the bank entity, legal claimant, admitted recipient, authoritative record, rule-changing authority or cash-out obligation remains unidentified. Also defer if the available service is only a pilot invitation or proposed corridor outside the company’s signed admission.
Return to the board for a new bank or booking branch, currency, recipient class, network, recurring rule, token-minting step, custody structure or broader amount limit. Customer funds, internal lending, foreign exchange and collateral uses require separate approval and analysis.