Finance & ERP · Integration
Ramp
Add Ramp to your product for your customers, and give your AI agents governed access to it.
Ramp is corporate cards and spend management, and what makes it useful downstream is that a transaction does not arrive bare: it carries the accounting detail a controller needs, a general ledger account, a department, a location and whatever custom accounting dimensions that company synced across from its ERP. Those valid codes come from the customer's own chart of accounts, so they are per-tenant configuration and never a list you can ship. Reimbursements, bills and vendors follow the same shape. Writes are idempotent because a duplicated coding entry or a duplicated bill is a number somebody has to explain at close, and events arrive as triggers so your product reacts to an approved expense rather than polling for it. fastn owns the credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Ramp account so card transactions arrive in your product already coded to their general ledger accounts.
Read reimbursements, bills and vendors with their accounting dimensions attached, so a payable never has to be re-keyed.
Write the codes your product owns back onto a transaction, drawing on values that exist in that customer's chart of accounts rather than defaults.
React to a new transaction or an approved reimbursement with an event trigger instead of a nightly pull.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent explains how a transaction was coded and which policy approved it.
An agent flags transactions still missing a receipt or a general ledger code before a close.
An agent codes a transaction within governed permissions, idempotently, with the write logged.
Example prompt
Which transactions this month are still missing a general ledger code or a receipt, and whose cards are they on?
Set up Ramp in 4 steps
- 01Enable the Ramp connector in your fastn dashboard.
- 02Have each customer authorise their own Ramp account with scopes limited to the spend data your product needs.
- 03Map their general ledger accounts, departments, locations and custom accounting dimensions, then enable triggers.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Ramp integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Ramp integration without building it. Your customers connect their own Ramp account inside your product and work their invoices, payments and vendors there, with no per-customer code on your side.
- Handle the part that actually costs time: financial writes must be idempotent and reconcilable, because a duplicate is an accounting problem rather than a bug. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Ramp update is not your on-call problem.
- One integration serves your product and your agents. The same governed Ramp connection powers in-product features and gives AI agents scoped, audited access, so you move financial records without hand-keying them between systems without wiring it twice.
Used by these teams
Compare with
Brex
Expensify
NavanOften used alongside
Tools the same teams tend to run next to Ramp, across other categories.
Shopify
Stripe
BigCommerce
AfterShipRamp integration FAQ
How do I add a Ramp integration to my product?
Enable the Ramp connector in your fastn dashboard, then let each customer authenticate their own Ramp account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Ramp client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Ramp account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Ramp account and only ever sees their own invoices, payments and vendors. 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 Ramp 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 explains how a transaction was coded and which policy approved it.
Who maintains the Ramp integration?
fastn does. When Ramp 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 Ramp integration safe for financial writes?
Writes are idempotent, so a retry after a timeout does not post a document twice, and every call is logged per tenant so an entry can be traced back to the event that created it. That matters more in finance than anywhere else, because a duplicate is a number somebody has to explain.
Can it handle each customer's own chart of accounts?
Yes. ERP deployments are configured to the business, so account structures, required fields and fiscal calendars differ per customer. Those are mapped per tenant as configuration, not hard-coded.
What about Ramp rate limits during a first import?
Backfills are throttled deliberately. ERP limits are often account-wide rather than per-integration, so an unthrottled import can exhaust a customer's allowance and disrupt their other integrations.
What can I build with the Ramp integration?
A common starting point: let each customer connect their own Ramp account so card transactions arrive in your product already coded to their general ledger accounts. 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 Ramp integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Ramp does not change your per-connector cost. You can start free with 3 connected accounts.
Add Ramp to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.