The BIS Stablecoin Dollarisation Paper Is a Wallet-Risk Warning, Not Just a Macro Note

The Bank for International Settlements published a working paper on July 21, 2026 that deserves more attention from crypto operators than the usual central-bank research note. The paper, "Dollarisation and monetary control: what lessons for the rise of stablecoins?", studies dollar-pegged stablecoin inflows across more than 130 economies and compares them with the older pattern of foreign-currency bank deposits.

The headline finding is simple enough: stablecoin dollarisation behaves like dollarisation, but it does not sit inside the same control surface. BIS researchers found that stablecoin flows share many drivers with conventional dollar deposits, including sovereign stress, banking crises, and exchange-rate pass-through. But unlike bank deposits, stablecoin flows appear largely unaffected by capital-flow and foreign-exchange restrictions.

That is not just a macroeconomic observation. It is an operational warning. If dollar stablecoins are increasingly used as a parallel dollar rail in countries where banks, exchanges, and payment processors face tighter controls, then wallet monitoring becomes part of treasury governance. The question is no longer only whether a token trades at one dollar. It is whether the wallet path, issuer policy, jurisdictional exposure, and counterparty graph can survive scrutiny when regulators, issuers, banks, or exchanges decide a flow should not move.

FreezeRadar is built around that exact problem: stablecoins are useful because they are fast, liquid, and programmable, but the same properties make them sensitive to issuer intervention, sanctions exposure, and indirect counterparty risk.

What BIS actually found

The BIS paper compares two ways people and institutions get dollar exposure outside the United States. The first is familiar: holding foreign-currency deposits in the banking system. The second is newer: moving into dollar-pegged stablecoins such as USDT or USDC through crypto rails.

The paper does not claim stablecoins have replaced bank deposits. It says the two forms of dollar exposure share similar macro drivers and can both become persistent once established. That matters because dollarisation is rarely a temporary preference. Once businesses, households, brokers, remittance firms, and informal liquidity providers build workflows around a dollar instrument, reversing that behavior is hard.

The more important distinction is control. Bank deposits are visible to banks, supervisors, and capital-flow rules. Stablecoins can circulate between self-custodied wallets, centralized exchanges, OTC desks, payment apps, and DeFi contracts. Some of those touchpoints are regulated. Some are lightly supervised. Some are simply addresses.

For a compliance team, the practical reading is this: stablecoins can carry dollar exposure across borders even when the banking channel is constrained. That does not automatically make the flow illicit. It does make the risk assessment more dependent on wallet provenance, counterparties, chain selection, issuer controls, and the quality of monitoring between the first and last regulated touchpoint.

Why this is bigger than monetary policy

Central banks care because broad stablecoin adoption can affect monetary sovereignty, bank funding, and financial stability. A treasury team cares for a different reason: a payment rail that bypasses traditional frictions also bypasses many of the cues that normally trigger review.

A wire transfer gives institutions names, accounts, banks, jurisdictions, and message fields. Stablecoin transfers give them token contracts, chains, addresses, amounts, timestamps, and transaction paths. That is powerful data, but it requires a different operating model. A wallet that looks clean at the direct counterparty level may still be exposed through recent upstream funding, reuse of OTC settlement clusters, mixer-adjacent flows, sanctioned infrastructure, or issuer-blacklisted neighbors.

This is where the BIS finding connects directly to two-hop exposure analysis. If stablecoins are being used as a pressure-release valve around local currency weakness or transfer restrictions, first-hop screening is not enough. The relevant question is whether the wallet sits inside a flow pattern that a bank, exchange, issuer, or regulator may later treat as high risk.

The risk is especially sharp for companies that accept stablecoin payments from distributors, affiliates, brokers, market makers, cross-border customers, or treasury counterparties in high-friction markets. A payment can settle in seconds and still become a problem days later if its provenance changes, an upstream address is designated, or an issuer freezes a connected address.

The issuer-control layer is unavoidable

The BIS paper is about dollarisation, not token blacklists. But stablecoin dollarisation cannot be separated from issuer control. The dominant dollar stablecoins are not bearer cash. They are issuer-controlled assets running on public ledgers. Their contracts, policies, and redemption systems determine what happens when a wallet is frozen, blacklisted, rejected, or treated as unacceptable by a platform.

That is why operational teams should read the paper alongside FreezeRadar’s guide to freezeable assets and stablecoin compliance. When a token is freezeable, risk is not only market risk. It is also intervention risk. A user may hold the private key and still lose practical control over a token balance if the issuer blocks transfers at the contract level or if downstream venues refuse the funds.

This creates three separate questions for any serious stablecoin workflow:

1. Is the asset itself issuer-controlled, and what can the issuer do?
2. Is the wallet exposed to sanctions, blacklist, fraud, mixer, or high-risk counterparty signals?
3. Is the business prepared for a delayed intervention after funds have already been received or routed onward?

The BIS dollarisation paper strengthens the case for asking those questions before stablecoin rails become deeply embedded in treasury operations.

Capital controls do not remove sanctions risk

