# ZIP 324: URI-Encapsulated Payments

Status: Draft

Owners: Jack Grigg, Daira-Emma Hopwood, Kris Nuttycombe

Snapshot: a34cfc091434275120ff017c92c3b50d3cef623a

Source date: 2026-10-16T02:56:04+01:00

[Source revision](https://github.com/zcash/zips/commit/a34cfc091434275120ff017c92c3b50d3cef623a)

[Official source](https://zips.z.cash/zip-0324) · [Source file](https://github.com/zcash/zips/blob/a34cfc091434275120ff017c92c3b50d3cef623a/zips/zip-0324.rst) · [Discussion](https://github.com/zcash/zips/issues/421)

## Document parts

[Part 1](https://zips.tools/zip/324) · [Part 2](https://zips.tools/zip/324?part=2)

Reading part 2 of 2. Follow all parts for the complete proposal.

<a id="note-retrieval"></a>

### Note retrieval

Ideally: a lightweight wallet can receive the funds with the assistance of a more powerful node, with minimal information leakage to that node (e.g., using simple lookups queries that can be implemented via Private Information Retrieval). The open question is how to do this given that most practical PIR are for retrieving an index out of an array, not a key from a key value standpoint.

<a id="other-questions"></a>

### Other Questions

Should senders delay admitting a generated transaction by a random amount to prevent traffic analysis (i.e., so the messaging service operator cannot correlate messages with on-chain transactions)?

Consider the behavior in case a chain reorgs invalidates a sent payment. Should we specify a Merkle root or block hash to help detect this reason for payment failure? Or have some servers that maintain a cache of payments that were invalidated by reorgs?

<a id="references"></a>

## References

<a id="publication-blockers"></a>

## Publication Blockers

- Clean up semantics.

- Clean up rationale.

---

1. [Information on BCP 14 — "RFC 2119: Key words for use in RFCs to Indicate Requirement Levels" and "RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"](https://www.rfc-editor.org/info/bcp14)[↩︎](/zip/324#fnref1)

2. [Zcash Protocol Specification, Version 2023.4.0 or later](protocol/protocol.pdf)[↩︎](/zip/324#fnref2)

3. [Android Developer Guides: Handling Android App Links](https://developer.android.com/training/app-links)[↩︎](/zip/324#fnref3)

4. [Apple Xcode Documentation: Allowing apps and websites to link to your content](https://developer.apple.com/documentation/uikit/inter-process_communication/allowing_apps_and_websites_to_link_to_your_content)[↩︎](/zip/324#fnref4)

5. [Microsoft Universal Windows Platform Documentation: Enable apps for websites using app URI handlers](https://docs.microsoft.com/en-us/windows/uwp/launch-resume/web-to-app-linking)[↩︎](/zip/324#fnref5)

6. [ZIP 321: Payment Request URIs](/zip/321)[↩︎](/zip/324#fnref6)

7. [Uniform Resource Identifier (URI): Generic Syntax](https://tools.ietf.org/html/rfc3986)[↩︎](/zip/324#fnref7)

8. [Zcash Protocol Specification, Version 2023.4.0 or later](protocol/protocol.pdf)[↩︎](/zip/324#fnref8)

9. [Zcash Protocol Specification, Version 2023.4.0 or later](protocol/protocol.pdf)[↩︎](/zip/324#fnref9)

10. [Zcash Protocol Specification, Version 2023.4.0 or later](protocol/protocol.pdf)[↩︎](/zip/324#fnref10)

11. [Zcash Protocol Specification, Version 2023.4.0 or later](protocol/protocol.pdf)[↩︎](/zip/324#fnref11)

12. [Zcash Protocol Specification, Version 2023.4.0 or later](protocol/protocol.pdf)[↩︎](/zip/324#fnref12)

13. [ZIP 321: Payment Request URIs](/zip/321)[↩︎](/zip/324#fnref13)

14. [ZIP 321: Payment Request URIs](/zip/321)[↩︎](/zip/324#fnref14)

15. [FinCEN Guidance FIN-2019-G001. May 9, 2019. Application of FinCEN’s Regulations to Certain Business Models Involving Convertible Virtual Currencies](https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20Guidance%20CVC%20FINAL%20508.pdf)[↩︎](/zip/324#fnref15)

## Citation relationships

Cites: [ZIP 32](https://zips.tools/zip/32), [ZIP 321](https://zips.tools/zip/321)

Cited by: None