Domain
Payments
Institutional cash movement: payouts, PvP, DvP cash legs, workflow/memo privacy. - Stakeholder-only visibility with selective disclosure; ISO/SWIFT linkage when needed. - Measure latency/finality/costs on target L2/app-chain; avoid HTLC brittleness.
5
Case Studies
5
Patterns
3
Vendors
Shortest-path Patterns
Building blocks for payments privacy
Vendors
Who builds payments privacy tooling
Chainlink ACE
Modular compliance layer built on the Chainlink Runtime Environment (CRE) to define, execute, and enforce identity- and policy-based controls for digital assets across public and private chains. Core onchain components (CCID, CCT Compliance Extension) pair with CRE services (Policy/Identity/Monitoring managers). Offchain policy execution returns signed approvals; onchain enforcement is required. PII/NPI remains offchain. It enables private transactions, with one of the main target use cases being CBDCs management.
Paladin
Open-source (Apache-2.0) privacy layer under the [Linux Foundation Decentralized Trust](https://github.com/LFDT-Paladin/paladin). Paladin provides the common wallet/vault functions that are needed to interact with all forms of privacy preserving smart contracts. It also provides a model for atomic programmability across these privacy preserving smart contracts, harnessing the power of the underlying EVM shared ledger.
Aztec Rollup
Aztec is a privacy focused rollup (or zk-zk-rollup) on Ethereum that enables private transactions and programmable privacy. It is a fully programmable network where applications can access both private and public state.