They use technologies or payment systems that limit how much transaction data is visible or linkable to other parties.
Quick Answer: Privacy was built into the legacy financial infrastructure. A bank could verify a transaction without exposing a company’s entire payment history to the public. Blockchain-based payments change that equation. On public networks, a single wallet address can reveal not just one payment, but a trail of transactions, counterparties, and financial activity. As stablecoins and tokenized assets move into mainstream settlement, this creates a difficult question: how can payments remain verifiable without making commercially sensitive information visible to everyone? The Bank for International Settlements has identified privacy as a key design consideration for digital payments, highlighting the need to balance privacy with transparency and compliance.
Tokenized payments inherit a fundamental feature of public blockchains: transaction data can be inspected and analyzed after settlement. For individuals, this can expose wallet activity. For businesses, repeated transfers can reveal counterparties, payment volumes, and commercial connections.
The most sensitive information usually falls into three areas:
This becomes a reasonable concern as stablecoins and tokenized assets move into commercial payments. A public record can provide useful verification while also exposing information that a business would normally keep confidential. Private transaction infrastructure addresses this by limiting the visibility or linkability of payment data. ChangeNOW, for example, provides solutions to private transfers for crypto assets that reduce the direct on-chain connection between sender and recipient.
The setup question is therefore becoming more specific: which transaction data should remain public, and which should be available only to the parties or institutions that need it? That question leads directly to the different privacy models now being developed for onchain payments.
It’s also becoming harder to stay secure as crypto automation is rising.
Bitcoin made public transaction verification a central feature of crypto. Monero took a different route, using ring signatures and stealth addresses to make transactions harder to trace by default.
Ethereum-based privacy mechanisms introduced another model. Tornado Cash pooled deposits and withdrawals to obscure direct transaction links. In August 2022, the U.S. Treasury sanctioned the protocol, highlighting the regulatory risks surrounding transaction-obfuscation devices.
Tokenized finance is moving toward a more selective approach. Banks and asset managers may need transaction details hidden from the public while still giving regulators or other authorized players access when required. Privacy-preserving tokenization therefore focuses on controlling tokenized payments, rather than making every transaction opaque.
| Model | Where privacy sits | Main trade-off |
| Privacy networks | At protocol tier | Harder fit with regulated finance |
| Mixers | Between transactions | Stronger obfuscation, higher compliance risk |
| Selective privacy | Transaction or application layer | More authority over data access |
For encrypted payments, selective privacy is particularly relevant because it can protect commercial information while keeping transactions compatible with broader blockchain infrastructure. The subsequent issue is how this model can satisfy both privacy requirements and financial compliance.
Privacy can be applied either to the entire network or just particular transactions. Permissioned networks restrict transaction data to approved participants, while cryptographic tools can hide selected details on public blockchains.
Visa and Brale experimented with private stablecoin settlement on Canton Network in 2026, focusing on controlled access to institutional transaction data. Polygon also introduced private stablecoin payments using zero-knowledge proofs through Hinkal, keeping settlement on a public network while concealing transaction details.
Privacy and anonymity serve different purposes. Privacy limits who can see transaction data, while anonymity makes the parties harder to identify. A regulated payment can therefore keep amounts or counterparties confidential while still allowing authorized institutions to identify the participants.
Regulated tokenized finance still needs KYC, AML checks, and transaction monitoring. BIS Project Mandala tested a protocol that builds jurisdiction-specific compliance rules into cross-border transactions and uses cryptographic proofs to limit the amount of data shared.
Compliance units may need to identify transaction parties, check whether a transfer meets applicable rules, and screen it against relevant restrictions. Project Agorá tested tokenized commercial bank deposits and central bank reserves on a shared platform, with compliance requirements built into the transaction workflow. The 2026 prototype involved more than 40 regulated financial institutions and demonstrated atomic cross-border settlement.
The same transaction can therefore carry the information needed for regulatory checks without revealing its entire record to every participant.
A company paying a supplier with tokenized money may need to prove that the payment is approved while keeping its wider treasury activity, pricing terms and other counterparties confidential.
ANZ, ADDX and Chainlink tested this type of setup for tokenized commercial paper under Singapore’s Project Guardian. The test used encrypted transaction data and selective access to support confidentiality during cross-border settlement.
That creates a clearer boundary around transaction data: regulators can receive information needed for oversight while counterparties see only what their role requires.
The path for private encrypted payments will depend on regulatory clarity, interoperability, and the readiness of financial institutions to use public blockchain infrastructure for sensitive transactions. Three scenarios show what these conditions could mean in practice.
Mixed payment systems become the common model. Routine transfers remain on public networks, while banks and large businesses use permissioned environments for payments involving sensitive commercial data. A company could therefore use a public stablecoin rail for standard transfers while keeping supplier settlements and treasury operations within a controlled network.
Typical privacy standards allow tokenized payments to move between public and private networks without rebuilding compliance and confidentiality controls for each connection. A multinational could pay a supplier in tokenized money across several networks, with the transaction resolving on the most suitable rail while sensitive details remain restricted to the parties that need them. This would make cross-border tokenized payments easier to integrate into existing financial systems.
Fragmented regulation and lofty compliance costs push institutions toward closed networks. Banks may restrict public-chain settlement to low-risk transactions and require sensitive payments to remain within approved platforms. Businesses operating across several jurisdictions could then confront different privacy and reporting requirements for similar transactions, making private encrypted payments more expensive and harder to scale.
The most likely direction is a hybrid model where privacy is built into payment infrastructure and adjusted to the transaction. Recent BIS projects point toward shared tokenized platforms that combine settlement, compliance, and data safeguards rather than treating privacy as a different layer.
For encrypted payments, the competitive question will be whether these systems can give businesses meaningful confidentiality while keeping transactions verifiable and workable across jurisdictions. The schemes that solve both requirements will have a stronger case for institutional adoption.
They use technologies or payment systems that limit how much transaction data is visible or linkable to other parties.
Transaction data can disclose commercially sensitive information such as payment patterns, counterparties, and treasury activity. Privacy controls can limit this exposure.
Privacy approaches can restrict data access while allowing authorized institutions to verify identities, transaction conditions, or compliance requirements.
Privacy itself is normally compatible with regulated finance, although specific requirements vary by jurisdiction and transaction type. Services that facilitate crypto transfers may still be subject to applicable AML, sanctions, and reporting rules.
A hybrid approach appears more likely, with different levels of data access depending on the transaction and the participants involved. Institutional projects are already testing privacy management alongside tokenized settlement infrastructure.
