Skip to content

Get paid with a link

A payment link is a hosted page where the payer connects their wallet and pays. You don’t need their address in advance.

Set REQUEST_DESTINATION_ID to your dashboard Route ID. The route decides the network, the token and the wallet that gets paid.

Send me a payment link for 250 USDC for the logo work.

The assistant calls create_payment_link and replies with:

Payment link created for 250. Send this to the payer:
https://pay.request.network/?token=v1.XjC8…
Invoice ID: 01e273ec… (use check_invoice to see when it's paid).

Send the link however you like: email, chat or a QR code.

Payment links can’t carry a name or note on Request Network, so the server keeps a small private notebook on your computer. Say who you’re billing and what for:

Bill Acme 500 USDC for the logo.

Later, ask by name:

Has Acme paid?

Send me Acme’s link again.

The assistant gives you the link to send. It never sends messages itself. See Security for where the notebook lives.

Has the logo invoice been paid?

Each route is one wallet, one network and one token. To be paid in several, create a route for each in the dashboard, generate a Client ID on each, and list them in REQUEST_ROUTES:

"env": {
"REQUEST_ROUTES": "0xYou@eip155:8453#AAAA1111:0xUSDC=cli_base, 0xYou@eip155:42161#BBBB2222:0xUSDT=cli_arb"
}

Each entry is a Route ID, then = and that route’s Client ID. If you also set REQUEST_CLIENT_ID, routes without their own Client ID use it. The first route is the default.

Then just say what you want:

What can I get paid in?

2 route(s):
1. USDC on Base to 0xYou… (default)
2. USDT on Arbitrum to 0xYou…

Payment link for 50 USDT.

The assistant picks the Arbitrum route. If more than one route matches, like “USDC” when you take USDC on two networks, it asks which network instead of guessing. list_invoices and check_invoice cover invoices from every route.