Quickstart

Build your first monetization flow in minutes.

Start in test mode, verify email, choose a project, create a test API key, open Stripe checkout, and verify access from your backend. Licenzy handles the runtime billing flow on top of Stripe, so you do not have to rebuild subscriptions, credits, and access logic yourself.

Start free in test mode. Go live only when you're ready for real payments.

For setup details, see Stripe setup , tenant webhook setup and outbound Licenzy webhooks, plus checkout session. If you are comparing rollout timing, the pricing page explains when to move from test mode to production.

Test API key firstFirst runtime call: checkoutFirst verification call: access
Start freeRead docs
runtime.licenzy.app
createdPOST /v1/checkout/session

Checkout session

subject_refuser_123
Idempotency-Keyrequired
checkout_urlready
modetest
Integration flow

Stripe payment -> Licenzy entitlement -> app access.

Stripe sends billing events to Licenzy through the Stripe inbound webhook. Your first runtime call is POST /v1/checkout/session with an Idempotency-Key. After Stripe webhook processing, your first verification call is POST /v1/access/check.

Step 1

What matters here

Verify email

Unlock setup changes before you create runtime resources.

  • Finish the account step first so the rest of setup is unblocked.
  • This is the cleanest way to keep the first test pass moving.
Create account
First pass

Run the setup once, in the right order.

Keep the runtime rules on one side and the onboarding order on the other. The goal is a clean first verification pass without rebuilding billing logic around Stripe.

Operational notes

Compact rules to keep the first test pass predictable.

Create a test API key first.

Keep Licenzy API keys private in your backend before any runtime call.

POST /v1/checkout/session is the first runtime call.

Include an Idempotency-Key from the start.

POST /v1/access/check comes after Stripe webhook sync.

Run the first verification call only after inbound processing finishes.

POST /v1/usage/consume is only for usage_pack products.

It also requires an Idempotency-Key on every request.

Project scope stays centralized.

Your project owns the API key, products, Stripe setup, runtime activity, and optional outbound webhooks.

First run checklist

Follow the onboarding order before your first real verification pass.

  1. 1Verify email.
  2. 2Create a project.
  3. 3Create a test API key.
  4. 4Connect Stripe.
  5. 5Configure Stripe webhook.
  6. 6Create a product.
  7. 7Run a test checkout.
  8. 8Verify access.
  9. 9Consume usage for a usage pack.
  10. 10Optionally configure outbound webhooks.
Stripe handoff

Stripe webhook destinations are configured in Stripe. Licenzy stores the Stripe credentials and signing secret, then receives Stripe events directly.

Start in test mode, then go deeper when needed

Quickstart is the shortest path to a working first flow: create a test API key, run checkout with Idempotency-Key, verify access after the Stripe inbound webhook, and use usage/consume only for usage_pack products.

Start freeRead docs