Commerce & Payments · Integration
cXML
Add cXML to your product for your customers, and give your AI agents governed access to it.
Embed a cXML integration so your customers can exchange purchase orders, confirmations, and invoices with their trading partners from inside your product, without you building document handling per partner. Writes are idempotent, so a retry after a timeout does not send the same order twice, and every exchange is logged per tenant so a document can be reconciled against the event that produced it. fastn handles each customer's endpoint credentials and upkeep, so onboarding another trading relationship 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 send purchase orders from your product to their trading partners in cXML rather than by email.
Receive order confirmations and invoices per customer so order state stays current in your product.
Map each customer's own item, unit, and reference fields to the document format as configuration, not code.
Trigger your product when a confirmation or invoice document arrives for an order.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads the documents exchanged for an order before answering a status question.
An agent resends or corrects a document within governed permissions, with the write idempotent and audited.
An agent reacts to an incoming confirmation and runs the next fulfilment step.
Example prompt
List orders sent in the last week with no confirmation document received back yet.
Set up cXML in 4 steps
- 01Open the cXML connector from your fastn dashboard.
- 02Have each customer configure their own endpoint credentials for their trading partners.
- 03Map the document types and fields your product exchanges, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the cXML integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a cXML integration without building it. Your customers point it at their own endpoint and credentials and work their orders, payments and customers through it, 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 cXML update is not your on-call problem.
- One integration serves your product and your agents. The same governed cXML 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
Works well with
Coupa
NetSuiteOften used alongside
Tools the same teams tend to run next to cXML, across other categories.
Notion
Box
Docusign
QuickBookscXML integration FAQ
How do I add a cXML integration to my product?
Enable the cXML connector in your fastn dashboard, then let each customer authenticate their own cXML account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no cXML client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
How is a cXML connection configured per customer?
cXML is a specification rather than a service you sign up for, so there is no cXML account. Each customer supplies their own endpoint and credentials, and that connection is scoped to them, so they only ever reach their own orders, payments and customers. The per-tenant isolation works the same way it does for a vendor product.
Can AI agents use this cXML 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 reads the documents exchanged for an order before answering a status question.
Who maintains the cXML integration?
fastn does. When cXML 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 cXML 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 cXML integration?
A common starting point: send purchase orders from your product to their trading partners in cXML rather than by email. 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 cXML integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding cXML does not change your per-connector cost. You can start free with 3 connected accounts.
Add cXML to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.