Commerce & Payments · Integration
Paddle
Add Paddle to your product for your customers, and give your AI agents governed access to it.
Paddle is a merchant of record rather than a payment gateway, and that distinction drives everything about integrating it. Paddle is the seller, so it handles sales tax and VAT registration across jurisdictions and the money arrives as a payout rather than per transaction. A product reading Paddle should not expect gateway-shaped data: what you get is a transaction with tax already resolved, which is more useful and differently shaped. Subscriptions carry the lifecycle worth reacting to, and those events are the integration most products actually need. fastn scopes each customer's key per tenant and handles the event delivery.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Paddle account so billing state appears inside your product.
Read transactions with tax already resolved rather than recomputing it per jurisdiction.
Track subscription lifecycle, which is where churn and upgrade signals live.
React to a payment failure or cancellation the moment it happens.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which subscriptions failed payment and how much is at risk.
An agent cancels or pauses a subscription within governed permissions, with the action audited.
An agent explains why a customer's charge differed from list price.
Example prompt
Which subscriptions failed payment this week, and what is the total at risk?
Set up Paddle in 4 steps
- 01Enable the Paddle connector from your fastn dashboard.
- 02Have each customer authorise their own Paddle 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 Paddle integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Paddle integration without building it. Your customers connect their own Paddle 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 Paddle update is not your on-call problem.
- One integration serves your product and your agents. The same governed Paddle 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
Stripe
PayPal
RazorpayOften used alongside
Tools the same teams tend to run next to Paddle, across other categories.
NetSuite
Notion
Box
DocusignPaddle integration FAQ
How do I add a Paddle integration to my product?
Enable the Paddle connector in your fastn dashboard, then let each customer authenticate their own Paddle account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Paddle client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Paddle account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Paddle 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 Paddle 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 reports which subscriptions failed payment and how much is at risk.
Who maintains the Paddle integration?
fastn does. When Paddle 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 Paddle 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 Paddle integration?
A common starting point: let a customer connect their own Paddle account so billing state appears 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 Paddle integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Paddle does not change your per-connector cost. You can start free with 3 connected accounts.
Add Paddle to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.