Turn Lemon Squeezy billing events into controlled revenue action

Lemon Squeezy documents that customers should retain access through trial, active, paused, past-due, unpaid, and cancelled subscription states, and lose it only when the subscription is expired. For subscription products with license keys, the related key stays active until the subscription expires. MetaCTO turns that lifecycle into an explicit entitlement policy, retrieves current subscription and license state before acting, and compares it with the access actually provisioned. AI can explain drift or prepare a case, but it does not reinterpret a payment warning as permission to revoke access.

The subscription API can change a variant, pause payment collection, move a billing date, and cancel or resume a subscription; plan changes use proration by default unless the request changes that behavior. Those are consequential commercial operations, not ordinary agent tools. MetaCTO has AI assemble the evidence and proposed before-and-after values, then requires policy validation and an authorized reviewer for customer-impacting changes. A separate executor re-reads the subscription, uses a narrowly held server-side credential, performs the approved request once, and reconciles the resulting state and webhook.

Lemon Squeezy signs each request in the `X-Signature` header and expects an HTTP 200 response; a non-200 response is retried up to three more times with exponential backoff, and recent events can also be resent manually. Its developer guide recommends storing events locally so the receiver can acknowledge quickly and process outside the request. MetaCTO verifies the signature against the raw body, persists the original event, deduplicates delivery, and fetches current API state before deciding. Failed downstream work stays in a reconciliation queue instead of relying on another webhook or repeating a financial side effect.

The separate License API can activate, validate, and deactivate license instances, is limited to 60 requests per minute, and returns an instance ID that should be retained for later validation or deactivation. Lemon Squeezy also recommends checking the returned store, product, or variant identifiers so a key for another product cannot grant access; fully disabling a key is currently a dashboard action rather than a License API operation. MetaCTO keeps full keys out of prompts and broad logs, queues validation traffic, verifies product identity and activation limits deterministically, and sends disablement or exceptional-access decisions to an accountable operator.

Lemon Squeezy is a strong candidate when supported digital goods, software, or SaaS fit its merchant-of-record model and its orders, subscriptions, customer portal, webhooks, and optional licensing can remain the commerce authority. Its documentation says physical goods and services are prohibited, so it should not be forced into those operating models. The general API also documents a 300-request-per-minute limit, separate from the License API limit, which means bursty reconciliation needs queues and backoff. MetaCTO compares seller responsibility, catalog and entitlement complexity, expected event volume, approval needs, and finance reconciliation before choosing it over a broader billing or ERP platform.