Tenant webhook setup

Stripe inbound delivery is not an app integration endpoint. It is part of the platform setup that allows Licenzy to turn Stripe billing events into entitlement state.

• Register Licenzy as the Stripe destination in each mode you operate.
• Keep webhook mode aligned with the same Stripe credentials, products, and API keys used elsewhere in setup.
• Your application should not proxy or replay inbound Stripe webhook events.

Subscribe the tenant webhook to the full event set Licenzy uses to finalize purchases and update runtime state:

• checkout.session.completed
• checkout.session.expired
• customer.subscription.created
• customer.subscription.updated
• customer.subscription.deleted
• invoice.payment_succeeded
• invoice.payment_failed
• charge.refunded
• charge.dispute.created
• charge.dispute.closed
• refund.created
• refund.updated

Setup tells Stripe where to send billing signals. The runtime and event architecture docs explain what Licenzy does with those signals after they arrive.

• Webhook and event architecture for the overall runtime model.
• Inbound Stripe lifecycle for the webhook processing boundary.