POST request to your endpoint containing the event payload.
Method: GETURL:
https://app.kulmipay.com/api/v1/webhooks/
Webhook endpoints must use HTTPS. Endpoints that cannot be reached or return non-2xx responses repeatedly will be automatically disabled after reaching the failure threshold.
Code example
cURL
Webhook object
Unique identifier for this webhook configuration.
The HTTPS URL where Kulmi Pay sends event payloads. Must include a valid, verifiable TLS certificate.
Whether this webhook is currently active. Kulmi Pay sets this to
false automatically when the endpoint reaches the failure threshold.When
true, this webhook receives notifications whenever a collection invoice changes state (for example, when a payment completes or fails).When
true, this webhook receives notifications for disbursement (send money) state changes.When
true, this webhook receives notifications when a chargeback or reversal is processed on your account.When
true, this webhook receives notifications when an intra-wallet transfer is completed.When
true, this webhook receives notifications when a subscription status or billing cycle changes.The number of consecutive delivery failures for this endpoint. Kulmi Pay will warn you by email when this reaches 50% of the failure threshold, and disable the endpoint at 100%.
ISO 8601 timestamp of when this webhook was registered.
ISO 8601 timestamp of the last configuration update.
Example response
The
challenge secret used to verify incoming webhook payloads is not returned by this endpoint. Store your challenge secret securely at the time you register the webhook. Use it to validate the X-Kulmi Pay-Signature header on incoming requests.Verifying webhook payloads
Kulmi Pay signs every outgoing webhook request. Verify the signature before processing any event to confirm the payload originated from Kulmi Pay and has not been tampered with. Use yourchallenge secret to compute an HMAC-SHA256 signature of the raw request body and compare it against the value in the X-Kulmi Pay-Signature header.