Commerce & Payments · Integration
Checkout.com
Add Checkout.com to your product for your customers, and give your AI agents governed access to it.
Checkout.com models a payment as a sequence rather than a single act. A payment is authorised first and captured afterwards, in full or in part, and it can be voided before capture or refunded after it, so your product has to know which stage a payment sits at before it offers anybody an action. Hosted payment sessions cover the collection side, and disputes turn up later with evidence deadlines attached. Two operational details matter: an idempotency key on every write, because an authorisation submitted twice is a real problem, and webhooks, which have to be verified and are the only dependable way to learn that state moved. fastn stores each account's credentials per tenant and tracks Checkout.com's API changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a merchant connect their own account so authorisation, capture and refund all run under their credentials.
Capture part of an authorised payment when only part of an order ships, and void what is left.
Create a hosted payment session so sensitive card entry never reaches your product's own forms.
Act on verified webhooks for captures, refunds and disputes, since a state change surfaces nowhere else in time.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which payments are authorised but not yet captured, and how long each has waited.
An agent refunds a captured payment within permission, with the capture it reversed recorded.
An agent lists open disputes and the evidence deadline attached to each.
Example prompt
Which payments are still authorised but uncaptured, and are any of them close to expiring?
Set up Checkout.com in 4 steps
- 01Enable the Checkout.com connector from your fastn dashboard.
- 02Have each customer authorise their own Checkout.com account, so calls run under their credentials rather than a shared key.
- 03Decide which payments, captures, refunds and payment sessions your product needs, and map the authorisation lifecycle, since which stage a payment is at gates every action.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Checkout.com integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Checkout.com integration without building it. Your customers connect their own Checkout.com 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 Checkout.com update is not your on-call problem.
- One integration serves your product and your agents. The same governed Checkout.com 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
BraintreeOften used alongside
Tools the same teams tend to run next to Checkout.com, across other categories.
NetSuite
Notion
Box
DocusignCheckout.com integration FAQ
How do I add a Checkout.com integration to my product?
Enable the Checkout.com connector in your fastn dashboard, then let each customer authenticate their own Checkout.com account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Checkout.com client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Checkout.com account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Checkout.com 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 Checkout.com 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 payments are authorised but not yet captured, and how long each has waited.
Who maintains the Checkout.com integration?
fastn does. When Checkout.com 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 Checkout.com 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 Checkout.com integration?
A common starting point: let a merchant connect their own account so authorisation, capture and refund all run under their credentials. 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 Checkout.com integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Checkout.com does not change your per-connector cost. You can start free with 3 connected accounts.
Add Checkout.com to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.