Request payment

About this page

Build a payment request, then send the link or the QR code to whoever owes you.

Request: Nothing here is sent anywhere. The request exists only inside the link you copy.
What you send: The expiry is a note to the payer, and the link names no network. Nothing enforces either one — not this screen, not Send, not the chain.
What a request is, and what it is not: It is a link carrying an amount, an asset, an address and your own note. Everything in it is something you typed here; nothing else about you travels with it.

Available · read and reference

A request is a link you hand over yourself: Ryntra writes no invoice, notifies nobody, and cannot tell you when it has been paid.

What a request is, and what it is not

Invoice recordNone — nothing reaches a server

NotificationNone — you send the link yourself

Payment trackingUnavailable — nothing here observes a payment

Payments made elsewhereInvisible — read the address on a block explorer

What would have to exist before this screen could say it was paid

Three things, and this deployment has none of them: a stored request with an identifier, a watcher reading transfers to the recipient address on the network, and a rule matching an observed transfer to one request rather than to any payment of a similar size. The workspace ledger is not a substitute — it records what was sent from this workspace and carries no recipient, so there is nothing in it a request could be matched against. Until all three exist, the only honest thing this screen can say about payment is nothing.