Scrive eID Hub has a new Age Verification endpoint that checks a configurable age threshold and returns only a true or false response.
Age verification should prove eligibility, not expose identity ↗
What happened
- The endpoint reuses identity methods already connected through Scrive eID Hub, including BankID, MitID and Freja.
- Where a national eID is unavailable or document-grade verification is needed, the same endpoint runs on Onfido instead.
Why it matters to Signicat
- Scrive positions age verification as an eID Hub feature, which overlaps Signicat's eID and Wallet Hub and age-check use cases.
- Scrive's Onfido fallback is a vendor-stated document route; the article gives no independent evidence of its performance.
Evidence from the source (4 quotes)
- “The verification process reuses trusted digital identity methods already connected through Scrive eID Hub, including BankID, MitID, Freja and more European eIDs and identity verification methods” source ↗
- “Where a national eID isn’t available, or where you need document-grade verification, the same endpoint runs on Onfido instead.” source ↗
- “Scrive eID Hub’s new Age Verification endpoint is designed around privacy-first verification and GDPR data minimisation.” source ↗
- “Where a national eID isn’t available, or where you need document-grade verification, the same endpoint runs on Onfido instead.” source ↗
Age verificationData sovereignty privacyeID brokeringProduct launchThought leadershipGlobal
3 of 3 facts verified against the source · confidence medium · claude-haiku-5-5