A decimal string, with a full stop and no thousands separator. Leave it empty and the payer enters the amount.
Travels with the payment so you can match it later. It is carried in the clear: reconciliation is private because you query your own ledger, not because the reference is hidden.
Required, and filled in for you thirty days out. A request with no deadline stays payable forever, which is where replay and double payment come from, so a conforming wallet refuses one. Change it to whatever suits the invoice.
The payee party, as the ledger spells it. Opaque to Payvol.
There is nothing to create. The artifact exists as soon as it is described, with no server and no session, which is the whole of what makes it portable.
Encoded in your browser. Nothing is sent anywhere, and no key is used to make a request.
Example values — edit the amount, reference and expiry before sharing this. The recipient is yours to set: it is the one field a mistake cannot be undone in.
Works printed on paper, in an email, or written to an NFC tag. No server, no session.
The bytes themselves
canton: URI
Canonical JSON
Select instrument
Nothing matches that.
About Request
Describe a payment you want to receive and watch it become a canton: URI, canonical JSON, a digest and a QR code.
No wallet needed. No wallet, and no server. The artifact exists as soon as it is described, and every value on the screen is computed in your own browser.
What this does not tell you
- A request is an ask, not a payment. Building one moves nothing and reserves nothing.
- The recipient and instrument are yours to supply. They come from the party and registry you already use; Payvol does not look them up and cannot tell you whether a party exists.
- Nothing is stored or sent. Close the tab and the request is gone unless you copied it out.