UPI QR, online checkout and counter confirmation explained

Separate the order from the payment

A guest can open a menu, submit an order and open a payment app without the restaurant having received confirmed funds. Treat those as separate events. The cashier's job is to know which payment flow the shop is using and which confirmation it requires.

ScanFirst subscription checkout is another separate payment: it pays for the restaurant's software plan. It should not be confused with a diner's bill.

What a static UPI QR does

A static payment QR helps the customer open the payment app with the shop's configured payment details. Displaying or scanning that QR does not, by itself, tell ScanFirst that a bank payment succeeded.

For a staff-recorded UPI payment, the counter must confirm collection before settling the bill. Use the payment method that matches what actually happened. The same principle applies when recording cash or a card payment taken through a separate terminal.

Do not train staff to settle a bill simply because the customer shows a payment screen. Follow the shop's own collection and verification procedure, and check the receiving account or terminal information appropriate to that payment method.

How verified online checkout differs

An online checkout uses a configured provider and its verification flow. Payment references are checked rather than trusting a browser message alone. Subscription activation also requires captured funds matching the expected order, amount and currency, with no refund recorded.

If the browser closes after payment or confirmation takes longer than expected, registration offers a payment-status check. A saved checkout keeps its original amount. An authorized payment that is still processing is not a reason to start another payment attempt.

Configure accepted methods before service

In branch operating setup, review the methods the counter will accept and the payment details shown to guests. Confirm the receipt identity and the tax settings applicable to your operation before live bills are created.

Be clear about who can settle bills and who can only view history. Staff should use their own accounts with the appropriate role. A kitchen account does not need payment permissions merely to prepare an order.

Keep a simple counter checklist

1. Find the correct guest or table bill.
2. Check the order and total before collecting payment.
3. Confirm collection through the method your shop actually used.
4. Record the matching tender and settle the bill.
5. Check the receipt and use payment history when investigating a discrepancy.

Hardware and payment-provider fees are separate from the ScanFirst subscription. Review those arrangements before buying equipment or enabling a payment workflow.

Use practice and live records appropriately

The sample demo simulates collection so staff can understand the steps. It moves no money and creates no real bill. Your branch's first-settlement milestone completes only from a real settled bill, which also affects operational records and reports.