Common integration mistake
Transparent fallback
Should blockA checkout promises privacy but falls back to a transparent receiver.
Zcash privacy tooling
Catch privacy leaks before they ship.
Inspect a Zcash payment request or address and get a plain-language policy review. ShadeCheck runs in your browser and never asks for keys or funds.
Nothing is uploaded or stored.
Guided demo
See a privacy leak before it ships.
Choose a realistic checkout path. ShadeCheck turns the request into a policy gate, an exposure explanation, and a fix you can act on.
1 Choose2 Review3 Fix
Safer starting point
Shielded checkout
Should passA payment request uses a shielded-capable receiver and includes the amount.
Analyze an input
Start with a ZIP-321 payment request or a single address.
Privacy review
Every finding includes a source and an action.
Nothing reviewed yet
Paste an input or use a sample to see the policy gate, request anatomy, and next actions.
Parse the request
Read ZIP-321 addresses, amounts, memos, assets, and indexed payments without sending input to a server.
Explain exposure
Separate transparent, shielded-capable, mixed, unknown, and cross-network paths in language a product team can use.
Ship with confidence
The next phase keeps any chain-aware adapters opt-in and separate from local policy rules.
Public fixtures
Review common integration mistakes.
These examples contain no wallet data. Open one to see the same rules, sources, and redacted sharing path.
Blocked1 payment
Transparent output
A payment request routes value to a transparent receiver.
Review required1 payment
Amount missing
A shielded-capable request leaves the wallet to ask for the amount.
Blocked2 payments
Mixed network
One request contains payment targets from different Zcash networks.