What Banks Should Check Before Tokenizing Deposits

Banks selecting tokenized deposit infrastructure should assess a provider’s technology, regulatory controls, interoperability and capacity to handle payment activity. The review should cover how deposits are issued, transferred, redeemed and recorded in the bank’s existing systems.

Tokenized deposits are digital versions of commercial bank deposits that can move through distributed ledger technology or other programmable systems. They remain liabilities of the issuing bank and are generally intended to retain a one-to-one value with conventional deposits.

Banks should first define the activities the infrastructure will support. These may include corporate payments, cross-border settlement, securities transactions, treasury operations and transfers between financial institutions. The system should be tested against expected transaction volumes, processing speeds, settlement arrangements and operating hours.

Integration with existing banking technology should be assessed before a provider is selected. Banks should check whether the system can connect to core banking platforms, payment networks, digital-asset custody tools and compliance systems through standard interfaces. They should also establish how balances will be reconciled and how transactions will be recorded in the bank’s accounts.

The legal and regulatory requirements in every market where the deposits will be offered should be identified. Banks need to determine who controls issuance and redemption, how customer claims are protected, which entity is responsible for errors and how records will be supplied to regulators. The system should support know-your-customer checks, transaction monitoring, sanctions screening and regulatory reporting.

Security testing should cover the ledger, wallets, smart contracts, access credentials and administrative tools. Banks should ask providers how they manage cryptographic keys, unauthorized transfers, software updates, outages and recovery after an incident. Independent testing and procedures for suspending or reversing transactions should form part of the review.

The governance structure can affect how operational or legal problems are handled. Providers should identify who validates transactions, approves software changes, updates transaction rules and accesses sensitive data. Banks should also establish whether the network is operated by one company, a group of financial institutions or a broader set of participants.

Privacy requirements are relevant to corporate payments and transfers between banks. Banks should determine which transaction data other participants can see, where the data is stored and how access is restricted. They should also verify that the system meets data-retention and data-localization rules in each jurisdiction.

Before signing a long-term agreement, a bank should review the provider’s financial and operational capacity. The assessment should cover service-level commitments, pricing, technical support, exit terms and the ability to transfer records or balances to another system. Banks should test the infrastructure in a controlled environment before offering it to customers or other institutions.

Tokenized deposit systems may involve banks, payment companies, technology providers and regulators. Banks should therefore assess the wider network, including the institutions that can receive the tokens and the payment systems that can connect to the platform. A system with limited participation may have restricted use even if its underlying technology operates as designed.