SHIELDED
RECEIVINGCreate requests that require a shielded-only receiving address. Orchard or Sapling, with no transparent fallback. Review the final payment in your wallet.
ZPAID / PAYMENT PATH ZIP 321EVENTDESTINATIONSTATE
ZP
THE REQUEST IS YOURS.
THE FUNDS ARE YOURS.
01 / create a requestlocal browserCOMPOSE
02 / share a link or QRyour recipientENCODE
03 / review in walletzcash networkUSER SIGNED
ZCASH / SHIELDED RECEIVING / PRIVATE BY CHOICE
YOUR PAYMENT.
YOUR PRIVACY.
Get paid in ZEC with shielded receiving. Inspect your address, keep transparent fallbacks out of your request, and share directly with the payer. Your money. Your keys.
NATIVE ZEC
- PRIVACY LAYER
- Zcash
- KEYS HELD BY US
- 0
- YOUR SAVED REQUESTS
- 0
- CUSTODY
- Always yours
INSPECT
ADDRESS PRIVACYRead what your address actually contains. See its Orchard, Sapling, and transparent receivers before you share a request. The inspection runs locally in your browser.
WORKSPACE
YOUR DEVICEKeep the requests you choose to save in one place. Reopen, copy, or export them. Confirm incoming payments in your own wallet.
DEVELOPERS
OPEN FORMATUse Zcash's payment request standard. Inspect the URI, copy its exact fields, and integrate a payment button into your own workflow.
PRIVACY
BY DESIGNShielded on-chain does not mean hidden everywhere. Understand what stays on your device, what the payment link exposes, and what your wallet protects.
How privacy works +CONTROL ROOM · ON THIS DEVICE
YOUR PAYMENTS, IN YOUR HANDS.
A shielded receiver. A request you can inspect. A wallet you control.
SAVED REQUESTS
+
A fresh start.
Create your first payment request.
Save it only when you choose.
THE PRIVACY STACK01 / ZEC
- ASSET
- ZEC NATIVE
- RECEIVERS
- Orchard / Sapling
- PLATFORM CUSTODY
- None
- SIGNING
- Your wallet
WALLET HANDOFFDIRECT
- 01
Compose the requestAddress · amount · reference
LOCAL - 02
Open a compatible walletReview all payment details
REVIEW - 03
Confirm receiptCheck your receiving wallet
WALLET
Payment confirmation happens in your wallet.
PAYMENT RECIPES
LESS EXPOSURE.
MORE CONTROL.
Invoices, services, and open-source support. Start with a shielded receiving address, then share only the details your payer needs.
HOW IT WORKS
YOU SET THE REQUEST.
Enter your mainnet address. Inspect its receivers. Shielded receiving mode blocks transparent addresses and transparent fallbacks before the request is generated.
THE WALLET PROTECTS.
Share the request directly with your payer. Their compatible wallet reviews the amount, selects the receiving pool, and signs the transaction.
YOU RECEIVE ZEC.
Funds go to the address you supplied. Confirm receipt in your wallet. ZPAID does not hold funds or automatically verify payments.
A CLEAR BOUNDARY
PRIVACY YOU CAN
ACTUALLY INSPECT.
Privacy starts with the receiving address. ZPAID checks its native Zcash receivers before creating a payment request. Your wallet controls the final transaction.
Does ZPAID hold my money?+
No. A request contains your receiving address. You retain your keys, and payment goes to that address. We never ask for your recovery phrase.
Is every payment shielded?+
No. The address and wallet determine the receiver used. Unified addresses can include a transparent fallback. Review the payment path in your wallet.
What can someone see in a payment link?+
Anyone with your request link or QR can read its address, amount, label, reference, and memo. Do not include sensitive details. A memo is encrypted only when included in a shielded transaction.
How do I know I have been paid?+
Check your receiving wallet. This app does not monitor the chain or confirm settlement. Shielded verification needs wallet scanning and authorized viewing information.
Are there payment fees?+
ZPAID does not add a platform fee to the payment request. Your sending wallet calculates applicable Zcash network fees before you approve the transaction.