Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.request.network/llms.txt

Use this file to discover all available pages before exploring further.

The Request Network Dashboard (dashboard.request.network) is the no-code home for everything you do with Request Network as a receiver: setting up where you want to be paid, generating API credentials, sending and receiving payment links. Sign in with an EVM or Tron wallet — no email, no password.
Dashboard home with active payment destination

​
Sign-in

The login screen offers EVM and Tron as parallel tabs.
Connect MetaMask, Coinbase Wallet, or WalletConnect. Sign the SIWE message when prompted to start your session.
Dashboard sign-in (EVM)
Your session is a wallet-bound cookie with a 15-minute idle timeout, shared across dashboard.request.network, auth.request.network, and api.request.network — sign in once and you’re authorised across all three.

​
Payment destinations

A payment destination registers where you want to receive payments. It’s a single chain × token × wallet combo, encoded as an ERC-7828 humanReadableInteropAddress.
Create payment destination dialog
Supported chain × token combinations in the Dashboard UI:
ChainTokens shown in the UI
Ethereum, Optimism, Base, Polygon, BSCUSDC, USDT
Arbitrum OneUSDC, USDT0
TronUSDT (TRC-20)
Sepolia (testnet)FAU, USDC, USDT
The underlying API also supports USDC on Tron and additional tokens on some chains; the Dashboard UI exposes the curated set above. To use a token not in the UI, create the destination via the Auth API directly.
You can switch your active destination at any time via Manage Destination → Update Receiving Route.

​
Client ID management

Client IDs are the credential the Dashboard (and your own apps) use to call the API on your behalf. The Dashboard’s Generate New Client ID dialog collects:
  • A label (display name)
  • Allowed Domains — one or more HTTPS origins (leave empty for backend-only Client IDs)
Manage destination and Client IDs
Generate Client ID dialog
Advanced fields — feePercentage, feeAddress, operatorWalletAddress, payeeDestinationId, defaultPreApprovalExpiry, defaultAuthorizationExpiry — are only configurable via the Auth API. Existing Client IDs created from the Dashboard can be edited (allowed domains) or revoked from the same screen. For the full field reference, see Client ID Management.

​
Get Paid

The Get Paid tab is your incoming-payments view. Create a request — amount, currency, optional reference and payer identifier — and the Dashboard generates a pay.request.network link to share.
Get Paid list
Each request shows status (Pending / Paid), the on-chain transaction hash once paid, and a copyable payment URL. Works identically for EVM and Tron destinations.
Request detail with payment link

​
Pay (outgoing)

The Pay tab is your outgoing-payments view. Create a single-recipient payout, sign the resulting transaction, and the Dashboard tracks settlement.
Pay list (outgoing payouts)
The Dashboard UI today supports single-recipient payouts only on both EVM and Tron. For batch payouts (one signature, many EVM recipients), use the API directly — see Batch payouts.

​
What the Dashboard does not do

  • It is not an admin / merchant control panel for downstream platforms — it’s a user dashboard for your own wallet.
  • It does not manage webhooks today — webhooks are managed via the Auth API.
  • It does not host the payer-side checkout — that’s Secure Payment at pay.request.network.

​
Open the Dashboard

Open dashboard.request.network

Sign in with your EVM or Tron wallet to start.

Quickstart

End-to-end walkthrough using the Dashboard.

Secure Payment

The payer-facing companion at pay.request.network.