VietQR payments on F&B POS in 2026: configure it right for automatic reconciliation

VietQR is now the default payment method in Vietnamese F&B — cheaper than card terminals, faster than cash counting, no monthly POS fee from the bank. But "having a VietQR sticker" and "having VietQR properly integrated into your POS" are very different things, and the difference shows up at month-end when your cashier and your bank disagree by 380k VND.

Here''s how to set it up so the reconciliation just works.

The four levels of VietQR integration

Level 0: Static QR on the wall

A printed QR linked to your owner''s personal bank account. Customer scans, types the amount, sends. You "trust them" or check the bank app. This doesn''t reconcile with anything. It''s fine for street stalls, dangerous for any business with employees.

Level 1: Dynamic QR per transaction, manual entry back

Your POS generates a unique QR with the exact amount baked in. Customer scans and pays in one tap. But the payment confirmation never flows back to the POS — your cashier sees "paid" on their phone and marks the POS transaction "VietQR" manually. Reconciliation is a daily Excel chore.

Level 2: Dynamic QR with bank webhook

Same QR generation, but your bank pushes a webhook to your POS the moment payment lands. The transaction auto-closes. Reconciliation against bank statement is automatic. This is the minimum acceptable setup for any restaurant with >1 employee in 2026.

Level 3: Dynamic QR + webhook + tip handling + refund flow

Level 2 plus: customer can add a tip via the QR flow, the POS handles partial refunds back via VietQR (using NAPAS 2.0 refund APIs), and split-payment scenarios (half QR, half cash) just work.

Most Vietnamese POS vendors are at Level 1 or claim Level 2 but don''t fully implement it. Test before you trust.

What to check during vendor demo

1. Show me a live VietQR payment that closes the POS ticket automatically. Not "it will in the next release." Now.
2. What''s the latency? Should be under 8 seconds from customer paying to cashier seeing confirmation. Anything over 15s causes line jams.
3. What bank account does the money land in? It must be a business account, not the owner''s personal account, for tax compliance.
4. What happens on failed payments? Customer''s app shows success but webhook never fires (this happens ~0.5% of the time). Your POS must have a reconciliation tool to catch these.
5. Can I refund via VietQR? Or do I have to do cash refunds? Cash refunds defeat half the point.

Bank choice matters

Not every Vietnamese bank exposes the webhook API to small business accounts. The current realistic options for full Level 2/3 integration:

• MB Bank — best API documentation, fast webhooks
• VPBank — good for VIP business accounts
• Techcombank — reliable but more enterprise-focused
• VietinBank — works, slightly slower webhook
• Vietcombank — possible but requires sponsorship for API access

If your current bank isn''t on this list, opening a second account at MB or VPBank purely for QR collections is often the fastest path. Sweep funds to your main account weekly.

Reconciliation rules that prevent the "missing 47k" problem

Configure these in your POS:

• Match window: Webhook arrival within 3 minutes of POS ticket creation = auto-match.
• Amount tolerance: Zero. If the amount doesn''t match exactly, flag for review.
• Memo parsing: VietQR memos include the order ID — make sure your POS reads it.
• Unmatched queue: Any inbound bank credit not matched to a POS ticket within 30 minutes shows up on the manager''s phone, not lost in a spreadsheet.
• Daily close lock: Cashier can''t close the day until unmatched queue is empty.

What VietQR doesn''t replace

VietQR is brilliant for instant payments under 10M VND. It''s not great for:

• Corporate clients who want a card receipt or invoice with tax code (use NAPAS card or e-invoice)
• International tourists without Vietnamese banking apps (still need card terminal)
• Subscription/recurring billing for membership programs (use Visa/Mastercard direct debit)

Most restaurants need VietQR + one card terminal as backup. That covers 99% of payment scenarios.

Cost reality

VietQR transaction fees in 2026:

• Inbound to your business account: 0 VND (banks compete on this)
• POS integration fee: usually bundled, sometimes +200k/month
• No monthly terminal rental like with card POS

Compare to card terminals at 1.5–2.5% + 200–500k/month rental. For a restaurant doing 200M/month, switching to VietQR-primary saves 4–5M/month.

Bottom line

The technology is there. The banks are there. The customers already prefer it. The only question is whether your POS implements it as Level 2/3 — or whether you''re still in Level 1 and reconciling by hand. Audit your current setup this week.

Related reading

• POS-MISA accounting integration
• GrabFood and ShopeeFood integration

Why this matters in 2026

Multi-outlet F&B operators across Vietnam and Southeast Asia are running into the same wall in 2026: aggregator commissions compress margins, food-cost drift compounds across outlets, labour cost climbs faster than ticket size, and a traditional POS only surfaces the damage at month-end when the only response left is firefighting. Operators who win in 2026 close the loop in hours, not weeks — variance flags before the next shift, demand forecasts before purchasing, daypart promos drafted automatically for slow slots, and a single morning brief instead of five dashboards. That is the bar this guide is written against, and the reason LOOP exists. The cost of a missed signal is no longer a single bad week — it is the difference between a chain that compounds outlet-level profitability and a chain that opens new outlets to mask the leaks at the old ones.

