Commerce & Payments · Integration
Lemon Squeezy
Add Lemon Squeezy to your product for your customers, and give your AI agents governed access to it.
Lemon Squeezy's API at api.lemonsqueezy.com/v1 is a JSON:API implementation, so requests need both Accept and Content-Type set to application/vnd.api+json and responses arrive as data, attributes and relationships rather than flat objects. Filtering uses the filter[store_id] style and related records are pulled with include, which matters because an order does not carry its subscription inline. Lemon Squeezy acts as merchant of record, so tax handling and the customer's country sit on the order rather than in your own billing logic, and refunds are recorded as order refunds rather than negative orders. Licence keys are a first-class resource with activation limits and instances, and are the usual reason software vendors integrate at all. Webhook payloads are signed with an HMAC SHA-256 hex digest in the X-Signature header computed over the raw body, so parsing before verifying breaks the check. fastn stores each customer's API key and store scope separately and keeps the webhook and token upkeep off your roadmap.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Lemon Squeezy store so their orders and subscriptions show up in your dashboard
Sync subscription status changes so entitlements in your product follow the customer's plan
Issue, activate and deactivate licence keys from your own admin screens
Reconcile payouts and refunds against your internal revenue records
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent look up a customer's current subscription and licence activations before answering a support question
Have an agent draft a refund request for human approval rather than issuing it directly
Give an agent read access to order history with every query audited per tenant
Example prompt
How many active subscriptions does my Lemon Squeezy store have on the annual plan?
Set up Lemon Squeezy in 4 steps
- 01Enable the Lemon Squeezy connector from your fastn dashboard.
- 02Have each customer authorise their own Lemon Squeezy account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Lemon Squeezy integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lemon Squeezy integration without building it. Your customers connect their own Lemon Squeezy account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Lemon Squeezy update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lemon Squeezy connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to Lemon Squeezy, across other categories.
NetSuite
Notion
Box
DocusignLemon Squeezy integration FAQ
How do I add a Lemon Squeezy integration to my product?
Enable the Lemon Squeezy connector in your fastn dashboard, then let each customer authenticate their own Lemon Squeezy account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lemon Squeezy client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lemon Squeezy account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lemon Squeezy account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Lemon Squeezy integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent look up a customer's current subscription and licence activations before answering a support question
Who maintains the Lemon Squeezy integration?
fastn does. When Lemon Squeezy changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Lemon Squeezy integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Lemon Squeezy integration?
A common starting point: let a customer connect their own Lemon Squeezy store so their orders and subscriptions show up in your dashboard. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Lemon Squeezy integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lemon Squeezy does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lemon Squeezy to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.