Trusted Palm ID / identity servicesDelivery scope.
Delivery scope.
Responsibilities without ambiguity.
Creator/GRGBanking cooperation model supplied by Mobile-ID. The framework is a proposal, not a signed delivery agreement.
Reference responsibility matrix.
| Scope | Creator / supplier | Mobile-ID | Customer |
|---|---|---|---|
| Hardware / firmware | Supply model records and updates | Integration testing and profile selection | Mounting, power/network and on-site operation |
| SDK / engine | Scope, versions and tests per supplier record | Bind engine to service and policy | Approve processing environment |
| Identity / binding | Agreed capture interface | Source integration and session controls | Business identity, processing authority and operators |
| Data & evidence | Declare engine data handling | Configure domain separation, logging and requests | Purpose, retention and access authorization |
| Incident / replacement | L3 within the supply scope | L2 integration, revocation and recovery | L1, local containment and support approval |
Tiered support, governed by agreement.
- 01L1 / on-site
- 02L2 / Mobile-ID
- 03L3 / supplier
Start with a controlled PoC.
Define purpose, devices, risks and acceptance criteria before scaling.