WebhookEventData
The `data` of a delivery whose subscription asked for `thin`, which is every subscription event and the default for the rest.
Build with AI 3 packages
A build package is every page for one task, with the API operations they use. Copy the prompt into a coding assistant, or hand it the package itself: slim links to each page, full inlines all of them in one document.
- Take a paymentEverything needed to take a payment end to end with One API, from credentials through the hosted page to the webhook that confirms it, and the test cases that prove each outcome before you go live.
- Take a recurring paymentEverything needed to collect from a customer on a schedule with One API, from the consent the customer gives once through to each collection and the webhook that reports it.
- Migrate a payin from the Payments API to One APIEverything needed to move an existing redirect payin onto One API, with the legacy guide and its One API counterpart side by side.
Fields
idstring uuid requiredWhat the event is about: the transaction, the refund, or the subscription.
statusstring requiredThe outcome. The values differ per event: see the event's own description.
reasonstring nullableThe status message, when there is one to give.
Guides
- Redirect to OzowBuild a redirect payin with One API. Create a payment request, send the customer to Ozow's hosted page, and confirm the result from the webhook.
- Recurring paymentsCollect repeat payments with One API. One consent the customer approves, then merchant-initiated collections that need no further customer action.