Private payments. Finally practical.
The payment infrastructure for Zcash's NU7 era.
Create invoices, accept ZEC from a Zcash wallet, a Solana wallet or a card, and verify payments through a single API. Built for Zcash's new 25-second block targets.
One chain shows everything. One shows nothing.
Four sentences, no jargon. The honest table of who can see what is further down.
A Solana payment is a postcard
Sender, amount, receiver and time are written on the outside. Anyone can read them, today or in ten years.
A shielded payment is a sealed envelope
The chain records that an envelope was posted. Who sent it, how much is inside and who it is for stay inside.
The block is the collection
Zcash collects the post in blocks. Since the NU7 upgrade the target is one every 25 seconds, down from 75.
The viewing key opens one envelope
The receiver holds a key that reads only their own payments. It can prove a payment without moving any money.
Watch a payment go dark.
Left: real transfers settling on Solana right now, with everything attached. Right: Zcash's shielded pool, every private note ever made. The ring fills until the next block lands. Run the crossing to see what a payment loses on the way over.
—
| Sender | Receiver | USDC |
|---|
| Block | Wait | Notes | Sender | Amount | Receiver |
|---|
Private for the receiver. Not for everyone.
What each party can read depends on how the invoice is paid. Orange is public or shared. Gold stays sealed.
| Who | Paid from a Zcash wallet | Paid from a Solana wallet | Paid by card |
|---|---|---|---|
| Anyone with a block explorer | Shielded address: only that a note was created. Public (t1) address: sender, amount and receiver. | The payer's wallet, the amount and the time, on Solana, for good. | Nothing on any chain. |
| The route (NEAR Intents) | Not involved. | Both ends and the amount. Refunds may return to a public address. | Not involved. |
| Stripe and the card network | Not involved. | Not involved. | The payer's identity, card and amount. |
| This site | The invoice as typed: amount, note and receiving address. It holds no funds and no keys. | ||
| The receiver | Their own payment, with their viewing key. | ||
Pick an amount. The route answers.
Price it in dollars. The payer chooses how to pay: scan with a Zcash wallet, send from a Solana wallet, or use a card. The receiver's address is the only thing you need.
Three calls. No keys held.
The API creates invoices, returns the pay links and QR codes, and reports what both chains say. It never takes custody: payments go wallet to wallet, or through the route.
Create an invoice
Amount in dollars, a note, the receiving address.
Read it back
Pay link, QR, status and the methods on offer.
Read the chains
Block height, measured block time, pool size, live transfers.
Reads both chains
Zcash blocks and Solana transfers are read as they land. Every number on this page is a chain read.
Zcash wallet pay
Invoices carry a standard Zcash pay link and QR. The payment goes straight to the receiver.
Solana wallet pay
Quotes are live. Deposit addresses are issued only when live payments are switched on.
Card pay
The card checkout runs as a simulation: no card details, no charge. A real card payment would settle in dollars, not ZEC.
Invoices to a public (t1) address mark themselves paid. Not built yet: seeing a shielded payment arrive (needs the receiver's viewing key) and the lens on real payments.