Connect everything your restaurant already runs on
Ten payment gateways. Five delivery marketplaces with two-way order sync. WhatsApp, SMS, email and push. Printers, drawers, kiosks and QR menus. And a documented REST API for whatever is left.
Start Free Trial10
Payment gateways you can switch on per restaurant
5
Delivery marketplaces with two-way order sync
1
Menu that pushes out to every channel you sell on
0%
Marketplace commission on orders from your own channels
Keep the marketplace orders. Own the relationship.
RestioX exists partly to cut what you hand to delivery apps. The fastest way to do that is not to switch them off on a Friday and hope the demand reappears on your own site by Saturday. It is to run every channel through one system, price the difference honestly, and give customers a reason to come direct next time.
So the aggregator connections are deliberate, not a compromise. An Uber Eats order and a QR order from table six arrive in the same list, fire the same kitchen ticket and deduct the same stock. The only thing that differs is the commission line in your channel report — and that is the line that moves once your own ordering channel starts to work.
- Uber Eats, Wolt, Bolt Food, Talabat and Grab orders land in the same order list as your own
- One kitchen queue and one set of tickets, whatever channel the order arrived on
- Your website, QR menus and self-service kiosk take orders with no marketplace commission attached
- Receipts, confirmations and WhatsApp updates carry your name, not the app’s
- Channel reporting shows what each marketplace actually costs you against a direct order
Commission is charged on two of these five lines. The kitchen ticket is identical for all five.
What RestioX connects to today
Grouped by what the connection does for you rather than by who owns the logo. Everything below is in the product now — there are no roadmap entries and no coming-soon badges on this page.
Ten gateways, plus the counter and the cash
Take money the way your country actually takes money. Each gateway is enabled per restaurant with its own keys, runs in sandbox until you are ready to go live, and confirms the payment from a signed webhook rather than trusting the browser that started the checkout.
- ST Stripe Cards, wallets and subscription billing
- PP PayPal PayPal balance and card checkout
- RP Razorpay India — cards, UPI and netbanking
- PK Paystack Africa — cards and bank transfer
- FW Flutterwave Africa — cards and mobile money
- MO Mollie Europe — iDEAL, cards and SEPA
- PA Paddle Merchant-of-record subscription billing
- XE Xendit Southeast Asia — e-wallets and virtual accounts
- PF PayFast South Africa — cards and instant EFT
- TP Tap Gulf region — local cards and wallets
- EP Epay Cards and regional payment methods
- Card terminal In person — chip, swipe and contactless
- Cash and COD Counter cash and cash on delivery
The terminal layer is separate from your online gateway. Chip, swipe and contactless results are recorded against the order like any other payment, and the provider is configured per site — so the processor you use at the counter does not have to be the one you use online.
How payment integration worksFive platforms, one order list
Every platform is its own adapter, with its own credential form, its own status vocabulary and its own webhook signing scheme. None of that reaches your staff. What reaches your staff is an order.
- UE Uber Eats Global marketplace
- WO Wolt Europe and the Nordics
- BF Bolt Food Europe and Africa
- TA Talabat Middle East and North Africa
- GR Grab Southeast Asia
What the connection actually does
- Push your menu out Send categories, items, prices and availability to the platform, so you edit the menu once instead of once per app.
- Pull orders in New orders arrive as ordinary RestioX orders by webhook, or by polling on platforms whose webhooks are unreliable.
- Sync status back Accepted, preparing, ready and out for delivery push back, so the customer’s tracker matches what your kitchen is doing.
- Map items to your menu Match each platform product to the RestioX item behind it, so stock, recipes and reporting stay attached to one product.
- Verify every webhook The HMAC signature on each inbound payload is checked against that platform’s scheme before a single order is created.
- Monitor connection health Failed pushes, expiring tokens and stalled pulls show up as a status per platform, instead of showing up as missing orders.
Tell people what is happening, on the channel they read
Order confirmations, ready-for-collection alerts, reservation reminders, loyalty rewards and staff pings all run through one notification layer. You choose which channels each message goes out on, per restaurant.
- WhatsApp Order updates and customer replies
- SMS Reminders, one-time codes and alerts
- VO Vonage SMS delivery provider credentials
- Transactional email Receipts, confirmations and scheduled reports
- Web push Browser alerts for the back office
- Mobile push Staff app and customer notifications
The metal on your counter
RestioX talks to standard restaurant hardware instead of a proprietary bundle you have to buy from us. If it speaks ESC/POS and it is reachable on your network, it is a printer as far as the software is concerned.
- Receipt printers 80mm thermal, ESC/POS
- Kitchen printers KOT tickets routed per station
- Cash drawers Kick-open on a cash payment
- Customer displays Second screen facing the guest
- Self-service kiosks Order and pay unattended
- QR code menus Table-side ordering, no app to install
Each printer is assigned to what it prints — bar tickets to the bar, hot line tickets to the pass, the bill to the counter. Add a station later and you point it at a printer; you do not re-plan the network.
An API for the integration nobody has built yet
Accounting exports, a loyalty engine you already own, a reservations tool your group standardised on years ago, a second till from another vendor — the things that are specific to you are the things no directory will ever list. So they get an API instead of a promise.
Authentication is token-based, the endpoints are documented, and inbound webhooks are signed and rate limited. If you are scoring RestioX against a procurement checklist, this is the section to forward to whoever maintains your stack.
- Documented REST API covering catalogue, orders, customers and platform settings
- Partner authentication, so delivery partners get their own scoped login
- Multi-POS integration endpoint to register another till against the same data
- Signed inbound webhooks with per-platform verification and rate limiting
# a marketplace pushes an order to your signed endpoint
POST /marketplace/webhook/wolt/{token}
X-Signature: sha256=9f2c1b…
-> signature checked before an order exists
# your own systems read and write over the REST API
GET /api/application-integration/customer/catalog
POST /api/application-integration/multi-pos/register
Authorization: Bearer <token>
# delivery partners authenticate on their own scope
POST /api/application-integration/partner/auth/login
Connecting a platform takes an afternoon, not a project
The flow below is the marketplace one, because it is the fussiest of the lot. A payment gateway or a printer is the same shape with fewer steps.
-
1
Step 1
Pick the platform
Open Integrations, choose the platform, and fill in the connection form its adapter asks for — an API token and a store ID for some, an OAuth handshake for others. Credentials are stored encrypted, per branch.
-
2
Step 2
Test before you trade
Test connection makes a real call and reports what came back. A failure names the reason — wrong token, unknown store ID, region mismatch — rather than going quiet and surfacing at half past seven on a Friday.
-
3
Step 3
Push the menu, then map it
Send your categories and items across, or import what the platform already holds. Then map each platform product to the RestioX item behind it, so stock movements and sales reporting follow the order home.
-
4
Step 4
Point the webhook
Copy the signed endpoint for that platform into their dashboard. Every inbound payload has its signature verified before an order is created, and the endpoint is rate limited so a misbehaving sender cannot flood the till.
-
5
Step 5
Watch it run
Orders land in the same list your waiters already use. Status pushes back as the kitchen works. Connection health flags an expiring token days before it starts dropping orders on a Saturday night.
Three ways operators use this page
The single site adding channels
One café already on two delivery apps, now adding its own site and a QR menu. Same kitchen, same printer, one order screen — plus a weekly report showing what the apps cost against a direct order.
The multi-branch group
Six branches where each site has its own marketplace store IDs, its own printers and sometimes its own gateway. Connections are configured per branch; reporting rolls the whole estate up.
The procurement checklist
An operations lead comparing systems who needs to know, before booking a demo, whether their gateway, their aggregator and their back-office tooling are covered. That answer is on this page; the rest is in the API.
Don’t see the tool you run?
Tell us what it is and what it exposes. The marketplace layer is adapter-based and the REST API is open, so a fair number of gaps close without waiting on our roadmap.
The awkward questions, answered
Because those orders already exist, and switching the apps off on a Monday does not make them reappear on your own site on a Tuesday. The integration is how you stop running them as a separate business: they land in the same order list, print the same tickets, deduct the same stock and show up in the same reports. Your website, QR menus and kiosk — which carry no marketplace commission — are then what you point repeat customers at. Keep the demand, move the relationship.
Six things. It pushes your menu to the platform, pulls new orders in by webhook or polling, syncs the status back as the kitchen works, maps each platform product to the RestioX item behind it, verifies the HMAC signature on every inbound webhook before creating anything, and monitors the connection so an expiring token surfaces as a warning rather than as missing orders.
No. You switch on the ones your bank and your country support. Most restaurants run one; some run a second as a fallback for the night the first one has an incident. Cash and cash on delivery are always available, and in-person card terminals sit alongside whatever you use online.
Yes. In-person terminals run through a provider-agnostic layer covering chip, swipe and contactless, and the result is recorded against the order like any other payment so it reconciles in the same drawer session. Because the provider is configured per site, you are not tied to whichever processor handles your online checkout.
We do not list brands, we list interfaces. RestioX prints to standard thermal receipt and kitchen printers and opens a cash drawer through the printer’s kick port, which is how the large majority of counter hardware behaves. If yours does something unusual, send us the model before you buy six more of them.
Yes. There is a documented REST API with token authentication, a separate partner authentication flow for delivery partners, a multi-POS registration endpoint for putting another till on the same data, and signed inbound webhooks for systems that would rather push than be polled. The developers page is the place to start.
Wire your restaurant together this week
Start free, switch on the gateway your bank supports, connect the marketplaces you already sell on, and print your first ticket the same day. No hardware needed to try it.
Start Free Trial
Post tonight’s special without leaving the back office
Connect the accounts once through OAuth, then write, schedule and measure from the same place you manage the menu — instead of from a phone behind the pass at seven o’clock.