This guide walks through the end-to-end flow for receiving payments via the Request Network: creating a payment destination and Client ID in the Dashboard, registering a webhook 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, create payment destinations, and generate Client IDsauth.request.network) — Programmatic alternative for Client IDs, and the home of webhooksapi.request.network) — Create payment links (secure payments)┌──────────────────────┐
│ 1. Sign in with │ dashboard.request.network
│ wallet │
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ 2. Create Payee │ dashboard.request.network
│ Destination │
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ 3. Create Client ID │ dashboard.request.network
│ │ (or auth.request.network/open-api)
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ 4. Register Webhook │ auth.request.network/open-api
│ │ (POST /v1/webhook with x-client-id)
└──────────┬───────────┘
│
▼
┌──────────────────────┐
│ 5. Create Secure │ api.request.network/open-api
│ Payment (link) │
└──────────────────────┘
Your wallet session cookie (session_token) is shared across dashboard.request.network, auth.request.network, and api.request.network — so signing in once on the Dashboard gives you access to the 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.