Tokenized deposits on more networks: the controls treasury now needs
JPM Coin reached Ethereum and Jack Henry brought tokenized deposits to community banks. What changes for treasury controls when bank money runs 24/7 on many networks.
On 19 October 2026 Kinexys by J.P. Morgan brought JPM Coin, its US dollar deposit token, to Ethereum, a base-layer (Layer 1) public blockchain, for its institutional clients. The token, launched in November 2025, was until now available on Base, a network built on top of Ethereum. Three days earlier, core banking provider Jack Henry announced it will integrate with Google Cloud Universal Ledger (GCUL) so that the community banks and credit unions it serves can offer tokenized deposits.
A tokenized deposit is an ordinary commercial bank deposit recorded on a distributed ledger. It is not a stablecoin: it is a claim on the issuing bank, held inside that bank's regulated balance sheet. What the past fortnight shows is that these tokens are leaving single-bank pilots and arriving on several networks at once, for large and small institutions alike. That changes some basic treasury controls.
Tokenized deposits are now on several networks, not one
The JPMorgan move is the clearest example. Its JPM Coin product page now describes the token as issued on both Ethereum and Base, and CoinDesk reports that the bank flagged in January a plan to take the token to the Canton Network as well. Emma Landriault, global head of Kinexys Labs, described the aim in the bank's announcement as giving clients "multi-chain optionality for moving wholesale money."
Other announcements from the same period point the same way:
- Community banks. Jack Henry says it will be the first core technology provider to integrate with GCUL, which it describes as a managed distributed ledger with programmable, 24/7 settlement.
- Loan payments between banks. On 19 October Participate reported a loan participation payment between two Texas banks, Vantage Bank and Rio Bank, settled in tokenized deposits over the Hazel Network in under three minutes, with loan balances and notices updated as the money moved.
- A bank token for wider use. On 15 October VersaBank said it had started the commercial phase of its US tokenized deposit, VUSD, and plans to list it on digital asset exchanges.
- Cross-border treasury. On 7 October OCBC launched a tokenized deposit solution with Ant International so that Ant can move Singapore dollar and US dollar liquidity between its entities in Singapore and Malaysia around the clock.
The CoinDesk report also notes that JPMorgan, Citi, Bank of America and Wells Fargo, with more than a dozen other banks, plan a shared network for tokenized deposits. A treasury team could plausibly hold tokens from more than one bank, on more than one network, within a year or two.
Same money, different addresses
On a public network, a token is identified by the address of its smart contract, not by its name. JPMorgan makes the point directly: its product page warns that tokens with the same or a similar name at different contract addresses are not affiliated with the bank. Once one bank's deposit token lives on two networks, there are two legitimate contract addresses for the same money, and any number of lookalikes.
For a payment operation this is a reference data problem, much like maintaining standard settlement instructions. Someone has to own the list of approved token contracts per network, change it under dual control, and make sure every payment and every incoming receipt is checked against it.
Always on, except when it is not
The appeal is continuous settlement. The JPM Coin page says transfers on the network complete 24/7/365, but its footnote adds that moving funds between traditional demand deposit accounts and its blockchain deposit accounts has a three-hour downtime every Saturday, currently 3-6 p.m. Eastern time, with an enhancement under development. In other words, the token moves at any hour, but converting back into the account your other systems see does not always.
That matters for liquidity planning. A sweep or intra-group transfer that settles at 2 a.m. on a Sunday is useful only if the institution is also ready to approve, monitor and account for it at 2 a.m. on a Sunday.
What it means for treasury and payment operations
Six questions worth answering before tokenized deposits reach your payment flows:
- Which tokens and which networks are allowed? Write down the specific issuer, token and network combinations you accept, by contract address, and who may change that list.
- Who approves out of hours? If money can move at any time, approval chains, limits and escalation need to work at any time too, or out-of-hours payments need tighter limits.
- Where is the reconciliation boundary? JPMorgan says that because payment and settlement sit on a shared ledger, reconciliation happens automatically. That is true on the ledger. The Hazel Network payment still needed a dedicated layer: Participate's release says Custodia handled automated reconciliation monitoring between the deposit ledger and the blockchain. Your general ledger and treasury system remain a third record that must agree with both.
- How are counterparties vetted? JPM Coin is restricted to vetted, approved counterparties, according to the product page. Tokens listed on exchanges, as VersaBank plans, may reach a wider set of holders. Either way, the institution still needs its own screening of every wallet it pays or receives from.
- What happens if the issuer freezes tokens? VersaBank says its technology can "freeze, seize and burn" tokens that regulators determine are used for illegal purposes. Plan how a frozen balance is detected, reported and accounted for.
- Can you show the full trail later? For each token payment, can you link the on-chain transaction to the internal instruction, the approvals and the rule that allowed it?
The legal treatment of tokenized deposits, stablecoins and the networks they run on differs by jurisdiction and is still developing. Nothing here is legal advice; each institution must check its own obligations with its advisers and supervisors.
Where IXFXN fits
IXFXN is an approval layer that sits in front of money movement, whatever the rail. Rules limit the asset, provider (rail), recipient, jurisdictions and maximum amount; a payment outside a rule is stopped with a reason code, and larger amounts need more approvers. Rules are versioned, and every decision can be replayed against the version in force at the time, which is the audit trail question above. Its AI proposes and explains payments but never sends money; the payment engine acts only with a permit for one exact payment, which works once and expires within 60 seconds.
To be clear about where it stands: tokenized deposits, bank transfers and USD Coin (USDC) run against a built-in simulation only, recipient and wallet screening is simulated, and there are no customers or pilots yet.
Sources
- J.P. Morgan: JPM Coin goes live on Ethereum, extending institutional finance reach on second public blockchain
- J.P. Morgan Kinexys: JPM Coin product page
- CoinDesk: JPMorgan brings JPM Coin, representing dollar deposits, to Ethereum
- Jack Henry: Jack Henry Expands Collaboration with Google Cloud to Deliver Tokenized Deposits for Banks and Credit Unions
- EIN Presswire: Participate and Hazel Complete World's First Loan Participation or Syndication Payment Using Tokenized Deposits
- VersaBank: VersaBank Initiates Commercial Phase of Tokenized Deposit Program in the United States
- OCBC: OCBC launches tokenised deposit solution with Ant International for treasury management between Singapore and Malaysia