How to prompt your AI assistant to integrate stablecoin payments in under ten minutes

Request Network stablecoin payments — integration prompt

Step 0 — Detect the environment. Before writing anything, identify which of these this project is, since "server endpoint" means something different in each:

- A. Conventional server app — has its own backend framework (Express, Django, Rails, Next.js API routes, etc.) and a database you control. Implement normal server routes.
- B. AI-agent-managed site — a CMS/site edited by an agent via API-level access, with no dedicated app server (e.g. WordPress via REST + Code Snippets). Use that platform's own extensibility mechanism as the "endpoint" — e.g. a custom REST route registered in a snippet — instead of assuming a server that doesn't exist.
- C. No-code/low-code builder (Lovable, Bubble, Webflow, Replit Agent, etc.) — use that platform's own backend primitive (Lovable Cloud/Supabase edge functions, Bubble backend workflows), not a conventional file-based backend.

If none of these cleanly fits, ask before picking a default.

1. Checkout endpoint (any environment). Expose one endpoint/function via whatever mechanism the environment provides. It must run server-side — the client never sees the client ID or secret. It accepts { amount, referenceId } and calls https://api.request.network/v2/secure-payments with:
- requests: [{ destinationId: RN_DESTINATION_ID, amount: String(amount) }]
- redirectUrl: this site's URL with ?paid=1 appended
- redirectLabel: label for RN's "go back" button
- webhookUrl: this environment's webhook endpoint (below)
- reference: referenceId, only if provided
- Header x-client-id: RN_CLIENT_ID

Returns { url: data.securePaymentUrl }.

2. Webhook receiver (any environment). Expose a second endpoint/function that:
- Reads the raw, unparsed body. In frameworks that auto-parse JSON (Express, etc.), exempt this route from that middleware. In environments where the raw body is always available regardless of parsing (e.g. WordPress's WP_REST_Request::get_body()), skip that workaround entirely — check what your environment actually does first.
- Verifies x-request-network-signature against HMAC-SHA256(RN_WEBHOOK_SECRET, rawBody) with a constant-time comparison (crypto.timingSafeEqual / hmac.compare_digest / hash_equals, per language) — strip a sha256= prefix if present.
- Responds 200 immediately; defers processing where the environment supports it (fastcgi_finish_request(), a queue/background job); where it doesn't, keep the post-response work trivial rather than blocking on it.
- Parses totalAmountPaid, currency, txHash, network, paymentReference, explorer (a ready-made explorer link — use it directly, don't rebuild it).
- Logs/handles the payment in whatever this environment's actual persistence layer is (its database, a custom table, a CMS custom post type, a no-code data collection) to update order/access status.

3. Frontend checkout widget. Using the project's existing stack and styling only — no new framework or dependency:
- Floating action button → checkout modal.
- Preset amount chips (e.g. $5/$10/$25), one active by default; typing a custom amount clears chip selection.
- Optional reference/description input, max 120 chars.
- Submit calls the checkout endpoint, opens the returned url in a new tab, closes on success, shows inline error otherwise.
- Closes on backdrop click, close button, and Escape.

4. Frontend success confirmation. On load, if ?paid=1 is present, show a thank-you message; on dismissal, strip the param via the environment's history/URL API without a full reload.

Secrets. RN_CLIENT_ID, RN_DESTINATION_ID, RN_WEBHOOK_SECRET — store in whatever this environment's real secret surface is (.env + server env vars, the CMS's snippet/constant, the no-code platform's secrets panel). Never paste real values into the agent conversation.

CSP. Only relevant if a CSP header already exists and the browser calls api.request.network directly. If the call is proxied through your own server/function (required anyway, to keep the client secret off the client), the browser never talks to that host and no CSP change is needed.

Before writing code: state which environment (A/B/C) this is, the concrete "endpoint" mechanism for it, and where the three secrets will actually live — then wait for confirmation, since this wires up real payment collection.

Constraints: match existing language/framework/styling conventions, no new frontend dependency, no unnecessary comments, the redirect field is redirectUrl not returnUrl.