Commerce & Payments · Integration
MoonClerk
Add MoonClerk to your product for your customers, and give your AI agents governed access to it.
MoonClerk builds recurring payment forms on top of Stripe, so the merchant's funds and card data live in their Stripe account and MoonClerk holds the form, plan and schedule layer. Its API at api.moonclerk.com is read-oriented and authenticates with an Authorization header using the Token token= format, along with an Accept header naming the API version. The main resources are payments, customers, checkouts, forms and plans, where a checkout is the record linking a customer to a form and its recurring schedule, and a payment belongs to a checkout rather than directly to a customer. Because the actual charges are Stripe charges, reconciling MoonClerk payments against Stripe means matching on the Stripe identifiers carried on the payment record. There is no API for creating a subscription, so sign-ups still go through the hosted or embedded form, which surprises teams expecting a full write API. fastn keeps each customer's MoonClerk token separate and handles the per-tenant auth and upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own MoonClerk account so their recurring plans and payments appear in your product
Sync payment and checkout records into your own reporting so recurring revenue is visible alongside other sources
Alert a customer when a recurring payment fails and the schedule stalls
Match MoonClerk payments to the corresponding Stripe charges for reconciliation
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent look up a payer's checkout, plan and payment history when handling a billing question
Have an agent flag failed or overdue recurring payments for review, audited per tenant
Give an agent read-only access, since subscriptions cannot be created through the API anyway
Example prompt
Which MoonClerk recurring payments failed in the last week?
Set up MoonClerk in 4 steps
- 01Enable the MoonClerk connector from your fastn dashboard.
- 02Have each customer authorise their own MoonClerk 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 MoonClerk integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a MoonClerk integration without building it. Your customers connect their own MoonClerk 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 MoonClerk update is not your on-call problem.
- One integration serves your product and your agents. The same governed MoonClerk 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 MoonClerk, across other categories.
NetSuite
Notion
Box
DocusignMoonClerk integration FAQ
How do I add a MoonClerk integration to my product?
Enable the MoonClerk connector in your fastn dashboard, then let each customer authenticate their own MoonClerk account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no MoonClerk client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own MoonClerk account?
Yes. Every connection is scoped to the individual customer, so each authorises their own MoonClerk 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 MoonClerk 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 payer's checkout, plan and payment history when handling a billing question
Who maintains the MoonClerk integration?
fastn does. When MoonClerk 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 MoonClerk 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 MoonClerk integration?
A common starting point: let a customer connect their own MoonClerk account so their recurring plans and payments appear in 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 MoonClerk integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding MoonClerk does not change your per-connector cost. You can start free with 3 connected accounts.
Add MoonClerk to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.