Skip to main content
Use this page to see the shape of incoming webhook payloads for Payment Acceptance events. Every event follows the standard CDP webhook envelope: eventId, eventType, timestamp, and data. For payment session events, data.paymentSession always contains a session summary. For action-triggered events, the corresponding action detail is also included as a sibling field: data.authorization, data.capture, data.void, or data.refund.

Payment session events

Buyer’s funds are held. Ready to capture.

Disbursement events

Disbursement settled onchain.

Mandate events

For mandate events, data.mandate always contains the full mandate. Approval events also include data.approval, and revocation events include data.revocation. The created and canceled events carry only the mandate.
The customer approved the mandate. You can now authorize payments with it.

OAuth and identity events

These events apply to Pay with Coinbase. Keys in data can change over time, so ignore keys you don’t recognize.
The customer signed in or signed up, and consented on Coinbase. Call confirm-link next.
externalReferenceId is the external_reference you sent to init-oauth-session. intent is signup or signin, the flow Coinbase sent the customer to. It’s omitted when Coinbase can’t determine the flow, so don’t require it. signup doesn’t prove that the customer created a new account.
This page shows full incoming webhook request bodies (eventId, eventType, timestamp, data). See the API Reference for complete field definitions.

Webhook Subscriptions

Create and manage webhook subscriptions

Verification

Verify webhook signatures