Help with Devolens/Cryptolens payment automation for Stripe, n8n, Zapier, webhooks, external payment providers, license delivery, renewal, cancellation, CRM sync, expiry reminders, CreateKey, ExtendLicense, BlockKey, AddFeature, and MachineLockLimit workflows.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "license-payment-automation" with this command: npx skills add Cryptolens/skillsmp-cryptolens-cryptolens-license-payment-automation
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Help with Devolens/Cryptolens feature-gated licensing, feature flags, product editions, feature templates, HasFeature checks, data-object-backed feature hierarchies, AddFeature upgrades, and entitlement review across .NET, Python, Java, Node.js, direct Web API integrations, and related stacks.
Help with Devolens/Cryptolens backend license key creation, CreateKey API usage, license templates, server-side access-token scope, payment-success license delivery, customer-linked licenses, product IDs, periods, features, maximum machines, and license provisioning workflows.
Help with Devolens/Cryptolens subscription licensing, expiry checks, renewal logic, grace periods, ExtendLicense renewals, BlockKey cancellation handling, Stripe webhook flows, and subscription access review across .NET, Python, Java, Node.js, direct Web API integrations, and related stacks.
Shared cross-language guidance for Cryptolens software licensing SDKs, direct Web API 3 HTTP integrations, and unsupported-language fallbacks. Use when Codex works on any Cryptolens SDK or app integration and needs language-agnostic licensing rules, especially license key verification best practices, offline license verification with cached signed license files or strings, floating licenses, trial licenses, activation semantics, node-locking, machine-binding assumptions, or behavior that should stay consistent across Python, .NET, Java, Node.js, direct HTTP clients, and future SDKs.