One mistake would be to treat the paper as a story about emerging markets finding useful dollar access and stop there. Stablecoins can be legitimate tools for savings, remittance, working capital, and cross-border settlement. They can also become attractive rails for sanctioned entities, procurement networks, fraud groups, and capital-flight intermediaries.

FATF has already warned that stablecoins are heavily represented in illicit crypto activity and that peer-to-peer transfers through unhosted wallets remain a key weakness. Chainalysis separately reported a sharp rise in state-driven sanctions evasion volume in 2025, including stablecoin-linked activity around sanctioned actors and parallel-market infrastructure.

The operational point is not that every cross-border stablecoin flow is suspect. That would be lazy and commercially useless. The point is that teams need controls that can distinguish ordinary dollar demand from exposure patterns that create freeze, rejection, reporting, or escalation risk.

A stablecoin payment from a customer in a stressed currency environment should not be rejected by default. But it should be screened against direct sanctions lists, issuer blacklist data, known freeze events, exchange intervention patterns, risky counterparty clusters, and recent inbound provenance. FreezeRadar’s OFAC wallet screening guide lays out the defensible version of that workflow: screen, document, escalate where needed, and avoid turning every privacy-adjacent or emerging-market wallet into a false positive.

Treasury teams need a wallet policy, not just an issuer preference

Many organizations still treat stablecoin risk as an issuer selection problem. They ask whether USDC is safer than USDT, whether reserves are liquid, whether the issuer has a bank partner, or whether the token is available on the right chain. Those questions matter. They are not enough.

The BIS paper pushes the discussion toward flow behavior. If stablecoins are being used as persistent dollar instruments across economies and restrictions, then treasury teams need policies for wallet intake, chain selection, approval thresholds, and post-receipt monitoring.

A practical policy should include at least five controls.

First, separate treasury wallets by purpose. Do not use the same receiving address for customer payments, OTC settlements, internal treasury routing, DeFi yield experiments, and exchange withdrawals. Commingling makes provenance harder to explain.

Second, require pre-transfer screening for material payments. A stablecoin transfer that is cheap and instant can still deserve human review when the amount, jurisdiction, counterparty type, or routing path is unusual.

Third, monitor after receipt. Sanctions designations, issuer blacklist events, and exchange labels can change after a transaction settles. A wallet that was acceptable on Monday may require action on Thursday.

Fourth, define escalation thresholds before there is a crisis. Treasury, compliance, finance, and legal teams should agree what happens when a wallet receives funds linked to a sanctioned entity, mixer, freeze event, or high-risk OTC cluster.

Fifth, maintain fallback rails. If a stablecoin issuer or exchange blocks a flow, the business needs a documented path for refunds, customer communication, accounting treatment, and evidence preservation.

This is the operational core of wallet monitoring strategy: a useful watchlist is not a static blacklist. It is a decision system.

What teams should watch next

The BIS paper is one piece of a broader stablecoin-risk shift. The Fed has already examined how payment stablecoins could affect cross-border payments and monetary-policy implementation. Another BIS paper linked dollar-backed stablecoin inflows to short-term Treasury yields, with stronger effects under stress and as the sector grows. Recent academic work using Austrian crypto-asset service provider data showed how transaction-level stablecoin monitoring can reveal patterns that aggregate data misses.

Taken together, these pieces point in the same direction. Stablecoins are moving from crypto market plumbing into macro-financial infrastructure. That does not make them bad. It makes weak controls more expensive.

For wallet-risk teams, the next monitoring priorities are concrete:

• Track issuer blacklist and freeze events by chain and asset.
• Watch for sudden stablecoin inflows from jurisdictions under banking, FX, or sanctions pressure.
• Review upstream counterparties, not only direct senders.
• Separate routine customer payments from brokered settlement flows.
• Keep evidence trails for why a wallet was accepted, rejected, escalated, or monitored.
• Reassess exposure when sanctions lists, issuer policies, or exchange restrictions change.

The most important thing is to stop treating stablecoin settlement as final simply because the transaction confirmed on-chain. Confirmation proves the transaction entered the ledger. It does not prove the asset will remain usable across issuers, venues, banks, and regulators.

Key takeaway

The July 21 BIS paper is framed as research on dollarisation and monetary control. For FreezeRadar readers, the sharper lesson is operational: stablecoin dollar flows can move outside traditional banking controls, but they do not move outside risk.

That creates a new standard for treasury and compliance teams. If a business uses USDT, USDC, or another freezeable dollar token, it needs wallet-level visibility into sanctions exposure, issuer intervention risk, indirect counterparty provenance, and post-settlement changes. Stablecoins may reduce payment friction. They do not reduce the need for defensible monitoring.

Image credits: cover image, "Bank for International Settlements in the late afternoon 2.jpg" by Michal Pleskowicz via Wikimedia Commons, licensed under CC BY-SA 4.0. Inline image, "Bitcoin and cryptocurrency (38688311185).jpg" by Stock Catalog via Flickr/Wikimedia Commons, licensed under CC BY 2.0 with attribution to www.quotecatalog.com.