This guide walks through the end-to-end flow for receiving payments via the Request Network: creating a payment destination in the Dashboard, generating a Client ID, setting up webhooks for payment notifications, and creating a payment link — all using your wallet session.
The flow involves three services:
dashboard.request.network) — Sign in with your wallet and create payment destinationsauth.request.network) — Create Client IDs via the Scalar API docsportal.request.network) — Set up webhooks for payment notificationsapi.request.network) — Create payment links (secure payments) via the Scalar API docs┌──────────────────────┐
│ 1. Sign in with │ dashboard.request.network
│ wallet │
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ 2. Create Payee │ dashboard.request.network
│ Destination │
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ 3. Create Client ID │ auth.request.network/open-api
│ (Scalar API docs) │
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ 4. Set up Webhook │ portal.request.network
│ │
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ 5. Create Secure │ api.request.network/open-api
│ Payment (link) │
└──────────────────────┘
Your wallet session cookie (session_token) is shared across dashboard.request.network, portal.request.network, auth.request.network, and api.request.network — so signing in once on the Dashboard gives you access to the Portal and API docs as well.
session_token cookie in your browser that is shared across Request Network services.Note: Wallet sessions expire after 15 minutes. If your session expires during the following steps, return to the Dashboard and sign in again.