Commerce & Payments · Integration
Metro
Add Metro to your product for your customers, and give your AI agents governed access to it.
Embed a Metro integration so sellers can list their catalogue and work their marketplace orders from inside your product, with each seller connecting their own account rather than routing through a shared key. Product data and offers can be uploaded in bulk, orders can be read and searched in batches, line items marked as shipped and invoices uploaded, and a new or updated order can trigger your product as it lands. Writes are idempotent, so a retry after a timeout cannot duplicate a shipment or an invoice, and every call is logged per tenant so a document can be reconciled against the order behind it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each seller connect their own Metro account so your product can list their catalogue and work their marketplace orders.
Upload product data and create offers in bulk so a seller's catalogue reaches the marketplace without manual entry.
React to a new or updated order with an event trigger, then ship line items and upload the invoice from your product.
Keep every seller's catalogue, orders and documents scoped to the account that authorised them.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers where a marketplace order stands by reading the seller's own order and shipment data.
An agent marks line items as shipped within scoped permissions, with the write idempotent and audited.
An agent flags offers that are missing data or out of stock and explains what to fix.
Example prompt
Which Metro orders for this seller are still unshipped, and are any invoices missing?
Set up Metro in 4 steps
- 01Enable the Metro connector in your fastn dashboard.
- 02Have each seller authorise their own account so calls run under their credentials.
- 03Map the product, offer, order and invoice fields your product uses, then enable order triggers.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Metro integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Metro integration without building it. Your customers connect their own Metro 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 Metro update is not your on-call problem.
- One integration serves your product and your agents. The same governed Metro 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
Amazon Seller Central
Walmart Seller
ChannelEngineOften used alongside
Tools the same teams tend to run next to Metro, across other categories.
NetSuite
Notion
Box
DocusignMetro integration FAQ
How do I add a Metro integration to my product?
Enable the Metro connector in your fastn dashboard, then let each customer authenticate their own Metro account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Metro client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Metro account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Metro 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 Metro 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 answers where a marketplace order stands by reading the seller's own order and shipment data.
Who maintains the Metro integration?
fastn does. When Metro 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 Metro 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 Metro integration?
A common starting point: let each seller connect their own Metro account so your product can list their catalogue and work their marketplace orders. 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 Metro integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Metro does not change your per-connector cost. You can start free with 3 connected accounts.
Add Metro to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.