The SEA F&B operator landscape in 2026 also looks materially different from 2023. Aggregator commissions in Vietnam have settled in the 22–28% band; Thailand and the Philippines run higher, Singapore lower. Labour minimums have moved twice in eighteen months in Vietnam. E-invoice (TT78) is now non-negotiable and enforced. Loyalty has shifted from punch cards to messaging-native (Zalo OA, LINE, WhatsApp, Messenger) — and the chains that ride that shift are seeing repeat visits double inside ninety days. None of that lands as an upgrade on a legacy POS; it lands as a different operating model.

Operator playbook — first 30 days on LOOP

Week 1 — Foundations. Import menu, recipes, modifiers, customers, loyalty balances and 24 months of sales via CSV. Connect aggregators (GrabFood, ShopeeFood, Be, foodpanda, Gojek). Configure e-invoice provider (MISA / Viettel / VNPT). Confirm payment rails (VietQR for VN; PromptPay / QRIS / DuitNow / PayNow / QR Ph for the rest of SEA). Train two staff per outlet on voice and text commands; the rest pick it up by observation in days 4–7.

Week 2 — Variance and forecast online. Switch demand forecasting on at daypart level. Set variance alert thresholds (default: food-cost ±3pp, labour ±2pp, void rate ±0.5pp). Let the system run a full week without intervention so the baseline calibrates. Review the morning brief each day; ignore the urge to override — by day 10 the forecast typically holds steady.

Week 3 — Promo and loyalty loop. Turn on daypart promo drafting for the two slowest hours per outlet. Connect Zalo OA / LINE / WhatsApp for delivery; start with a single segment (e.g. lapsed-30-day) and a single offer. Measure incremental visits, not coupon redemptions.

Week 4 — Compound. Roll the same flow to a second outlet, then a third. The operating model is the same at outlet 2 as outlet 20 — that is the point of LOOP.

KPI table — what to watch

Common pitfalls SEA operators hit in 2026

Treating aggregator orders as a separate business. Operators who keep five aggregator tablets running in parallel lose roughly 4–7 minutes per peak hour to context-switching alone, and miss the per-aggregator margin picture entirely. Unifying the queue (one tablet, one KDS, one accounting line per aggregator) is usually the single highest-leverage move in the first 60 days.

Letting variance live in spreadsheets. A weekly food-cost review is a 7-day reaction time on a 24-hour problem. Variance has to live in the operating layer — flagged, attributed and routed to the responsible manager within hours, not aggregated to a Friday email.

Loyalty as a punch card. A 2026 loyalty programme is a messaging channel with attribution. If the only metric is "points issued", the programme is a cost centre. If the metric is "incremental repeat visits per segment per month", it compounds.

Forecasting at the wrong resolution. Chain-level forecasts are wallpaper. Daypart-and-outlet is the smallest unit that pays back — coarser is too vague to act on, finer is noise.

How LOOP solves this

LOOP is an AI-native restaurant operating system built for SEA F&B chains. Operators run their venues by voice or text command instead of clicking through dashboards. AI forecasts demand per outlet at daypart resolution (modelled accuracy published in our methodology), flags food-cost and labour variance within hours of the shift closing, drafts promos for slow daypart slots and pushes them to Zalo OA / LINE / WhatsApp, and delivers a three-item morning brief at 06:30 local time so the operator's first action of the day is informed. LOOP unifies GrabFood, ShopeeFood, Be, foodpanda and Gojek into one queue, supports VietQR / PromptPay / QRIS / DuitNow / PayNow / QR Ph, and ships VAT e-invoice (TT78) via MISA, Viettel and VNPT. Pairs with Peko loyalty (50% lifetime discount on LOOP for Peko customers).

Under the hood, LOOP is offline-first with a 90-second resync window so orders, payments and KDS keep firing through ISP drops; recipe-level COGS is computed at order time so every plate's contribution margin is visible before the shift ends; and the morning brief is generated from the previous day's variance, the current day's forecast and the next 14 days of bookings, weather and local events — not a static template. The result is fewer dashboards, faster decisions, and a noticeably calmer week for the operator.

Related guides

• LOOP blog — AI POS guides for SEA
• LOOP POS
• Peko Rewards loyalty
• VeLoop delivery aggregator unification
• LOOP pricing
• Compare LOOP vs other POS

FAQ

How fast can a SEA F&B chain switch to LOOP?

Typical cutover for 2–10 outlets is 5–10 business days: CSV import of menu, recipes, customers, loyalty and 24 months of sales, parallel run over a weekend, then cut over Monday open. Larger chains (20+ outlets) usually phase by region over 4–6 weeks.

Does LOOP work without stable internet?

Yes — LOOP runs offline-first with a 90-second resync window. Orders, payments and KDS keep firing during ISP drops; the cloud reconciles automatically on reconnect. Aggregator orders queue locally and dispatch when the link returns.

What does LOOP cost?

Per-outlet monthly pricing with no per-device upcharge. Peko loyalty customers get 50% lifetime discount on LOOP — see /pricing for the current band.

Does LOOP support VAT e-invoice (TT78)?

Yes — LOOP integrates with MISA, Viettel and VNPT as e-invoice providers. Issuance is automatic at order close and reconciles end-of-day.

Which payment rails does LOOP support?

Native: VietQR, MoMo, ZaloPay, VNPay for Vietnam; PromptPay (TH), QRIS (ID), DuitNow (MY), PayNow (SG), QR Ph (PH). Card acquirers are wired through local PSPs per country.