A canton: URI or the canonical JSON. Decoded in your browser by the same package a wallet would use.
REVIEW BEFORE YOU SIGN
Exact identifiers
No wallet is connected. Payvol never holds your key, so paying happens in your wallet.
- One transfer of this amount, once
- No standing permission and no allowance
- Nothing else in your wallet is touched
- Visible to you, the payee, the instrument's registry, and any party that registry adds
Simulated, not submitted
Everything above is computed from the request in your browser. Nothing has been submitted to the ledger, and Payvol holds no key with which to sign it.
About Pay
Paste a request and see exactly what signing it would authorise, before any wallet is asked for anything.
Wallet required. Reading the request needs no wallet. Actually paying it does: the transfer is signed in your wallet, and this page never holds a key.
What this does not tell you
- Decoding a request tells you what it asks for. It does not tell you the payee is who they say they are.
- No balance is checked. A request can be perfectly valid and still be unpayable from your account.
- The signature is checked for shape only. `signatureVerified: not-checked` means nothing was cryptographically verified, and it is not a pass.
- Your wallet does the signing, and it decides what it shows you. Read its screen, not this one, before you approve.
If your wallet says
- Loop says “Action failed: Prepared transaction not found” when you press Confirm.
- In Loop’s settings, switch the theme to Classic and pay again. Seen on DevNet on 19 October 2026 with Loop’s New theme, where Classic worked.
What a wallet must check All four tools Request Verify Match