Guidelines
To implement webhooks in your application, follow these essential steps:1
Configure Your Endpoint
Create a publicly accessible HTTP endpoint in your application that can receive POST requests. This endpoint must be available over HTTPS and return a 2xx status code to acknowledge receipt of webhook events.
Your webhook endpoint must be publicly accessible. For local development, use tools like ngrok to expose your local server.
2
Register with Gnosis Pay
Contact your Gnosis Pay partner manager or technical support team to register your webhook endpoint URL. Provide the complete HTTPS URL where you want to receive webhook notifications.
Setup Time: Webhook configuration typically takes 1-2 business days after you provide the required information.
3
Receive and Verify Events
When events happen in the Gnosis Pay system, we’ll send HTTP POST requests to your webhook endpoint with event data and cryptographic signatures.All webhooks include cryptographic signatures using Ed25519 asymmetric cryptography:Retrieve the public key for signature verification from our API:
X-Webhook-Timestamp
: Unix timestamp when the webhook was sentX-Webhook-Signature
: Base64-encoded Ed25519 signature
Always verify webhook signatures before processing events. This ensures
the webhook originated from Gnosis Pay and hasn’t been tampered with.
cURL
4
Parse and Process Event Data
Extract the Handle each event type appropriately in your application. Since we send complete entity data, you typically won’t need additional API calls to get the full context.
eventType
and data
fields from the webhook payload. The eventType
identifies what happened (e.g., user.created
, kyc.status.changed
), while data
contains the complete entity information.Process events idempotently to handle potential duplicates, and implement proper error handling and logging for monitoring.
Retry Policy: If your webhook endpoint returns a non-2xx status code, we’ll retry delivery up to 3 times with exponential backoff (1 minute, 5 minutes, 15 minutes).
Timeout: Your webhook endpoint must respond within 30 seconds. Requests that exceed this timeout are considered failed and will trigger our retry mechanism.