Integration And Automation
Use this section to connect LicenseKit to the systems around the product: Stripe, CRMs, custom commerce workflows, webhooks, events, custom fields, and reliability patterns.
Who This Is For
- teams issuing licenses from payments, invoices, subscriptions, or closed-won deals
- operators who need customer and order context attached to licenses
- developers building custom automation around LicenseKit events and APIs
- support, success, finance, and compliance teams that need trustworthy license evidence
When To Use This
Read this section when license issuance starts outside LicenseKit.
Stripe, HubSpot, Pipedrive, Zoho CRM, or your own system should remain the commercial source of truth. LicenseKit should receive the commercial context, create or update access records, enforce access at runtime, and expose reporting evidence.
What Is In This Section
- CRM And Commerce Integrations
- Stripe
- HubSpot
- Pipedrive
- Zoho CRM
- Orders And Subscriptions
- Error Handling
- Idempotency
- Webhooks
- Events
- Custom Fields
Integration Model
Use this mental model:
- A commercial event happens: payment succeeds, subscription renews, deal closes, or an internal order is approved.
- The integration resolves a LicenseKit product and policy mapping.
- LicenseKit creates or updates the customer, order, subscription, license, seats, feature entitlements, and relevant custom fields.
- The protected product uses the runtime API to validate access.
- Operators use reports, exports, events, and webhooks to understand what happened.
Common Mistakes
- making LicenseKit the billing source of truth instead of linking back to the billing or CRM source
- issuing duplicate licenses when the external system retries webhooks or workflow actions
- losing customer/order context by only storing a license key
- relying on a dashboard screenshot when a frozen JSON, CSV, or PDF export is required
- skipping runtime signature verification because the license was issued from a trusted CRM