21.05.2026
Stablecoin Payment Operations for CFOs: How to Manage USDT Payments
Read article
A tokenized bank deposit and a dollar stablecoin can look almost identical on a screen. Both may show a balance in dollars, move outside normal banking hours, and interact with programmable infrastructure. Economically, however, they are not the same asset.
The simplest distinction is the debtor. A tokenized deposit remains an obligation of a commercial bank to its customer. A fiat-backed stablecoin is issued under a separate stablecoin structure, with reserve assets, redemption terms, and holder rights defined by the issuer and the applicable rules.
That difference affects access, settlement, liquidity, credit risk, deposit protection, and where each instrument can circulate. It also explains why banks, central banks, stablecoin issuers, and payment companies are not necessarily building one universal form of digital cash.
Tokenization changes how a financial claim is recorded and transferred. It does not automatically change who owes the money or which legal framework applies.
A tokenized deposit is usually a digital representation of money held with a bank. The bank records the customer’s claim on a distributed ledger or connects that ledger to its core banking records. The resulting deposit token may support transfers and programmable conditions, but it still points back to a bank liability.
A fiat-backed stablecoin is a token designed to track a reference currency, usually one dollar or one euro. Its issuer holds reserves under a defined structure and sets the conditions for issuance and redemption. The token can often circulate among wallets on a public blockchain even when many holders have no direct account with the issuer.
When comparing the two, four questions matter more than the label:
These questions also help explain how stablecoins differ from one another. “Stablecoin” is a category, not one standardized balance-sheet model.
A bank deposit is already digital. Tokenization is therefore not about turning paper money into a database entry. It is about representing an existing deposit claim on programmable infrastructure, often using distributed ledger technology, or DLT.
The customer still has a claim against the bank. If the product is legally structured as a deposit, recording it on DLT does not by itself turn it into a stablecoin or a security. The token can serve as the technical representation used to transfer that claim, apply permissions, or coordinate settlement.
Implementations vary. A bank may keep the authoritative balance in its core ledger and use tokens as a synchronized transfer layer. Another design may make the DLT record the operative record for the deposit claim. Access can be limited to verified institutional clients, specific jurisdictions, or approved wallets.
This is why “tokenized” does not mean “permissionless.” A deposit token can run on a private network or on a public blockchain while remaining permissioned at the token level. The issuer can restrict who may receive it, which addresses may interact with it, and when transfers are allowed.
Deposit protection also requires product-specific analysis. If the instrument remains an eligible bank deposit, it may stay inside the relevant deposit-guarantee framework. That conclusion cannot be assumed from the word “deposit” alone: coverage depends on the bank, holder, legal structure, amount, and jurisdiction.
A fiat-backed stablecoin is a blockchain token intended to maintain a stable value against a currency. The issuer normally supports that promise with reserves such as cash, bank deposits, short-term government instruments, or other permitted liquid assets.
The token and the reserves are different things. A holder owns or controls the token. The reserve portfolio is held under the issuer’s legal and operational arrangement. Whether a particular holder can redeem directly, which identification checks apply, what minimum amount is required, and how quickly money is returned depend on the issuer’s terms and local regulation.
Stablecoins gained traction because they can move across public blockchain networks and between wallets, exchanges, payment services, and decentralized applications. A person does not necessarily need an account with the issuer to receive a token from another wallet. That transferability gives stablecoins broad reach, but it also separates the market price from the formal redemption channel.
If confidence, liquidity, or access to redemption weakens, a stablecoin can trade below or above its reference value. The mechanics behind that risk are covered in more detail in the guide to stablecoin depegs and business response.
This article focuses on fiat-backed payment stablecoins. Crypto-collateralized, algorithmic, commodity-backed, and yield-bearing tokens can use materially different risk models.
The visual balance is the easy part. The hard part is identifying the liability behind it.
The balance belongs to the bank’s deposit system. From the customer’s perspective, the asset is a claim against that bank. From the bank’s perspective, it is a liability that forms part of its funding base.
Banks use deposits within a regulated balance-sheet model. They hold liquid assets, make loans, manage capital and liquidity, and may have access to central-bank facilities. That does not make a bank deposit risk-free, but it places the claim inside the banking framework rather than a stand-alone reserve vehicle.
When customers of different banks pay one another, the banks must also settle between themselves. In the traditional system, that final interbank leg uses central-bank money. A tokenized system can preserve the same two-tier logic while coordinating the customer payment and bank settlement on programmable infrastructure.
A fiat-backed stablecoin typically uses a narrow reserve model. Money received for issuance is matched by a reserve portfolio rather than used like an ordinary bank deposit base. The issuer’s resilience therefore depends on reserve quality, custody, liquidity, segregation, operational controls, and the ability to meet redemptions.
Holder rights can differ. Some issuers offer direct redemption only to approved customers, while other users acquire and sell the token in secondary markets. A token trading at one dollar does not by itself prove that every holder has an unconditional one-dollar claim payable immediately.
This is why reserve disclosures, redemption terms, and market liquidity should be evaluated together. A strong reserve report cannot compensate for unclear holder rights, and a liquid secondary market cannot eliminate issuer or custody risk.
Stablecoin movement often looks simple: a wallet signs a blockchain transaction and the token balance changes. Once the network reaches the required state, the recipient controls the token. The banking system becomes relevant again when someone mints or redeems the stablecoin, converts it to fiat, or uses a regulated intermediary.
A tokenized deposit transfer may require more institutional coordination. If sender and recipient use the same bank, the bank can update two customer positions on its own ledger. If they use different banks, the system must move the customer claims and settle the banks’ positions without creating an unmatched payment.
Programmable ledgers can connect those steps. An atomic settlement design makes linked legs complete together or not at all. For example, a tokenized security and the payment asset can exchange simultaneously, reducing the period in which one party has delivered while the other still owes.
The relevant smart-contract mechanics can automate conditions, but code does not remove legal, credit, liquidity, cyber, or governance risk. It changes where some of those risks appear and how quickly they can propagate.
The idea is not new, but the institutional work has become more concrete.
Project Agorá, coordinated by the Bank for International Settlements and the Institute of International Finance, reported prototype results in May 2026. It used tokenized commercial-bank deposits and tokenized central-bank reserves to test wholesale cross-border payments across currencies and jurisdictions. The prototype demonstrated atomic settlement after the required validation and balance-locking steps.
That is evidence of technical feasibility, not a retail launch. The project involved central banks and regulated financial institutions, and the next phase focuses on real-value testing.
Banks are also developing their own models. J.P. Morgan announced JPMD as a permissioned dollar deposit-token proof of concept on Base for institutional clients. Citi Token Services uses bank infrastructure to let eligible institutional clients move liquidity between participating Citi branches around the clock, subject to product and market restrictions.
These examples reveal the current center of gravity: corporate liquidity, wholesale cross-border payments, collateral, and settlement of tokenized assets. They do not yet give an ordinary online merchant a universal deposit token that customers can send from any wallet.
At the same time, stablecoins already have broad distribution in crypto markets and digital payments. The 2026 debate is therefore not simply about which technology is newer. It is about whether open distribution and interoperability can be combined with the legal and liquidity structure of bank money.
Several digital assets can carry the same currency denomination without representing the same claim.
The last distinction matters when a product advertises yield. A fund share can accrue investment returns because it represents a portfolio. A bank may pay interest on an eligible deposit. A stablecoin issuer may face restrictions on paying interest directly, while a separate platform or protocol can expose the holder to lending, liquidity, or counterparty risk.
The same “digital dollar” description can therefore hide very different economics.
There is no universal winner. The better rail depends on who needs access, where value must circulate, and which legal claim the parties are prepared to hold.
Stablecoins are currently easier to use when a payment must travel between independent wallets, exchanges, apps, and service providers. Their public-chain reach supports international transfers, crypto checkout, platform balances, and DeFi settlement.
That reach also creates operational choices. A business must select accepted assets and networks, define confirmation and exception rules, plan conversion and withdrawals, and understand the on-ramp and off-ramp path.
Deposit tokens are attractive when both sides already operate inside regulated banking relationships and need 24/7 liquidity movement, programmable controls, or settlement against tokenized assets. Bank identity, compliance, and balance-sheet systems are features of this model, not friction that the design tries to remove.
The trade-off is reach. A deposit token restricted to one bank, consortium, client category, or approved address set cannot automatically function as universal internet money. Interoperability between banks and ledgers becomes a core requirement.
Stablecoins can bridge time zones and move across public networks, but businesses still need compliant entry and exit points, liquidity, and clear redemption. Tokenized deposits can preserve bank relationships and central-bank settlement, but they must overcome institutional silos and operating-rule differences.
Future payment systems may use several instruments together: bank money for regulated wholesale settlement, stablecoins for broader distribution, and conversion layers between them. Coexistence is more plausible than a single instrument replacing every other form of money.
The word “tokenized” should never substitute for due diligence. A team evaluating a specific instrument should examine the complete structure.
For stablecoin use in Europe, the practical questions are inseparable from MiCA-era asset and provider checks. A product available in one market may be restricted or structured differently in another.
Most online businesses are not choosing between a live universal deposit-token network and a stablecoin checkout. Their immediate choice is whether to accept existing crypto assets, how to connect the payment to an order, and what they want to hold or withdraw after settlement.
Stablecoin acceptance can be implemented now, but it still requires an operating model. Finance needs rules for accepted assets, networks, conversion, exceptions, reconciliation, and withdrawal controls. The stablecoin operations framework for CFOs covers that layer in detail.
CryptumPay fits this present-day payment layer. Its current documentation describes crypto checkout through an HTML widget or API, including stablecoin payment flows and backend notifications. It does not turn a stablecoin into a bank deposit and should not be treated as tokenized-deposit infrastructure.
For a merchant, that boundary is useful. Payment acceptance, treasury asset choice, and bank settlement are separate decisions. A company can accept stablecoin payments without claiming that USDT or USDC is the same as money in a bank account.
Before choosing a digital-money rail, start with the transaction rather than the technology.
This prevents a common category error: choosing a token because it looks familiar while ignoring the claim and infrastructure behind it.
Tokenized deposits bring bank money onto programmable rails. Stablecoins bring transferable digital tokens into wallets and applications across the internet. Both can support faster and more automated payments, but they inherit different institutions, safeguards, and constraints.
In the near term, stablecoins have the distribution advantage for crypto-native and online payment flows. Tokenized deposits have a strong institutional case for bank liquidity, wholesale payments, and settlement of tokenized assets. Interoperability, legal clarity, and reliable conversion will determine how closely those worlds connect.
For businesses, the useful question is not “which digital dollar wins?” It is “which claim are we willing to hold, who can use it, and how does it settle?” That distinction will remain important as the wider set of crypto payment trends evolves.
This article provides general information, not legal, tax, investment, or financial advice. Requirements and protections depend on the product and jurisdiction.
Create an account and connect the checkout yourself, or talk to sales and we will plan the integration with you.
Contact us and we will plan the integration.
