Commerce & Payments · Integration
linked2pay
Add linked2pay to your product for your customers, and give your AI agents governed access to it.
Embed a linked2pay integration so your customers can take and track payments from their own account rather than through one you operate. Writes are idempotent, so a retry after a timeout cannot double-apply a payment, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it. fastn handles per-customer credentials, retries and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own linked2pay account so payments are initiated on their account, not yours.
Read transaction status so your product knows when a payment settled, failed or was returned.
Create or update payer records so a payment is raised against the right account.
React to a payment status change so accounting or entitlement steps run when it lands.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks a payment's status before answering a billing question.
An agent raises a payment within governed permissions, with idempotent writes and an audit trail.
Every call is logged per tenant, so a transaction can be traced to the request behind it.
Example prompt
List payments still pending after three business days and tell me which payer each one belongs to.
Set up linked2pay in 4 steps
- 01Open the linked2pay connector from your fastn dashboard.
- 02Have each customer authenticate their own linked2pay account.
- 03Map the payer and transaction fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the linked2pay integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a linked2pay integration without building it. Your customers connect their own linked2pay 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 linked2pay update is not your on-call problem.
- One integration serves your product and your agents. The same governed linked2pay 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
AdyenWorks well with
QuickBooksOften used alongside
Tools the same teams tend to run next to linked2pay, across other categories.
NetSuite
Notion
Box
Docusignlinked2pay integration FAQ
How do I add a linked2pay integration to my product?
Enable the linked2pay connector in your fastn dashboard, then let each customer authenticate their own linked2pay account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no linked2pay client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own linked2pay account?
Yes. Every connection is scoped to the individual customer, so each authorises their own linked2pay 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 linked2pay 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 checks a payment's status before answering a billing question.
Who maintains the linked2pay integration?
fastn does. When linked2pay 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 linked2pay 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 linked2pay integration?
A common starting point: connect their own linked2pay account so payments are initiated on their account, not yours. 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 linked2pay integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding linked2pay does not change your per-connector cost. You can start free with 3 connected accounts.
Add linked2pay to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.