Covers three intake channels: a service desk, a mobile app and a website handing off to an appropriate capture component. It distinguishes card reading, data/chip checks and verification of the presenting person.
Successful capture does not establish that every check passed. Fields may be absent depending on card type and access rights; channel handoffs must preserve the case and session.
Desk Agent/readers and native NFC on iPhone/Android under tested combinations.
Separate document/chip checks, facial matching and PAD.
The Backend validates outcomes before updating the case.
Infrastructure components, applicable documentation and integration support within the agreed scope.
Business systems, permitted data, decision authority and end-to-end acceptance.
CAs, banks, device suppliers or data sources as applicable; confirm connection rights and conditions separately.
The source is a proposal. Product scope, release, SDK/API, connections and usage rights require confirmation for the deployment combination; diagrams and mockups do not establish production readiness.
Accept one specific combination: card reading, verification, expired session, unsupported card, cancellation and duplicate results. Record field provenance and each check outcome.
Discuss pilot scopeLightweight offline WebP presentation. The original PDF opens only when you choose it.
Vietnamese presentation · the PDF has not been translated.
The editorial summary is based on the sections linked above. The original PDF is unchanged. An observed version is not confirmation of current commercial status.
Open source document · online
Knowledge HubMobileID_CheckID_eID_Integration_Proposal_V3 1.pdfBrings document tasks into conversation: locating cases, reviewing requests, updating, approving and signing within permissions. GoPaperless manages workflows, versions and evidence; ChatGPT helps users understand and prepare actions.
Proposes access to organisational work and Mobile-ID services in ChatGPT. GoPaperless SSO links identities, while each service independently checks permissions, states and prerequisites.
A proposal for adding OIDC/FAPI and Passkey sign-in and Palm/Facial verification to an existing banking channel. Three integration points are separated: BFF for sign-in, Web SDK for interaction and Backend for evidence validation. Transaction decisions and posting remain with the financial institution.
Share your current systems and intended outcomes to plan the next integration step.
