Guests waiting for the check, busy checkouts and delivery collections may use different devices, but they are all sales from the same restaurant. MagicPay connects restaurant payment acceptance through check and order references. Android POS works at the table, QR on the guest's phone and Soft POS during courier delivery. Branch transaction and collection reports come together in a shared dashboard.
Collections suited to your service model
Bring payment to the guest. Use Android POS at the table, open the relevant payment request with QR or take Soft POS collections on delivery using a compatible NFC-enabled Android phone. The order relationship remains intact when the channel changes.
- Separate server, cashier and courier roles.
- Bring split payments together under the original check.
- Follow refunds and cancellations from sales history.
Give the branch and center the same check
Branch, device and user information is part of each payment. Checkout teams follow the paid and outstanding amount; finance reviews the provider and reconciliation relationship. Payment investigations use a shared transaction record rather than service messages.
Connect restaurant flows in three steps
Launch service and collections together.
- 1. Identify check, table, branch and user references.
- 2. Connect payment channels used at the table, checkout and delivery.
- 3. Test split payments and refunds, then monitor branches in the same dashboard.
Who is it for?
Restaurant and cafe chains, quick-service locations and delivery teams. Where a business has several service models, each is tracked through a shared check relationship. The Restaurant Solutions page presents the detailed operational workflow.