Open Wallet Standard · zkx:kyc

ZK-KYC
for Agents

Institutional-Grade Zero Knowledge Proofs for Agentic Banking

Try the DemoHow it works

0 bytes

PII transmitted

~2.5s

Proof generation

Groth16

ZK protocol

OWS native

Wallet standard

How it works

Compliance that scales with risk

ZKX acts as a middleware layer in the payment stack. Low-value flows stay fully private. High-value flows require proof — not disclosure.

01< $1,000 / day

Anonymous micropayment

Agent initiates a payment under the daily threshold. No identity required. No data collected. Fully private by default.

02Policy engine

Real-time threshold check

The ZKX compliance engine — an Open Wallet Standard middleware — evaluates cumulative daily spend in real time against the policy.

03≥ $1,000 / day

Zero-knowledge identity proof

Above the limit, the agent generates a Groth16 proof in-browser. The verifier learns the credential is valid — nothing more.

The ZK Circuit

What the verifier learns

  • ✓The holder knows a preimage (idHash, salt) that maps to a registered commitment
  • ✓Age satisfies currentYear − birthYear ≥ 18
  • ✗Name, ID number, date of birth, or any PII
kyc_credential.circom
// private inputs — never leave browser
signal private input idHash;
signal private input birthYear;
signal private input salt;
// public inputs — visible to verifier
signal input commitment;
signal input currentYear;
signal input minAge;
// constraint: Poseidon(idHash, salt) == commitment
// constraint: currentYear - birthYear >= minAge

Live demo

Interactive compliance engine

Select a scenario and send a payment. Exceed the daily threshold to trigger the ZK proof flow.

Technology

Built with

◈

circom

ZK circuit language

⚡

snarkjs

Groth16 prover / verifier

⬡

Open Wallet Standard

zkx:kyc feature extension

∿

Poseidon hash

ZK-friendly commitment

▲

Next.js 16

App + API routes

∞

BN128 curve

Elliptic curve cryptography