Usage
There are two ways to integrate with Scrive eID Hub: using the eID Hub frontend or going API-only.
| Approach | Best for | Effort |
|---|---|---|
| eID Hub Frontend | Most integrations | Low (same code for all providers) |
| API-only | Custom UI, headless or server-driven flows | Higher (you own polling, UI and provider quirks) |
eID Hub Frontend
The Hub frontend handles the provider-specific UI, polling, QR rendering, app-switching and error states for you. You create a transaction, redirect the user to accessUrl, and read the result when they return. The same three steps work for every provider. You can also configure the Hub with a custom logo, title, and background colour to match your brand.
accessUrl can be redirected to or opened in a popup, but cannot be embedded in an iframe. This is enforced both by Scrive and by most eID providers: iframes prevent users from verifying the URL in the address bar, cause third-party cookie issues across browsers and platforms, and are more vulnerable to malicious external scripts and browser plugins.
API-only
For headless or custom UI flows, you can drive the API directly without the Hub frontend. This is supported by most providers, but not all. A few require the Hub frontend due to hosting restrictions imposed by the provider.
In API-only mode your application owns the UI, polling cadence, QR rendering and all provider-specific behaviour.