Iframe Overview
The Heuristik Iframe embeds a fully hosted biometric identification UI into your application. It runs on iframe.heuristik.com and communicates results back to your page via postMessage.
How it works
Key characteristics
- Hosted UI — runs entirely on
iframe.heuristik.com, no frontend code to build or maintain - Hardware required — needs a fingerprint scanner connected via USB and the local driver running (both provided by Heuristik)
- Staff authentication — clinic staff log in inside the iframe before scanning
- Results via postMessage — the iframe sends
{ HHID: string, isNew: boolean }to the parent window - Token-based access — a
tokenIframeprovided by Heuristik authorizes the integration - Third-party cookies required — the iframe needs cross-origin cookies for session management
When to use the Iframe
| Iframe | JavaScript SDK | |
|---|---|---|
| Integration effort | Minimal — embed an <iframe> tag | Medium — install package, write code |
| UI customization | None — hosted UI as-is | Full control over UI |
| Hardware dependency | Fingerprint scanner + local driver | Fingerprint scanner + local driver |
| Authentication | Staff logs in inside the iframe | Your app handles auth via SDK |
| Result delivery | postMessage to parent window | Callback functions in your code |
| Best for | Quick integration with no frontend changes | Custom workflows and UI |
When to choose the Iframe
Use the Iframe when you want the fastest integration path and don't need UI customization. If you need control over the identification flow or UI, use the JavaScript SDK instead.
Prerequisites
Before integrating the Iframe, ensure you meet all requirements. In summary:
- Fingerprint scanner and local driver (both provided by Heuristik)
- Iframe token (provided by Heuristik)
- Third-party cookies enabled for
iframe.heuristik.com