TM-Ai20
The TM-Ai20 is a face access terminal and the family head with QR support: residents walk in on their face, visitors tap their phone against the same glass. The gate design is one device, and the crowd splits itself.
Key specifications
| Function | Face access terminal with QR credential lane for visitors |
|---|---|
| QR lane | Code-based visitor access — phone display or printed pass (config) |
| Face capacity | 5,000–50,000 class across models; per-unit value via model table (config on request) |
| Fingerprint | 1,000–1,600 templates on compatible variants (config on request) |
| Card capacity | 100,000+ credential store class (card module optional) |
| Verification speed | 0.3 s class |
| Liveness | Dual-lens RGB + IR, photo/screen rejection |
| Mounting | Wall-panel class, indoor geometry (40–70 cm face distance envelope) |
| Power | DC12V 2A |
| Network | TCP/IP |
| Warranty | 2 years |
Full specification
| Parameter | Value | Note |
|---|---|---|
| Product line | Face access terminals · family head, QR variant | TM-Ai family |
| Recognition | Face (1:1 / 1:N), 0.3 s class | Family spec |
| QR credential | Code lane for visitor passes | Per config |
| Liveness | Dual-lens RGB + IR | Photo and screen attacks rejected |
| Door control | Relay output, exit-button input | Direct lock wiring |
| Power input | DC12V 2A | Controller PSU or adapter |
| Networking | TCP/IP | 48h FAE install help |
| Environment | Indoor/sheltered class | Canopy gates |
| Warranty | 2 years | From first unit |
Line values per catalog are family-class figures. TM-Ai20-specific figures are stated in the datasheet extract and confirmed by the FAE on request. Exact capacities and options by model vary — the sales team confirms the per-SKU matrix within 48h.

Nobody registers a doorbell for the courier.
Visitor handling is a state machine that usually ends at a shouting intercom. With QR support, the gate gives the visitor an independent action: the invited code from the host, the camera doing its own job.
- Code turns into an event — QR pulses logged, so the visitor, the host, and the record agree.
- Face and code parallel — your staff keeps their face inside; invited read their pass. No kiosk machine on top of the door.
- Host-issued access — the invite config is software-side, so a change of policy doesn't involve a schematic.
Nearby in the line
TM-Ai20 FAQs
Yes — codes are software issued and revoked in the same view punches live; the QR lane reads whatever the host config publishes at the gate.
Printed and display codes of the pass class are both read (config); glossy small print is a formatting nuance the FAE team checks against your template.
No — lanes are independent; the 0.3 s face class stands, and the QR lane reads in parallel with the same events ledger.
Visitors used to be a doorbell problem. No more.
Show us your invite flow — get the QR-lane config matrix and sample offer within 48h.



