Create a payment request
A payment link carries the whole request inside the link itself — your address, the token, the network, the amount. There is no account and no invoice database: whoever opens it sees the request and pays you straight from their own wallet. That is also why the links are long, and why we never see what you send.
- Pick the network and token. The payer needs that token on that exact network — USDC on Base is not the same asset as USDC on Polygon, and a payment to the wrong chain is gone.
- Set the receiving wallet. “Use Connected” fills it from your wallet, which beats pasting an address you can mistype.
- Add an amount and a label to prefill them. Both optional — leave the amount blank and the payer chooses it.
- Choose how to seal it using the buttons at the bottom, then share the link or the QR code.
Encrypting this link for one person?
Only needed for Create Encrypted Link. Ask the recipient for their public key — they generate one under Generate Key and it is safe to send in the clear. Skip this for a plain or signed link.
- Create Payment Link — plain and instant, no wallet popup. But anyone who receives it can edit the address before forwarding it on, and the next person cannot tell. Use it when you hand the link over yourself.
- Create Signed Link — recommended. Your wallet signs the request, so the payment page detects any change to the address, amount, token or network. It is a signature, not a transaction: free, instant, no gas.
- Create Encrypted Link — for one named recipient. Paste their public key above and only they can read the amount and description. Everyone else, us included, sees nothing but noise.
Scan to open
Page QR opens the payment page — any
phone camera reads it.
Wallet QR is an EIP-681 code: scanned
from inside a wallet app it jumps straight to a prefilled transfer.