Commerce & Payments · Integration
Cybersource
Add Cybersource to your product for your customers, and give your AI agents governed access to it.
Embed a Cybersource integration so your customers can take payments and work their own transactions, captures, and refunds through your product, each using their own merchant account. Writes are idempotent, so a retry after a timeout cannot double-charge, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it. fastn handles per-customer credentials and API upkeep, so onboarding another merchant 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 process payments through their own Cybersource merchant account from inside your product.
Read transaction records so payment status appears against the right order or invoice in your app.
Issue a refund or capture an authorisation from your product, with the write idempotent.
Trigger your product when a payment succeeds, fails, or is refunded so fulfilment and accounting steps follow immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up a transaction and its current status before answering a billing question.
An agent issues a refund within governed permissions and approval limits, with the action audited.
An agent reacts to a failed payment and runs the retry or dunning step.
Example prompt
Find declined transactions from yesterday over 200 dollars and show the decline reason for each.
Set up Cybersource in 4 steps
- 01Open the Cybersource connector from your fastn dashboard.
- 02Have each customer authenticate their own Cybersource merchant account.
- 03Map the transaction and refund 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 Cybersource integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cybersource integration without building it. Your customers connect their own Cybersource 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 Cybersource update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cybersource 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
Braintree
Adyen
Authorize.NetOften used alongside
Tools the same teams tend to run next to Cybersource, across other categories.
NetSuite
Notion
Box
DocusignCybersource integration FAQ
How do I add a Cybersource integration to my product?
Enable the Cybersource connector in your fastn dashboard, then let each customer authenticate their own Cybersource account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cybersource client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cybersource account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cybersource 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 Cybersource 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 transaction and its current status before answering a billing question.
Who maintains the Cybersource integration?
fastn does. When Cybersource 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 Cybersource 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 Cybersource integration?
A common starting point: process payments through their own Cybersource merchant account from 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 Cybersource integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cybersource does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cybersource to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.