Going live

The checklist before your digid integration reaches real customers.

Work through this list before you release. Each item links to the page that explains it.

Licence

The product's production licence is active (its first invoice is paid) and lists every app that will run the SDK: Android package and signing certificate (the Play App Signing certificate if Google signs your releases), iOS bundle id, web origins. See Licences and renewal.
The released app uses the production key, not the sandbox key.
The licence includes every feature your flow uses: card reading, the selfie (face match and liveness), fingerprints.
Your app logs the licence status at start-up (state and reason, never the key itself) so a key that fails to apply is noticed.
A release build shows no "Evaluation" tag. Results have evaluation: false.

Your app sets a usage sender and calls online() when it has a connection.
Your app gives the SDK a usage store, so counts and the phone's counter survive restarts.
Pay as you go: your app calls renewLicence regularly (for example daily, when online), keeps the key it returns and applies it at the next start. It handles usage_report_missing and insufficient_credit.
Pay as you go: someone watches the product's credit in the customer portal and tops it up before it runs out.

screens.result.download is false: the document goes to your backend, not to the person's device.
flow.documents, flow.require_back and engine.expiry_policy match your process.
Consent: if your process needs it, screens.consent shows your text and a link to your privacy notice.
Both languages read well with your string overrides, if any.
The camera permission prompt explains why your app needs the camera (NSCameraUsageDescription on iOS).
Tested on low-end phones your customers actually use, in poor light, with worn cards.

The document reaches your backend only over TLS, with your app's authentication.
The backend runs every check in Verify on your backend: schema, tamper check, evaluation flag, freshness, document type, verdict, expiry, face.
review results reach a person, with the checks' details to look at.
The document and fingerprint images are never written to logs, analytics or error reports.
You keep the document only as long as your retention policy says. See Privacy and security.

The SDK files, the engine and the model pack are served from your own origin over HTTPS, with .wasm as application/wasm.
Your content security policy allows 'wasm-unsafe-eval' for scripts, also on the worker script.
Your Permissions-Policy header does not disable the camera.

Someone on your team can sign in to the customer portal to download keys, see usage and pay invoices.
Your support team knows what the person sees: the steps, the English and Swahili guidance, and what "Needs review" means for them.