Commerce & Payments · Integration
2Checkout
Add 2Checkout to your product for your customers, and give your AI agents governed access to it.
Embed a 2Checkout integration so your customers can work their orders, subscriptions, and refunds inside your product while your agents get governed access to the same payment records. fastn manages per-customer credentials and API maintenance, so accepting a new customer's 2Checkout account is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read orders and transactions into your product, reconciled to their own records.
Read subscription state so your product can gate entitlements on real billing status.
Issue or read refunds from your product without leaving it.
Trigger your product when a payment succeeds, fails, or a subscription lapses.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up a customer's recent transactions before answering a billing question.
An agent issues a refund within governed permissions and logs the reason.
An agent reacts to a failed payment and starts a dunning workflow.
Example prompt
Find orders from this account in the last 60 days with a failed payment and summarise what was attempted.
Set up 2Checkout in 4 steps
- 01Open the 2Checkout connector from your fastn dashboard.
- 02Have each customer authenticate their 2Checkout account.
- 03Map the order, transaction, and subscription 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 2Checkout integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a 2Checkout integration without building it. Your customers connect their own 2Checkout 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 2Checkout update is not your on-call problem.
- One integration serves your product and your agents. The same governed 2Checkout 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
Adyen
Authorize.NetOften used alongside
Tools the same teams tend to run next to 2Checkout, across other categories.
NetSuite
Notion
Box
Docusign2Checkout integration FAQ
How do I add a 2Checkout integration to my product?
Enable the 2Checkout connector in your fastn dashboard, then let each customer authenticate their own 2Checkout account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no 2Checkout client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own 2Checkout account?
Yes. Every connection is scoped to the individual customer, so each authorises their own 2Checkout 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 2Checkout 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 looks up a customer's recent transactions before answering a billing question.
Who maintains the 2Checkout integration?
fastn does. When 2Checkout 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 2Checkout 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 2Checkout integration?
A common starting point: read orders and transactions into your product, reconciled to their own records. 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 2Checkout integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding 2Checkout does not change your per-connector cost. You can start free with 3 connected accounts.
Add 2Checkout to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.