Where it goes

On a sent transaction’s detail screen, next to Share or View on explorer: Prove this payment. Only for transactions this wallet sent from Orchard or Ironwood notes.

The flow

  1. Choose what to show. Default: outputs sent to someone else, with memos. Options: hide the memos, add a message (an invoice number, or a request link that fills in its challenge).
  2. Confirm. One screen listing the transaction, the outputs, the message and any extra disclosure in plain words.
  3. Share the link, or save it as a file.

The calls

Wallets on the Zcash Android or iOS SDK get the same two calls from Swift and Kotlin bindings: prepareReceipt(dbPath, …) and signPrepared(…) (crates/zceipt-ffi).

Composing from a wallet

The relationship proofs reuse the same prepared material. A wallet that offers Prove this payment can add Prove I’m one donor (a payer tag), or issue delegated receipts to a back office, without new key handling.

Building on stock orchard

zceipt-core without the orchard-ext feature builds on stock orchard 0.16 and gives receipts, batches, source proofs, sign-in, payment requests and proof of funds. Claim tags need the patched crate. scripts/check-stock-orchard.sh builds the stock profile and runs real testnet receipts through it.