Commerce & Payments · Integration
SoftwareOne
Add SoftwareOne to your product for your customers, and give your AI agents governed access to it.
SoftwareOne's Marketplace Platform is where software and cloud services actually get bought, so its commerce API deals in orders, the agreements they create or amend, the subscriptions inside those agreements, and the catalogue of items available to a given account. An embedded integration places an order, updates the subscriptions on an agreement, reads order and subscription status, and reads catalogue and price detail. Two details govern how you use it. A subscription's state is a consequence of the last completed order that touched it, so your product should read that state rather than infer it from what it asked for. And these writes commit money, so each one is idempotent and recorded against the account that made it, which is what makes a purchase reconcilable afterwards. fastn holds the per-account credentials and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own SoftwareOne account so purchasing happens inside your product rather than a separate portal.
Place an order for a licence or service and follow it to completion, idempotently so a retry cannot buy twice.
Read the subscriptions on an agreement so your product can show current entitlement rather than a purchase history.
Read catalogue and price detail so your product only offers items that account can actually order.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which subscriptions renew next and what each one currently costs.
An agent raises an order for an approved request within scoped permissions, with the write attributed.
An agent explains a subscription's state by reading the order that last changed it.
Example prompt
Which subscriptions on this agreement renew in the next 60 days, and what are we paying for each?
Set up SoftwareOne in 4 steps
- 01Enable the SoftwareOne connector in your fastn dashboard.
- 02Have each customer authorise their own Marketplace account so orders are placed against it.
- 03Map the order, subscription and agreement fields your product uses, then enable the actions you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SoftwareOne integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a SoftwareOne integration without building it. Your customers connect their own SoftwareOne 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 SoftwareOne update is not your on-call problem.
- One integration serves your product and your agents. The same governed SoftwareOne 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
AppDirect
CloudBlue MarketplaceWorks well with
CoupaOften used alongside
Tools the same teams tend to run next to SoftwareOne, across other categories.
NetSuite
Notion
Box
DocusignSoftwareOne integration FAQ
How do I add a SoftwareOne integration to my product?
Enable the SoftwareOne connector in your fastn dashboard, then let each customer authenticate their own SoftwareOne account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SoftwareOne client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SoftwareOne account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SoftwareOne 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 SoftwareOne 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 subscriptions renew next and what each one currently costs.
Who maintains the SoftwareOne integration?
fastn does. When SoftwareOne 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 SoftwareOne 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 SoftwareOne integration?
A common starting point: let each customer connect their own SoftwareOne account so purchasing happens inside your product rather than a separate portal. 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 SoftwareOne integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SoftwareOne does not change your per-connector cost. You can start free with 3 connected accounts.
Add SoftwareOne to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.