> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/integrations/stripe.md).

# Stripe

Automate license provisioning, renewals, and cancellations in Zentitle2 by syncing them in real time with Stripe payments and webhooks.

<figure><img src="https://2412542193-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1tBhTGn5igyI6ECLHjpC%2Fuploads%2Fz5l23Rd1eGvoxdztXOR3%2Fstripe-integration%20header.png?alt=media&amp;token=7921baac-6bc0-4671-8a4e-4f2e18dc5359" alt=""><figcaption></figcaption></figure>

***

### Benefits of the Stripe Integration in Zentitle 2

1. **Automatic License Provisioning**\
   When a customer completes a payment in Stripe, Zentitle 2 automatically creates the corresponding license or entitlement. This removes the need for manual intervention after each purchase.
2. **Seamless Customer Experience**\
   Payment and license activation are tightly connected, so customers can access what they purchased immediately without waiting for manual setup.
3. **Support for Subscription Lifecycle**
   * **Renewals**: As Stripe processes renewals, Zentitle 2 automatically extends license periods.
   * **Cancellations**: When a subscription is canceled in Stripe, the linked license can be automatically disabled or revoked.
4. **Price-to-Offering Mapping**\
   Each Stripe price maps to a specific Zentitle offering through the price's lookup key. This ensures the correct product entitlements are delivered.
5. **Real-Time Sync via Webhooks**\
   Webhooks from Stripe (e.g., payment success, subscription cancellation) trigger immediate updates in Zentitle 2, keeping licenses fully aligned with billing status.
6. **Multiple Products per Transaction**\
   A single Stripe checkout can cover multiple products or offerings, and the integration handles mapping and provisioning for each.
7. **Developer Flexibility**\
   Zentitle 2 emits its webhook events when licenses or entitlements are created. This allows teams to build custom workflows, such as sending activation codes or automating onboarding steps.
8. **Reduced Manual Overhead & Errors**\
   Because license issuance, extension, and revocation are automated, the risk of human error is reduced, and administrative work is minimized.
9. **Planned Enhancements**\
   Future improvements are expected to simplify setup by simplifying how Zentitle 2 connects with Stripe.

***

### Broader Advantages of Using Zentitle 2

* **Centralized License Management**: One platform to control entitlements and licenses across all products.
* **Flexible Licensing Models**: Supports subscriptions, trials, feature-based licensing, usage-based models, and more.
* **Customer Self-Service**: End-users can activate, manage, or renew their licenses without support involvement.
* **Security and Compliance**: Strong entitlement enforcement with revocation, tracking, and auditing built in.
* **Ecosystem Integration**: Can connect with CRMs, billing tools, and other systems beyond Stripe.
* **Automation**: Event-driven workflows reduce manual tasks and keep licensing in sync with business processes.
* **Improved Customer Retention**: Smooth onboarding, renewals, and license updates deliver a frictionless user experience.

***

→ [Learn more](/zentitle2-docs/ui-administration/integrations/stripe.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nalpeiron.com/zentitle2-docs/integrations/stripe.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.