Skip to main content

Overview

The Payments domain covers institutional cash movement scenarios including payouts, payment-versus-payment (PvP) settlements, delivery-versus-payment (DvP) cash legs, and workflows requiring selective disclosure to stakeholders.
Key Focus: Stakeholder-only visibility with selective disclosure, ISO/SWIFT linkage when needed, and optimized latency/finality/costs on target networks.

Core Requirements

Privacy

Transaction details visible only to authorized stakeholders, protecting commercial terms and workflow memos

Compliance

Selective disclosure mechanisms for regulatory oversight without compromising counterparty privacy

Finality

Measure and optimize settlement latency on target L2 or app-chain infrastructure

Interoperability

ISO 20022 messaging integration for legacy payment rail connectivity

Technical Considerations

Hash Time-Locked Contracts (HTLCs) introduce timing dependencies and failure modes that are problematic for institutional settlements. Prefer ERC-7573 or zk-SPV patterns for atomic operations.
Evaluate latency, finality guarantees, and gas costs on target networks. App-chains offer predictable performance but require bridge security. L2s provide Ethereum security but may have variable throughput.
For workflows requiring comprehensive audit trails without on-chain data exposure, combine L2 privacy with encrypted off-chain storage and selective key disclosure.

Primary Use Cases

Private Stablecoins for Institutional Payments

Confidential stablecoin transfers between institutional counterparties with regulatory reporting

Shortest-Path Patterns

These patterns provide proven implementation approaches for common payment scenarios:

Private Stablecoin Shielded Payments

Zero-knowledge proofs for confidential stablecoin transfers

Private PvP via ERC-7573

Atomic payment-versus-payment with privacy preservation

Atomic DvP via ERC-7573

Delivery-versus-payment settlements with cryptographic guarantees

L2 + Encrypted Off-chain Audit

Layer-2 privacy with comprehensive audit trail management

Private ISO 20022 Messaging

Integration with legacy payment messaging standards

Adjacent Vendors

Chainlink ACE

Cross-chain atomic settlements with privacy

Kaleido Paladin

Enterprise privacy orchestration layer

Aztec L2

Zero-knowledge rollup for private payments

Trading

DvP cash leg settlements in trade execution workflows

Identity & Compliance

KYC/AML verification required before payment authorization
Payment workflows typically require coordination with Custody domain for secure key management and Identity & Compliance for transaction authorization.

Build docs developers (and LLMs) love