# Trusted PalmID: verification at service points

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.

## Problem

An identification result does not itself establish membership benefits or payment authority. Organisations, devices, merchants and purposes must be correctly linked before activation.

## Scope

- 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.

## Boundaries

PalmID differs from PalmPay. Biometric verification is not transaction authorisation or posting; proposed endpoints are not evidence of a released production API.

## Prerequisites

- Agree identity establishment, capture permissions, devices and alternatives.
- Agree OS, SDK, firmware, merchant binding and data permissions.

## Pilot

Select one service point and use case. Test enrolment, activation, failed verification, revocation and disconnection; the partner confirms business outcomes independently.

## Source document

https://docs.mobile-id.vn/Proposals/MobileID_TrustedPalmID_Integration_Proposal_V3%201.pdf

V3; 36 pages; Vietnamese PDF.

Observed source version; confirm implementation scope.
- Delivery scope: 8
- Journey and enrolment: 11
- PalmID and payments: 19
- Membership and attendance: 23
- Architecture and integration: 25
- Implementation and acceptance: 30