Billing events adapter (Webhooks)
Emit subscription lifecycle events to your backend via webhooks.
Early access
•
Webhooks
Outcomes
Your backend receives clean lifecycle events for subscriptions
Renewals, cancellations, and failures are represented consistently
Events are safe under retries and idempotent by execution window
Easy to drive entitlements, invoicing, and notifications off events
How it works
Subscribe to webhook endpoints for the events you care about
When execution state changes, the adapter emits events to your backend
Your system processes events and updates entitlements, emails, or billing logic
Capabilities
Subscription lifecycle events (created, renewed, cancelled, paused, expired)
Failure and retry signals with clear reasons
Idempotent delivery using stable event identifiers
Signed payloads to verify authenticity
Simple filtering by merchant, plan, or adapter scope
FAQ
what events do you emit?
Core lifecycle events such as subscription created, renewed, paused, cancelled, expired, and execution failed. The exact set can expand as more adapters go live.
Are events idempotent?
Yes. Events include stable identifiers so your backend can safely dedupe and retry processing.
How do you secure webhooks?
Payloads are signed so you can verify authenticity. Use the signing key to validate requests before processing.
Do you support retries?
Yes. Delivery is retryable and designed to behave predictably under failures.
Is this only for subscriptions?
No. The same event model can be extended to other execution types such as fees and just in time transactions.