ZPAID — PRIVATE BY CHOICE

Receiving ZEC should start with a clear request and a wallet you control. ZPAID brings the steps together: inspect the receiving address, create a native payment request, and share it directly with your payer.




Start with what the address contains.A Zcash Unified Address can contain several receiver types. That flexibility matters: an address may offer a shielded receiver alongside a transparent fallback. ZPAID inspects those receivers locally, so you can see the distinction before creating a request. The structure is defined by ZIP 316.


Shielded receiving is selected by default. In this mode, the builder blocks transparent addresses, transparent fallbacks, and unknown receiver items. For supported Unified Addresses with known receivers, the inspector can create an address containing the same shielded receivers with the transparent fallback removed. This changes the address encoding; it does not create a wallet or move funds.




A request you can read.Add a mainnet receiving address, an amount in ZEC, and an optional label or reference. The builder prepares a native ZIP 321 payment URI and a QR code encoding those details. Amounts support up to eight decimal places. The result is inspectable and can be shared as a link or opened in a compatible wallet.


Invoices, services, and open-source support each have a starting template. The terminal offers quick access to creation, address inspection, documentation, and your saved requests. Saving is your choice: requests stay in this browser's storage, and can be reopened, exported, or removed.




Your wallet has the final word.ZPAID never needs a spending key or recovery phrase. The payer's compatible wallet reviews the request and signs the transaction. Funds go to the receiving address supplied in the request. Receipt must be checked in the receiving wallet; ZPAID does not automatically confirm settlement.


A shielded receiver is one part of privacy, not a guarantee about the complete payment path. The sending wallet, funding source, and chosen receiver also matter. And a shareable request is readable by anyone who has the link or QR—including its address, amount, label, reference, and any encoded memo. Keep sensitive details out of the request.




Check. Create. Share.The interface makes these boundaries visible: address inspection before the request, exact fields before sharing, and wallet review before payment. That is the idea behind ZPAID: a practical workspace for native Zcash requests, with control kept in your hands.

ZPAID is an independent tool, not affiliated with the Zcash Foundation or Electric Coin Company. Learn more about the network at z.cash.

Sources:
https://zips.z.cash/zip-0316
https://zips.z.cash/zip-0321
https://z.cash/
