CRM And Commerce Integrations
Use this page to choose how LicenseKit should connect to the system where a sale, order, subscription, or deal already exists.
Who This Is For
- teams selling through Stripe, HubSpot, Pipedrive, Zoho CRM, or a custom order system
- developers wiring license fulfillment after a payment or closed-won deal
- operators who need license state visible next to customer and commercial records
When To Use This
Use a CRM or commerce integration when the customer relationship or payment already lives outside LicenseKit.
LicenseKit should not replace that system. It should attach enforceable access state to the commercial event and make the resulting license activity observable.
How It Works
The integration flow is consistent across platforms:
- receive a trusted event or workflow call from the external system
- resolve a mapping from external product, price, deal, SKU, or line item to a LicenseKit product and policy
- create or reuse the LicenseKit customer
- create or reuse the LicenseKit order or subscription record with
external_systemandexternal_id - issue, renew, suspend, reinstate, or sync the linked license
- show status back in the source system where the sales or support team works
Integration Matrix
| Source system | Best trigger | LicenseKit records | Visibility back to source |
|---|---|---|---|
| Stripe | paid checkout, invoice, subscription, or payment event | customer, order, subscription context, license, mapping, fulfillment attempt | Stripe app views for customer, product, subscription, invoice, and payment context |
| HubSpot | closed-won deal, mapped line item, or workflow action | customer, order, one license per mapped line item, lifecycle sync | CRM cards on deal, company, and contact records plus workflow outputs |
| Pipedrive | won deal event | customer, order, license, deal-to-license link | JSON panel on the deal detail view |
| Zoho CRM | Closed Won deal update notification | customer, order, license, deal-to-license link, event dedupe | Zoho deal related details panel and status route |
| Custom API | internal order approval, provisioning job, or partner workflow | any supported management record | your own portal, CRM, warehouse, or support tool |
What LicenseKit Adds
The source system tells LicenseKit what was sold or approved.
LicenseKit adds:
- runtime activation and validation
- signed runtime responses
- seats, device limits, features, versions, metering, offline issuance, and floating leases
- customer/order-linked license state
- event history and webhook delivery
- customer summaries, license audits, usage ledgers, settlement-oriented reports, and exports
Common Mistakes
- sending a static license key from a payment event without preserving the customer, order, and source IDs
- assuming CRM status is enough to protect the software at runtime
- letting each external retry create a new license instead of using idempotent source IDs
- syncing metered usage back into billing before deciding which system owns pricing and invoicing