If you have webhooks configured when an event occurs, Kustom sends an HTTP POST request to a URL you have configured.
You can use these notifications to automate workflows such as triggering fulfillment on a new order or updating your system when a refund is issued.
For full technical details on payload format, signature verification and retry behavior, see the Webhooks documentation.
Setting up a webhook destination
Open Kustom Portal and sign in.
Navigate to Integrations in the left menu and select Webhooks.
Click Start listening to webhooks.
Step 1: Select events
Choose which events should trigger notifications to your endpoint. You can select individual events or use Select all events to subscribe to everything.
The available events are:
dispute.created | A new dispute has been opened on an order. |
dispute.updated | An existing dispute has been updated. |
refund.created | A refund has been issued on an order. |
capture.created | A capture has been made on an order. |
order.created | A new order has been created. |
ipp.session.created | A new in-person payment session has been created. |
ipp.session.activated | An in-person payment session has been activated. |
ipp.payment.failed | An in-person payment attempt has failed. |
ipp.session.finalized | An in-person payment session has been finalized. |
ipp.session.cancelled | An in-person payment session has been cancelled. |
Click Continue when done.
Step 2: Configure destination
Enter a Name for the destination. This is a short label to help you identify it later.
Enter your Endpoint URL. HTTPS is required.
Click Continue to confirm and create the destination.
Signing secrets
When you create a webhook destination, Kustom generates a signing secret for it. Your endpoint should use this secret to verify that incoming requests originate from Kustom.
You can view and rotate the signing secret from the destination settings in the Portal. During a rotation, Kustom signs with both the old and new secret for up to 10 minutes while caches clear.
For instructions on verifying signatures, see the Webhooks documentation.
Retries
If your endpoint does not respond with a successful status code, Kustom retries delivery automatically using an exponential backoff strategy. Retries continue for up to 3 days.
Each event has a stable ID. Use it to safely detect and discard duplicate deliveries if your endpoint receives the same event more than once.
Troubleshooting
If the Webhooks tab is not visible under Integrations, you may not have the required permissions.
Contact your account admin to review your access level via User Management in the Portal.