Concepts
Payment requests
A payment request is the opposite of a payment link. The recipient makes it, sends it to whoever should pay, and nothing moves until that person confirms. The link cannot be spent.
Format
https://<app>/r#v1.<chainId>.<pool>.<base64url(tokenId 1B ‖ amount 12B ‖ address 64B ‖ label)>
- The fragment is the whole request. Browsers do not send it to the server, so a link preview never includes the address, the amount or the note.
tokenId0 andamount0 mean the payer chooses. An amount without an asset is rejected.- The address is the recipient's ordinary
batin1address: owner public key and view public key. It is not a spend key and not a view key. - The label is at most 48 bytes, for the human holding the link. It is not encrypted into the note and it is not checked on-chain. Don't put anything in it you wouldn't put in the chat message next to the link.
Making a request does not touch the chain. There is no proof and no gas.
Paying one
Opening the link shows the note and the amount they asked for. The payer confirms, and can pay a different amount. The wallet then does a normal private transfer to that address: two nullifiers, two commitments, sponsored on testnet. Sei does not learn the amount, the asset, the sender or the recipient.
The recipient sees the note the next time their app syncs. There is no on-chain "this invoice was paid" flag. If the request named an asset and an amount, the app on the phone that created it marks that request paid when a new note of that size arrives, ignoring notes the phone itself created (including a deposit it submitted from a connected wallet). A note above the last leaf this phone had already seen still counts, including one that arrives in the same sync. Two open requests for the same amount are left unmarked, because the app will not guess. A payer who sends a different amount is not matched.
What a request does not hide
Anyone you send the link to learns your address, and the amount and note if you set them. Your address is the same on every request from one wallet, so two requests shown to the same person are obviously the same recipient. That person still cannot read your balance or your other notes, and a chain observer who never saw the link learns nothing about either of you.
A request is not cash. Forwarding it lets more people pay you. It does not let them take money out.
Source: apps/web/content/docs/payment-requests.md