docs: document the secure_payment.user_event webhook

[rodrigopavezi]

Part of REQ-291

Documents the new secure_payment.user_event webhook.

Implementation: RequestNetwork/request-api#1139 · UI: RequestNetwork/request-secure-payment#550
Merge after the API PR ships, so the docs don't describe an event platforms aren't receiving yet.

What's documented

• api-reference/webhooks.mdx — a "Secure Payment Page Events (payer funnel)" section: the event table row, the three userEvent values (wallet_connected, payment_sent_to_wallet, payment_approved_in_wallet), a payload example, and a note on field semantics
• api-features/webhooks-events.mdx — new category row, and the event-type count bumped 12 → 13

Signature verification, delivery headers and retry behaviour are unchanged, so the existing guidance on this page applies as-is and isn't restated.

Points worth a reviewer's eye

• The payload example was checked field-by-field against what the service actually emits, including optionality.
• The note draws a deliberate line between server-derived fields (securePaymentToken, requestId/requestIds, orchestratorId, timestamp) and client-reported telemetry (occurredAt, properties) — integrators should not treat properties as authoritative, since it originates in the payer's browser.
• It also states that wallet addresses appear only as sha256 hashes, which holds for these three events.

Scope is limited to this one event; other currently-undocumented events (client_id.linked, secure_payment.access_rejected, kyt.screening.completed) are left alone.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
request-network	🟢 Ready	View Preview	Aug 6, 2026, 12:31 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[greptile-apps]

Greptile Summary

The PR documents the new secure_payment.user_event webhook and updates the previously stale complete-event catalogs.

• Adds the event’s payer-funnel semantics, supported userEvent values, payload example, and trust boundaries.
• Updates the quickstart and reconciliation guide to include the thirteenth event.
• Adds an illustrative reconciliation branch that records funnel telemetry without treating it as settlement.

Confidence Score: 5/5

The PR appears safe to merge after the dependent API implementation ships.

No blocking failure remains; the previously reported stale quickstart and reconciliation catalogs now both include secure_payment.user_event.

Important Files Changed

Filename	Overview
api-features/webhooks-events.mdx	Updates the catalog count and adds the Secure Payment Page event category and payer-funnel use case.
api-reference/webhooks.mdx	Documents the new event’s values, payload, delivery behavior, and distinction between server-derived and client-reported fields.
use-cases/quickstart.mdx	Adds secure_payment.user_event to the quickstart’s supported-event table and clearly identifies it as non-settlement telemetry.
use-cases/webhook-reconciliation.mdx	Completes the thirteen-event catalog and adds a reconciliation example that records funnel steps without changing payment state.

_{Reviews (2): Last reviewed commit: "docs: add the new event to the reconcili..." | Re-trigger Greptile}