A Hitchhiker's Guide to Privacy-Preserving Digital Payment Systems: A Survey on Anonymity, Confidentiality, and Auditability

1. Problem Statement

The rapid proliferation of digital payment systems, ranging from decentralized crypto-assets (e.g., Bitcoin, Monero) to Central Bank Digital Currencies (CBDCs), has created a fundamental tension between user privacy and institutional accountability.

• The Conflict: Public blockchains offer transparency and auditability but suffer from pseudonymity, allowing transaction tracing, address clustering, and user de-anonymization. Conversely, strict privacy mechanisms (like mixing or zero-knowledge proofs) often hinder regulatory compliance requirements such as Anti-Money Laundering (AML) and Combating the Financing of Terrorism (CFT).
• The Gap: Existing literature often focuses narrowly on specific technologies (e.g., only ZKPs or only mixers) or specific domains (only crypto-assets or only CBDCs). There is a lack of a unified framework that maps high-level privacy goals (anonymity, confidentiality, unlinkability) to concrete cryptographic implementations while simultaneously addressing the trade-offs required for auditability.

2. Methodology

The authors adopt a design-oriented perspective to survey the landscape of privacy-preserving digital payment systems.

• Scope: The survey covers both decentralized ledger systems and centrally managed infrastructures (CBDCs).
• Taxonomy Construction: The authors developed a multi-dimensional taxonomy to classify existing solutions. The dimensions include:
  • Protocol: System architecture, trust models, and interaction models.
  • Value Representation: How balances and transfers are modeled (Account-based vs. Token-based vs. Tabular).
  • Privacy Features: Specific guarantees like sender/receiver anonymity, value confidentiality, and unlinkability.
  • Auditability: Mechanisms for regulatory oversight (e.g., revocable anonymity, operating limits).
• Generational Analysis: The literature is traced through three conceptual "generations" to highlight the evolution from basic anonymity toward nuanced privacy-accountability trade-offs.
• Cryptographic Mapping: The study systematically maps high-level privacy objectives to the underlying cryptographic primitives (e.g., Blind Signatures, Ring Signatures, ZKPs, Homomorphic Commitments) and protocols that realize them.

3. Key Contributions

A. A Unified Taxonomy

The paper introduces a comprehensive classification system that bridges the gap between decentralized crypto-assets and regulated CBDCs. It categorizes systems based on:

• Architecture: Centralized (trusted issuers) vs. Decentralized (blockchain).
• Data Models: Account-based (balances), Token-based (UTXO/Chaumian), and Tabular ledgers.
• Privacy Guarantees: Distinctly separating Sender Anonymity, Receiver Anonymity, Value Confidentiality, Network Anonymity, and Unlinkability.
• Auditability Mechanisms: Anonymity budgets, operating limits, revocable anonymity, and verification without disclosure.

B. The Three-Generation Evolution

The authors trace the historical and conceptual evolution of these systems:

1. First Generation (Centralized): Relies on trusted issuers (banks) and Blind Signatures (e.g., Chaum's eCash). Focuses on payer anonymity but requires a central authority for auditability.
2. Second Generation (Decentralized/Privacy-Native): Emerged with Bitcoin. Focuses on Unlinkability and Untraceability using Ring Signatures, Stealth Addresses, and ZKPs (e.g., Monero, Zerocash). These systems often sacrifice auditability for strong privacy.
3. Third Generation (Balanced/Compliant): Integrates Auditability into the protocol design. These systems use advanced tools like Zero-Knowledge Proofs (ZKPs), Threshold Encryption, and Homomorphic Commitments to allow selective disclosure and regulatory compliance without fully compromising user privacy (e.g., zkLedger, PEReDi).

C. Technical Deep Dive

The paper provides a granular analysis of how specific privacy goals are achieved:

• Sender Anonymity: Achieved via Blind Signatures (eCash), Ring Signatures (Monero), or Group Signatures.
• Receiver Anonymity: Achieved via Stealth Addresses (one-time keys) or Encrypted Addresses.
• Value Confidentiality: Achieved via Pedersen Commitments (Confidential Transactions) or Homomorphic Encryption.
• Auditability: Implemented through "Trapdoors" (encrypted metadata accessible only to authorities), Anonymity Budgets (limiting anonymous transactions), and "Verification without Disclosure" (proving compliance via ZKPs without revealing data).

D. Identification of Open Challenges

The survey identifies critical gaps in current research:

• Formal Definitions: Lack of unified, composable formal definitions for privacy and auditability (e.g., Universal Composability proofs).
• Scalability & Efficiency: High computational costs of ZKPs (especially trusted setup for zk-SNARKs) and Homomorphic Encryption.
• Network-Level Privacy: Most systems rely on external networks (Tor/I2P) for IP obfuscation, leaving a cross-layer vulnerability where transaction timing and ordering can de-anonymize users.
• Adaptive Privacy: Difficulty in managing dynamic anonymity sets and rotating roles (e.g., in CBDCs) without compromising unlinkability.

4. Results and Findings

• Trade-offs are Inevitable: No single protocol satisfies all privacy and compliance goals. Systems must prioritize based on their threat model. For instance, strong unlinkability often complicates auditability, while encrypted transactions complicate oversight.
• Cryptographic Primitives are Context-Dependent:
  • Blind Signatures are efficient but require central trust.
  • Ring Signatures offer scalable anonymity but are vulnerable to heuristic analysis if the anonymity set is small.
  • ZKPs offer the strongest guarantees (hiding sender, receiver, and amount) but are computationally intensive and often require trusted setups.
• Auditability is a Design Feature, Not an Add-on: Third-generation systems demonstrate that auditability must be embedded in the protocol architecture (e.g., via accumulators or specific ledger structures like zkLedger's tabular model) rather than applied as a post-hoc layer.
• Hybrid Architectures are Emerging: The most promising solutions combine multiple primitives (e.g., Threshold Encryption + ZKPs + Commitments) to balance privacy, trust, and enforcement.

5. Significance

This paper serves as a critical reference for researchers, engineers, and policymakers in the field of digital finance.

• Bridging Communities: It bridges the terminology gap between the decentralized crypto-community and central bank regulators, offering a common language for discussing privacy and compliance.
• Design Guidance: By mapping privacy goals to specific cryptographic implementations, it provides a "design guide" for building new payment systems that can navigate the complex landscape of AML/CFT regulations while preserving user rights.
• Future Roadmap: It clearly outlines the research directions needed to move from academic prototypes to deployable, compliant, and scalable privacy-preserving payment systems, emphasizing the need for formal verification, efficiency improvements, and cross-layer privacy solutions.

In summary, the paper argues that the future of digital payments lies not in choosing between privacy and regulation, but in designing multidimensional systems where cryptographic tools are carefully orchestrated to satisfy both user anonymity and institutional accountability.