> 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

<figure><img src="/files/kZJCBX3aKhff7LQGy4C9" 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. **Metadata Mapping**\
   Stripe “price” objects can be tagged with metadata that maps them directly to specific Zentitle offerings. 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, including subscription identifiers, 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
