Webhooks

Cari Finance does not send webhooks to your server yet. You cannot register an endpoint, there is no screen for it in the dashboard, and no signed events are sent.

What this means for your integration

• To learn the result of a payment, read it. The checkout widget reports the result to your page (onSuccess with the charge_id). Your server can then check the charge with GET /charges/{id} before it fulfils an order, and should do so rather than trust the browser.
• If a payment is still being processed (the widget reports payment_processing, HTTP 202), look at GET /charges/{id} or the dashboard until it settles. Do not ask the customer to pay again.
• For refunds, disputes and payouts, poll the relevant list route or look in the dashboard.

What you may have seen elsewhere

Cari Finance does receive webhooks from its card processor (Stripe). That is how the platform learns the outcome of a card payment. It is internal to the platform and is not a feature you can use or subscribe to.

When outbound webhooks are added they will be announced here, with the event types and the way each request is signed. Until then, please do not build against a webhook format.