A palm-identity layer for apps, POS and service points. The journey covers identity establishment, enrolment, activation and subsequent verification; partners retain membership, attendance and payment decisions.
An identification result does not itself establish membership benefits or payment authority. Organisations, devices, merchants and purposes must be correctly linked before activation.
Two enrolment routes: mobile palmprint first or PalmDevice capture, with separate palmvein completion conditions.
SaaS, SDK/API and BackOffice under the agreed scope.
Partner applications consume results and apply business policy.
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.
Select one service point and use case. Test enrolment, activation, failed verification, revocation and disconnection; the partner confirms business outcomes independently.
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_TrustedPalmID_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.
