Private autopay for Zcash subscriptions

Approve a subscription once, with limits you sign. Cadence pays every period for you, shielded end to end. Merchants get paid without ever holding a key that can spend.

Open your Cadence Live on a private Zcash chain
How it works

One approval. Every payment after that is automatic.

You sign a mandate: who, how much, how often, how many times. Your Cadence agent pays each period and refuses anything outside it. Value moves inside Zcash's shielded pool, so the chain records that a payment happened and nothing about who or how much.

01

You approve

Exact amount, period and total, signed once on your device.

02

Your agent pays

Every rule is checked before each payment. Anything else is refused.

03

Shielded pool

Sender, recipient and amount are encrypted on chain.

04

Merchant sees it

Through a viewing key only. It can confirm payment, never spend.

new address every cycleno transparent fallbackrandomised send timerevoke stops it instantly
0

Transparent inputs or outputs

In every Cadence payment. Read back from the chain, not assumed.

1

Viewing key on the server

All a merchant holds. A breach can't move a single zatoshi.

1×

Approval per subscription

Then it runs inside your limits until you revoke.

Privacy

The chain sees a payment. Not your life.

Read back from the chain, a Cadence payment is a shielded transaction and a fee. Everything else stays between you and the merchant you chose.

Anyone watching the chain

Public data for every Cadence payment

Who paid hidden
Who was paid hidden
How much hidden
Links between payments none
What is publicblock, fee, 2 actions

You and your merchant

What each side knows, and nothing more

Youevery payment, every limit
Merchantthis subscription is paid
Merchant can't seeyour balance, other payments
Merchant can't docharge, change, keep charging
Proofone command, rerunnable
Live demo · running on this machine

Try the whole loop in two minutes.

A real Zcash chain, real shielded proofs, real wallets. Demo plans renew every few minutes and blocks are mined whenever a payment needs confirming, so you can watch whole cycles happen.

01 · open first

Your Cadence

The subscriber's app. Review limits, approve, watch payments go out, revoke any time.

02 · then

A merchant's checkout

What a customer sees on a shop's site. Subscribe with Zcash and watch the page confirm the first payment.

03 · and

Merchant dashboard

Revenue, renewals, late payers and webhooks, computed from a viewing key alone.

The two-minute tour

Follow these in order.

  1. Open Cadence. Your shielded test balance is already there.
  2. Open the Private VPN checkout and click Subscribe with Zcash.
  3. Read the limits, approve. The checkout flips to “first payment received”.
  4. Watch it renew every two minutes, in Cadence and on the dashboard.
  5. Revoke. The next renewal is refused. Nothing else can be taken.

Don't trust us. Verify.

Reads every payment back from the node and checks it, with a known-leaky control that must fail.

$ node src/cli.ts agent proof --config /data/home/.cadence-demo/agent/agent.json --rpc http://127.0.0.1:18232

# summary of the report it prints
no transparent inputs ............ PASS
no transparent outputs ........... PASS
amount appears nowhere public .... PASS
every cycle a different address .. PASS
control (leaky tx) ............... caught
ALL CHECKS PASS

Approve once. Stay private for good.

Open your Cadence, then subscribe from a checkout. The whole loop runs on this machine.