VNeID / RS-HUB
VNeID onboarding and mobile signing route with transaction status, callbacks and evidence.
VNeID / RS-HUB →GoPaperless Digital SigningOne Identity.
One Identity.
Multiple Signing Routes. Every Application.
One Integration · Multiple Signing Routes · Multiple CAs · Unified Evidence
Onboard with VNeID. Sign through VNeID/RS-HUB or Passkey. Extend the same signing ecosystem to Adobe/PDF and Microsoft Office through GoPaperless Agent, and to business applications through REST APIs.
Production claims, reference architecture and items requiring confirmation are explicitly separated.
Document and policyVersion • signer • authority
VNeID / RS-HUBApplicable identity and signing service route
GoPaperless AgentDesktop application handoff
REST APIAsynchronous transaction integration
Trusted SICTransaction-bound authorization
CA / RSSPSignature creation with the applicable key and certificate
Verification and evidenceOutput • state • correlation
01Unified transaction model
02Primary signing routes
03Access channels
∞Applications can integrate
03 ACCESS CHANNELS
One signing ecosystem. Three ways to access it.
Mobile for end users, Agent for desktop applications, API for business systems.
GoPaperless Agent
Connect PDF/Adobe-style and Microsoft Office signing workflows to the signing ecosystem.
GoPaperless Agent →REST API
Business applications create signing transactions and receive states, webhooks and results.
Developer Center →VNEID ONBOARDING
From trusted identity to signing readiness.
Identity information, consent, binding and signing eligibility should remain explicit—not hidden inside one button.
Document and policyVersion • signer • authority
VNeID / RS-HUBApplicable identity and signing service route
GoPaperless AgentDesktop application handoff
REST APIAsynchronous transaction integration
Trusted SICTransaction-bound authorization
CA / RSSPSignature creation with the applicable key and certificate
Verification and evidenceOutput • state • correlation
Describe VNeID authentication and attribute sharing only within the applicable service, consent, permission and legal scope.
SIGNING ROUTES
Two signing routes. One integrated experience.
Different trust routes. Consistent integration.
VNeID / RS-HUB
A VNeID-linked journey connecting RS-HUB and CA/RSSP according to the applicable integration model.
Explore architecture →ORCHESTRATED BYGoPaperlessPolicy · route · evidence
Passkey / Trusted SIC
Passkey supports authentication/authorization; the digital signature is produced by the applicable signing infrastructure.
Understand Passkey →GOPAPERLESS AGENT
Sign from desktop. Authorize on mobile.
Keep the familiar user workflow while moving the signing interaction into a modern signing ecosystem.
Digital signature
GoPaperless AgentSecure signing interaction bridge→
Authorize on mobile
VNeID / RS-HUB
Passkey
DEVELOPER EXPERIENCE
One API. Multiple Trust Routes.
Business applications integrate the signing transaction—not every underlying user journey.
Reference API ModelSIMULATED / NOT PRODUCTION
POST /v1/signing-transactions
{
"signer": "subject-ref",
"document_hash": "sha256:...",
"route": "AUTO"
}TRUST ARCHITECTURE
Trust does not stop at “Signed”.
Keep identity, authorization, signature creation, verification and evidence as distinct trust layers.
USE CASES
One platform, multiple transaction contexts.
Every vertical maps actor → application → identity → signing route → provider → evidence.
Banking & Finance
Onboarding, agreements, lending, securities, insurance and internal approvals.
Enterprise
Contracts, HR, procurement, finance documents and approvals.
Government / Public Services
Citizen transactions, forms and administrative workflows.
Software / SaaS
Embed signing with REST API, webhooks and application-controlled UX.
FAQ
Clarify the boundaries before implementation.
Passkey, Agent, RS-HUB, CA/RSSP and production/reference APIs are not the same layer.
What is GoPaperless Digital Signing?
A unified digital-signing access and orchestration layer across mobile, desktop and API channels. Business applications do not need to own every signing route or provider UX directly.
Is a Passkey a digital signature?
No. A Passkey can support strong user authentication and transaction authorization. The digital signature is produced by the applicable CA/RSSP signing infrastructure with the associated signing credential.
How are VNeID/RS-HUB and Passkey different?
They are different trust routes. VNeID/RS-HUB is tied to the VNeID-linked journey and integrated signing services; Passkey focuses on passwordless authentication and authorization. GoPaperless can orchestrate routes according to implemented policy.
What does GoPaperless Agent do?
The Agent is a desktop connectivity layer that lets familiar document-signing applications use the GoPaperless signing ecosystem without replacing the entire user workflow.
Does the Agent store the private key?
The website does not present the Agent as private-key storage. Private-key location and protection must be described according to the confirmed CA/RSSP/HSM/QSCD architecture.
Can I sign PDFs from Adobe?
PDF signing through Agent depends on the supported application, operating system, certificate and service configuration. Review the PDF guide and compatibility matrix before deployment.
START
Design the signing journey correctly from the start.
Choose Agent, API, VNeID/RS-HUB or Passkey according to the actual actor, application, credential and policy.
CAs and published cooperation scope
Mobile-ID publishes the module-specific cooperation below. This list does not establish that every CA is connected or available in a particular Sign configuration.
MISA-CA
MISA · TMS-RA · Remote Signing
Published cooperationEFY-CA
EFY · TMS-RA
Published cooperationNC-CA
HN · TMS-RA
Published cooperationTrustCA
Savis · TMS-RA · CA
Published cooperationMobile-ID published source · Partners and deployment records