Lightspeed Commerce

Enable the Lightspeed Commerce connector in your fastn dashboard, then let each customer authenticate their own Lightspeed Commerce account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lightspeed Commerce client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Lightspeed Commerce 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.

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent looks up an order and its status before replying to a shopper query.

fastn does. When Lightspeed Commerce 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.

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.

Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.

A common starting point: let merchants connect their own Lightspeed account so your product reads their products, orders and customers. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lightspeed Commerce does not change your per-connector cost. You can start free with 3 connected accounts.