Private Commerce
Your checkout calls createInvoice(). The customer scans a QR code. Your backend receives approved: true. You never see their identity, wallet address, or account balance. Proof replaces disclosure.
From checkout to settlement in three calls
No token vaults. No card-on-file. No PII storage. Each call returns a deterministic response. The complexity lives in 35 zero-knowledge circuits that run on our infrastructure, not yours.
createInvoice()
Pass amount, currency, and a reference ID. Returns an invoice object with a payment URI and expiration.
displayQR()
Render the payment URI as a QR code. Customer scans with any H33-compatible wallet. Proof generated client-side.
getSettlement()
Poll or webhook. Returns approved: true, settlement rail, and a cryptographic receipt. No customer data. Ever.
The merchant gets approval. Not identity.
Your API response contains everything you need to fulfill an order and nothing that creates liability. The zero-knowledge proof attests that funds are sufficient, compliance checks passed, and the customer authorized the transaction. You never touch the underlying data.
What the Merchant Sees
- approved: true
- Settlement amount and currency
- Settlement rail (ACH, RTP, FedNow, Card, etc.)
- Cryptographic receipt (verifiable)
- Invoice reference ID
- Settlement timestamp
- Compliance attestation (KYC/AML passed)
What the Merchant Never Sees
- Customer name or identity
- Bank account or routing number
- Wallet address
- Account balance
- Card number or CVV
- SSN or government ID
- Transaction history
Measured in liability reduced, not features added
Chargeback Reduction
Customer authorizes via cryptographic proof. No friendly fraud. No "I didn't authorize this." The math doesn't lie.
PCI Scope Reduction
You never touch card data. Never store it. Never transmit it. Your PCI audit surface shrinks to near-zero.
Liability Reduction
No PII in your database means no PII in your breach notification. You can't leak what you never had.
Faster Integration
Three API calls. No token vaults. No card-on-file flows. No 3DS redirects. Ship in an afternoon.
Better UX
Customer scans a QR code. No form fields. No OTPs. No "please re-enter your card." One scan, done.
Seven lines. Copy-paste ready.
One package. No dependencies on chain SDKs.
The H33 Commerce SDK handles proof generation, rail selection, and settlement verification. It feels like Stripe. Because that's how payment SDKs should feel.
npm install @h33/commerce
Source: github.com/H33ai/h33-commerce
Four endpoints. REST. JSON. Nothing exotic.
| Method | Endpoint | Description |
|---|---|---|
| GET | /v1/commerce/health | Service health and circuit status |
| POST | /v1/commerce/invoice | Create a payment invoice with amount, currency, and reference |
| GET | /v1/commerce/settlement/{id} | Retrieve settlement status, rail, and cryptographic receipt |
| POST | /v1/commerce/verify | Independently verify a settlement receipt |
35 AIR Circuits
35 zero-knowledge circuits handle the complexity. You never touch one. Proof-of-funds, KYC attestation, AML screening, sanctions checks, age verification, account authorization, rail eligibility, currency conversion, fee calculation, settlement finality, receipt generation, and 24 more. Each circuit produces a STARK proof. Each proof is post-quantum attested via H33-74. The merchant calls three functions. The circuits do the rest.
Six rails. One API.
The customer chooses how to pay. The merchant receives the same response object regardless of rail. No rail-specific integration. No conditional logic. One handler for all settlement types.
Proof replaces disclosure.
Three API calls. Ten minutes to integrate. No PII in your system. No chargebacks from unauthorized transactions. No PCI scope for data you never touch. Talk to us.