Privacy-Enhancing Augmentation Layer

Zero-Knowledge
Payment Proof Layer

A privacy-enhancing augmentation layer that sits alongside your existing payment rails. Generate cryptographic payment proofs that attest to transaction validity—without exposing sensitive financial data.

How It Works

Core data flow for cryptographic payment proofs

01

Payment Attestation

We verify the authenticity of payment events (Stripe, PayPal, etc.) following the official procedures of the providers, and on-chain stablecoins.

02

ZK Proof Generation

The SDK captures attestations and transforms them into zero-knowledge proofs using Circom circuits. Proofs validate payment authenticity without exposing amounts, identities, or transaction IDs.

03

Verification & Registry

Optional on-chain registration on EVM-compatible networks provides immutable, publicly verifiable records.

Client SDK Integration

TypeScript SDK for browser and Node.js environments

Quick Start

The ZKIW Client SDK integrates seamlessly into merchant flows. Capture attestations, communicate with backend services, and generate cryptographic receipts—without modifying your payment core.

Multi-rail adapters (Bank, Stablecoin, Card)
Circom-based ZK circuits (Groth16/PLONK)
Export verification bundles & receipts
JavaScript
// Initialize ZKIW SDK
const payProof = ZKIWPayProof.init({
  apiBase: "https://api.zkiw.com",
  merchantId: "MERCHANT-123",
  railAuthPublicRoot: "0xabc123..."
});

// Generate proof on payment completion
gateway.on("payment:completed", async (evt) => {
  const attestation = {
    rail: "BANK",
    amount: evt.amount,
    payerHash: evt.payerHash,
    timestamp: evt.timestamp,
    settlement: true
  };

  const proof = await payProof.generate(attestation);
  
  // Render ZK receipt widget
  payProof.renderWidget("#receipt", proof);
});

On-Chain Proof Registry

The PaymentProofRegistry smart contract stores proof commitments on Ethereum and L2 networks. Provides immutable, publicly verifiable records with Merkle-based processor authorization—no sensitive data exposed.

Groth16
SNARK Proofs
Audited
Smart Contracts
EVM
Compatible Chains
Proof Commitment 0x7a9f...
Rail BANK
Commitment 0x3e8d9a...
Timestamp 1732004500
Amount ●●●●●●
Parties ●●●●●●

Design Goals

Built for privacy, compatibility, and production deployment

Privacy by Default

Payment proofs never expose sensitive financial data (amounts, identities, raw transaction IDs) unless explicitly disclosed through controlled mechanisms.

Existing Rails Compatible

Integrates with conventional bank transfers, card processors (Stripe/PayPal), and on-chain stablecoins—without requiring changes to underlying payment infrastructure.

Strong Cryptographic Integrity

Proofs backed by Circom circuits using Poseidon hashing and Merkle verification—providing formal guarantees on correctness and soundness.

Auditability & Compliance

Supports selective disclosure, structured audit trails, and regulator-oriented views. Enable compliance workflows without mass data exposure.

Production Deployment

Containerized services, on-chain registries, documented infrastructure, and observability tooling. Self-hosted or managed SaaS configurations available.

Formal Verification

Critical invariants modeled and machine-checked in Lean. CI-integrated theorem checking guards core protocol properties and cryptographic assumptions.

Deploy the Payment Proof Layer

Self-hosted or managed SaaS—integrate cryptographic payment verification into your workflows