Connects VNeID sign-in, updates from authorised information sharing and signing within familiar desktop tools. The Agent bridges document applications and the configured signing service.
Sign-in, information-sharing consent and signing authorisation are distinct decisions. Signing support depends on the operating system and application integration mechanism.
Windows: CryptoAPI/CSP and CNG/KSP, tested per OS and application.
macOS: CTK/CryptoTokenKit, subject to release package and Intel/Apple Silicon support.
Distinguish PDF signing, native Office signing and Office-to-PDF conversion followed by signing.
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.
Test one selected combination on sample documents. Cover sign-in, optional information updates, cancellation, signing, verification and saving; record native Office and PDF routes separately.
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 HubGoPaperless_Agent_Proposal_V2 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.
