Commerce & Payments · Integration
Revel Systems
Add Revel Systems to your product for your customers, and give your AI agents governed access to it.
Revel is an iPad point of sale for restaurants and retail, so the records are orders and their line items, the menu and product structure behind them, the establishments where they were rung up, the employees who rang them and the payments taken against a check. Two facts shape any integration. A line item is rarely a bare product id, because a restaurant order is a product plus modifiers, and dropping the modifiers loses both the price and what the kitchen is meant to make. And a multi-site operator runs each establishment separately, so a query without an establishment answers for the wrong restaurant. Writes are idempotent because a duplicated check is duplicated food and duplicated money. fastn holds each operator's credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each operator connect their own Revel account so orders and payments are read and written per establishment.
Read the menu structure with its modifiers, so a line item your product creates matches something the kitchen can actually make.
Write an order idempotently, because a retry that duplicates a check duplicates both food and money.
Scope every read to an establishment, since a multi-site operator's numbers mean nothing without it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports what a site sold during a shift and which items drove it.
An agent looks up an order and its payment records to settle a dispute.
An agent updates a product or a price within scoped permissions, with the establishment logged.
Example prompt
What did this establishment sell during last night's dinner shift, and which modifiers came up most often?
Set up Revel Systems in 4 steps
- 01Enable the Revel Systems connector in your fastn dashboard.
- 02Have each operator authorise their own Revel account so calls run under their credentials.
- 03Map the establishments, menu and modifier structure, order fields and payment records your product uses.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Revel Systems integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Revel Systems integration without building it. Your customers connect their own Revel Systems 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 Revel Systems update is not your on-call problem.
- One integration serves your product and your agents. The same governed Revel Systems 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
Clover
Shopify
StripeOften used alongside
Tools the same teams tend to run next to Revel Systems, across other categories.
NetSuite
Notion
Box
DocusignRevel Systems integration FAQ
How do I add a Revel Systems integration to my product?
Enable the Revel Systems connector in your fastn dashboard, then let each customer authenticate their own Revel Systems account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Revel Systems client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Revel Systems account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Revel Systems 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 Revel Systems 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 what a site sold during a shift and which items drove it.
Who maintains the Revel Systems integration?
fastn does. When Revel Systems 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 Revel Systems 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 Revel Systems integration?
A common starting point: let each operator connect their own Revel account so orders and payments are read and written per establishment. 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 Revel Systems integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Revel Systems does not change your per-connector cost. You can start free with 3 connected accounts.
Add Revel Systems to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.