Connect Stripe to Licenzy for checkout

Your app does not call stripe.checkout.sessions.create directly in the Licenzy integration flow. Instead, your backend calls Licenzy runtime APIs and Licenzy uses the Stripe credentials stored in the portal.

Licenzy sits on top of Stripe for checkout, entitlement state, access checks, and usage consumption. Stripe still collects payment. Licenzy uses the saved connection to create Stripe Checkout internally when your backend calls POST /v1/checkout/session.

• Test Stripe keys and test webhook secret belong to test mode only.
• Live Stripe keys and live webhook secret belong to live mode only.
• Price IDs must match the same mode as the product and API key.

A reliable setup keeps credentials, products, price IDs, and runtime keys aligned in the same environment before the first checkout request is sent.

1. Connect Stripe credentials and webhook secrets in test mode first.
2. Create or verify the matching Licenzy products for the Stripe price IDs you plan to sell.
3. Create a test Licenzy API key and store it only in backend secrets.
4. Call checkout from your backend using a product code from the same mode.
5. Repeat the setup with live Stripe credentials, live products, and a live API key only when you are ready to follow the go live checklist.

• Using a live Licenzy API key with a test Stripe price ID.
• Creating a product in one mode and trying to buy it from the other mode.
• Saving Stripe credentials without the matching webhook secret for that mode.
• Passing a Stripe price ID directly to runtime checkout instead of a Licenzy product code.
• Calling Stripe Checkout directly and expecting Licenzy entitlement state to update from that separate flow.

• Checkout session for the backend runtime request Licenzy turns into Stripe Checkout.
• Products for mapping product codes to Stripe price IDs.
• Full integration example for the complete setup-to-access flow.