SUCCESS, FAILED, PENDING). Your system exposes a callback URL (HTTPS recommended) that accepts a JSON POST. We automatically retry a few times if your endpoint is temporarily unavailable.
What you’ll implement
- A publicly reachable HTTPS POST endpoint (your callback URL).
- Logic to validate the payload and verify its integrity.
- Idempotency handling to avoid double-processing.
- A fast 2xx response on success.
Event lifecycle (high level)
- We process the payment event → transform it into a client-friendly payload →
POSTit to your callback URL. - We treat HTTP 200/201/202 as delivered; non-2xx or timeouts trigger retries (up to a small, configurable maximum).
Note: Webhooks report status; they don’t accept commands. Use the Payments API for actions.
Where to go next
- See Event types for the status/code matrix.
- See Webhook payload for the exact JSON shape.
- See Retries & idempotency for retry rules and deduping.
- See Build your endpoint for handler patterns.
- See Consumer service for the internal queue → delivery flow.