Commerce & Payments · Integration
Recurly
Add Recurly to your product for your customers, and give your AI agents governed access to it.
Recurly runs recurring billing, so the records are accounts, the subscriptions on them, the plans and add-ons those subscriptions reference, and the invoices, line items and transactions that follow. Two things decide whether an integration behaves. A mid-cycle plan change is two separate decisions, the change itself and how it is prorated, and getting the second one implicitly is how a customer ends up with a credit nobody expected. And dunning is a state, not an event: a subscription with a failed payment is neither cancelled nor healthy, and whether it should still grant access depends on how far through the retry schedule it is. Writes are idempotent so a retry cannot bill twice, and events arrive per site as triggers. fastn holds each site's key per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Recurly site so subscriptions and invoices are read and written from inside your product.
Change a plan mid-cycle and set proration explicitly, because the plan change and the money it moves are two separate choices.
Read dunning state so your product knows whether a failed payment should still grant a user access.
React to a new invoice, a successful payment or a cancellation with an event trigger so entitlement follows immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent explains a customer's next renewal amount from their own subscription and add-ons.
An agent applies an approved credit or plan change idempotently, and the transaction is logged.
An agent lists subscriptions in dunning and how many retries each has left.
Example prompt
Which subscriptions on this site are in dunning, and what will they be charged if the next retry succeeds?
Set up Recurly in 4 steps
- 01Enable the Recurly connector in your fastn dashboard.
- 02Have each customer authorise their own Recurly site so calls run under their key rather than a shared one.
- 03Map the account, subscription, plan and invoice fields your product uses, then enable the triggers you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Recurly integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Recurly integration without building it. Your customers connect their own Recurly 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 Recurly update is not your on-call problem.
- One integration serves your product and your agents. The same governed Recurly 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
Chargebee
Maxio
StripeOften used alongside
Tools the same teams tend to run next to Recurly, across other categories.
NetSuite
Notion
Box
DocusignRecurly integration FAQ
How do I add a Recurly integration to my product?
Enable the Recurly connector in your fastn dashboard, then let each customer authenticate their own Recurly account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Recurly client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Recurly account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Recurly 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 Recurly integration?
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 explains a customer's next renewal amount from their own subscription and add-ons.
Who maintains the Recurly integration?
fastn does. When Recurly 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 Recurly 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 Recurly integration?
A common starting point: let each customer connect their own Recurly site so subscriptions and invoices are read and written from inside your product. 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 Recurly integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Recurly does not change your per-connector cost. You can start free with 3 connected accounts.
Add Recurly to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.