POST requests. See Webhook events for the full catalog of 11 events.
1. Register an endpoint
Dashboard (recommended)- Open Conexiones → tab Webhooks salientes (sandbox or production).
- Enter HTTPS URL and select events (all 11 types available).
- Copy the signing secret shown once at creation.
clm_*_sbx_* keys.
API (optional): GET/POST /api/v1/integrations/merchant-webhooks with dashboard session JWT — same event list as the UI.
2. Sandbox vs production
Assess on sandbox keys triggers sandbox webhooks only.
3. Understand the delivery
Body:
4. Verify the signature
HMAC_SHA256(secret, "<timestamp>.<rawBody>") → header t=...,v1=<hex>. Verify the raw body before JSON parse.
5. Handle the event
Monitor deliveries
Conexiones → Monitor → Entregas webhook salientes shows recent attempts, HTTP status, and retry state.Best practices
Verify against the raw body
Verify against the raw body
Read raw text first, verify, then parse JSON.
Respond quickly
Respond quickly
Return
2xx within a few seconds; use a queue for heavy work.Be idempotent
Be idempotent
Duplicates happen — key on
session_id + event or case_id.Subscribe narrowly
Subscribe narrowly
Start with
transaction.blocked, transaction.created, and fraud.detected; add dispute events when your chargeback workflow is ready.