Skip to main content
A partner has one webhook endpoint. It receives the events of every payment transaction created with the partner’s credential, while the merchant is still with the partner, and its merchants’ status changes.
1

Check for an endpoint

The list holds your endpoint, or is empty when you have none.
2

Create the endpoint

Response
Store signing_secret now: it isn’t shown again. If the answer has no signing_secret, as a replay doesn’t, POST /webhook-endpoints/{id}:rotateSecret issues one. A partner endpoint is always signed. A second endpoint answers 409 PARTNER_WEBHOOK_ENDPOINT_EXISTS: change the one you have with PATCH /webhook-endpoints/{id}, and replace its secret with POST /webhook-endpoints/{id}:rotateSecret.
3

Receive and verify an event

Quidkey posts each event to your endpoint, signed in X-Signature. Verify it with the signing secret before you parse it, as Webhooks shows. De-duplicate on result.id.
4

Read the resource

The event’s result.subject names what it’s about. Read it at the path its id gives, never at a URL taken from the body:
A payment transaction created with a merchant’s own credential reports to the merchant’s endpoints instead. See Integrate as a merchant.