Subscription collection succeeded
your notification URLBuild with AI 1 package
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 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.
Raised when an individual collection succeeds. Beta, subject to change.
Delivered by Svix, with svix-id, svix-timestamp and svix-signature headers. Verify the signature with the webhookWebhook A URL of yours that Ozow calls when something happens, rather than you polling to find out. The call carries no credential of yours and arrives at a public URL, so authenticate it before acting on it: a hash field on the Payments API, a Svix signature on One API.'s secret before acting on the contents.
Authentication
Ozow sends no credential with this call, so this check is the only thing standing between a real delivery and a stranger’s. Verify the delivery signature before acting on the contents: your notification URL is public, and anyone can post to it.
Payload
application/json
typestring requiredThe event type the subscription was created for.
timestampstring date-time requiredWhen the event was raised.
dataany of requiredWhat the subscription's message type decides. A
thinsubscription receivesWebhookEventData, which is every event's default and the only form the subscription events support. Afullsubscription totransaction.completereceivesTransactionCompleteFullData, and torefund.complete,RefundCompleteFullData. Afullsubscription to any of the subscription events receives nothing at all.
Your response
No body.