How QR access works
Guests scan a printed QR code with their phone camera to open a link. The destination can be a live menu with ordering and payment, or a read-only menu. A static QR link can be copied, so any verification of table access depends on the ordering system.
How NTAG 424 NFC tags solve table identity
Each MesaFlow table card uses an NTAG 424 DNA chip with Secure Dynamic Messaging (SDM). A tap supplies a read counter and a message authentication code (MAC). MesaFlow verifies the tag data on the server before opening the table's live menu.
Side-by-side comparison
| Capability | MesaFlow NFC (NTAG 424) | Printed QR Code Menu |
|---|---|---|
| Guest action | Tap phone on table tag; no camera app needed | Open camera, frame code, tap link |
| Table verification | Cryptographic UID + counter + MAC per tap | The QR opens a link. Verification depends on the platform. |
| Low-light reliability | Works in any lighting via NFC | Struggles in dim dining rooms or glare |
| Menu & kitchen sync | Live menu, modifiers, waiter call, and kitchen board | Live ordering and kitchen integration depend on the platform |
| Branding | White-label guest menu with your palette and fonts | Branding options depend on the platform |
When a venue should switch from QR to NFC
- You want dine-in guests to order or request the bill without downloading an app or creating an account.
- You want the server to verify the NFC tag associated with the table.
- You want your restaurant's own typography, colours, and multi-language menu on the guest's screen.
Next: See how MesaFlow NFC table ordering works or return to the MesaFlow overview.