Payments & gateways
Accept cards and digital wallets through payment partners that fit your market. Quarey routes payment flows through PCI-aware processors so card data stays with certified gateways — Quarey is not designed to store raw card numbers in the restaurant POS.
Stripe
Cards & online payments
PayPal
Checkout & wallets
Regional gateways
Market-specific processors
Delivery aggregators
Keep third-party marketplace orders flowing into the same kitchen display and POS workflows — while growing direct orders on Quarey’s branded delivery channel and rider dispatch.
Uber Eats
Marketplace orders
DoorDash
US delivery volume
Grubhub
US aggregator channel
Regional apps
Deliveroo, Careem, Talabat, local fleets
Accounting & back office
Export sales and settlement data into the books your finance team already uses — reducing double entry between POS and accounting at month-end.
QuickBooks
Sales & expense sync
Xero
Cloud accounting export
API & custom integrations
Connect Quarey’s cloud-based POS and hybrid POS stack to loyalty, CRM, or internal tools via API integrations. Built for multi-outlet and franchise groups that need a programmable restaurant OS.
REST APIs
Orders, menus, branches
Webhooks
Event-driven workflows
Custom domains
Branded ordering URLs
How payment gateway workflows work
When a guest pays at the counter or closes a dining check, Quarey initiates the charge through the configured gateway (for example Stripe or PayPal) rather than storing PAN data in the POS database. Settlements and failure states stay visible to managers so a declined card does not silently leave a table open. Online and branded-delivery payments follow the same principle: the gateway remains the system of record for cardholder data, while Quarey records the order, tip, and settlement status for restaurant reporting. Regional gateways can be selected during onboarding when your market requires a local processor — confirm which connectors are live in your country before promising a specific wallet to guests.
How aggregator orders reach the kitchen
Marketplace tablets create chaos when each channel has its own screen. Quarey’s integration approach is to land Uber Eats, DoorDash, Grubhub, and regional apps such as Deliveroo, Careem, or Talabat into the same POS and KDS ticket stream your dine-in orders already use. The kitchen sees one queue with clear channel labels; riders or collection windows get the right bag without a second set of SOPs. Quarey does not replace the aggregator — it reduces tablet sprawl while you grow direct orders on the branded delivery app and in-house rider dispatch. Availability of each marketplace connector varies by country; onboarding confirms what is enabled for your locations.
How sales reach QuickBooks and Xero
Finance teams should not re-key every shift. Quarey exports sales and settlement summaries into accounting tools such as QuickBooks and Xero so daily takings, tax lines, and payout batches can reconcile against gateway deposits. Multi-branch groups can separate location-level sales while rolling up to a parent entity. Exact field mappings and export cadence are configured with your bookkeeper during go-live — treat the integration as a bookkeeping aid, not a substitute for your accountant’s chart of accounts design.
API, webhooks, and custom domains
Franchise and enterprise teams often already run loyalty, CRM, or data warehouses. Quarey’s REST APIs expose orders, menus, and branch data so those systems can subscribe without scraping screens. Webhooks notify your stack when tickets fire, payments settle, or menus change. Custom domains keep branded ordering URLs on your restaurant’s hostname while Quarey handles the storefront. Hybrid POS offline sync continues at the terminal while cloud APIs serve HQ — the floor keeps selling if the WAN blinks. Developer access and scopes are provisioned during enterprise onboarding; ask for the current API surface if you are planning a custom build.
What to confirm before you switch
Integrations are only useful when they match how you actually serve guests. Before cutover, list your live payment methods, aggregator channels, accounting package, printer/network layout, and any loyalty system that must stay. Quarey’s onboarding team maps those to available connectors and documents gaps instead of implying every logo is live everywhere. See Security for PCI-aligned payment handling, Onboarding for rollout steps, and Watch demo for a short product walkthrough.
Integrations FAQ
Ready to run your restaurant smarter?
Join restaurants worldwide running smarter with Quarey.
Start your 7-day free trial