Skip to content

Payments overview

Payments run through your own gateway account, so money settles to you directly. You choose which methods appear at checkout, in what order, and under what conditions.

Online — charged at checkout, before the order reaches your kitchen:

Method Notes
Card Through your connected gateway. Bank verification (3-D Secure) is handled in the checkout flow where the region requires it
Apple Pay / Google Pay Ride on the same gateway; device-wallet registration is part of app setup
Wallet The customer’s stored balance with you — see Wallet

Physical — collected at handover, and recorded rather than processed:

Method Collected by
Cash Staff or the driver
Card on delivery The driver, on a machine they carry
Card terminal Staff, at the counter — see Card terminals
Bank transfer Arranged outside the platform and recorded against the order

Gateways available today: Stripe, Finix, Paytrail, InterGateway and Banca Transilvania, alongside cash and card on delivery. Which suits you depends on your market; your account team sets up anything beyond Stripe.

This table is the one worth remembering, because it decides your refund policy:

Method Charged when Refundable through the platform
Card / Apple Pay / Google Pay At checkout Yes
Wallet At checkout Yes, instantly
Cash At handover Recorded only
Bank transfer Outside the platform Recorded only
Card on delivery At handover No
Card terminal At handover No — reverse it at the terminal or in the gateway dashboard

Each entry under Payment Config is one thing a customer can choose, and carries:

  • An internal name, and the underlying method it maps to
  • A customer-facing name and description — what they actually read
  • A priority, which is its position in the checkout list
  • Visibility — public, private, or informational
  • Feature flags — whether it may fund a wallet top-up, an auto top-up, or a membership payment, and whether it is excluded from ordinary orders
  • Conditions — restrict it by business type, zone, outlet or order type
  • Optional fee, cashback and reward points — see Taxes & charges
  • Special rules — minimum and maximum amounts, a date range, operating hours

There is no separate per-outlet payment screen. Scoping is done from the method’s own Conditions.

An order shows pending, paid, failed or refunded. Prepaid orders arrive paid; pay-on-arrival orders show the amount still due until staff record it, which is what stops food leaving without money.

A failed payment means the order never reached you — nothing was charged and nothing needs doing.

Where you offer tipping, the customer chooses at checkout from presets you set, or types an amount. At a card terminal the reader itself can ask, and a tip taken that way is confirmed by the gateway and rides alongside the order total rather than inside it — so your order figures stay clean.

You can require prepayment until a customer has completed a set number of orders, disabling cash and card on delivery for them. It is the cleanest defence against repeat no-shows on delivery, and it turns itself off once the customer has a history.

  1. Connect a gateway — Gateway setup.
  2. Build the checkout method list, with priorities and conditions.
  3. Set Taxes & charges, so totals are right.
  4. Decide refund methods and permissions — Refunds & disputes.
  5. Place one real order with a real card, and refund it.

Related: Gateway setup · Taxes & charges · Refunds & disputes · Wallet

Was this page helpful?