A roadmap for post-quantum cryptography across certificate management, key protection, signing and verification. It separates local signing, server signing and evidence services, prioritising one pilot route rather than claiming ecosystem-wide readiness.
Keys, certificates and records have different lifecycles and compatibility. Algorithm migration must cover signer and recipient, certificate chains and validation policy.
Trusted Key for local signing; HSMs for infrastructure keys and server routes under specific configurations.
Composite at key, certificate and document-envelope layers represents three separate configurations.
Service rollout follows dependencies, testing and acceptance gates.
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.
Choose one issuance–signing–verification route on a fixed combination. Test invalid chains, wrong algorithms, altered data, revocation and recipient compatibility; retain reproducible evidence.
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_QuantumSafe_Ecosystem_Proposal_V5.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.
