VNeID / Passkey
End-user signing journeys.
Signing →Integrations
Integrations
Choose integrations by task: Identity, attribute sharing, signing routes, providers and desktop applications.
ON THIS PAGE
INTEGRATION SURFACES
Mobile · Desktop · API
GoPaperless Agent
Bring remote signing into existing applications.
Agent →REST API
Embed transactions inside business software.
Developers →ENTERPRISE SYSTEMS
Business systems above, signing ecosystem below.
- 01Business application
Request and correlation reference
- 02Mobile-ID
Orchestrate → redirect → track
- 03RAR/C06 / VNeID / RS-HUB
Contract-scoped services; user authentication and consent where applicable
- 04CA / RSSP
Separate signing authorization → signature → verification
OPERATIONAL NOTES
Implementation decisions · Integrations
Identify the source system, Mobile-ID, identity service and signing provider at each trust boundary.
For each integration, document request, callback/result, correlation reference and publication status.
Design cancellation, timeout, denial, provider-unavailable and reconciliation paths before go-live.
INTEGRATION MAP
Integrations are described by boundaries rather than partner logos
Each integration should identify caller/callee, shared context, created transaction, returned failures and retained evidence.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Channel | Role | Boundary |
|---|---|---|
| Agent | Desktop bridge | Local application ↔ Agent ↔ signing ecosystem |
| REST API | System integration | Business backend ↔ Sign transaction model |
| VNeID SSO | Authentication | Identity/session; not signature creation |
| ShareInfo | Attribute sharing | Purpose/consent-bound attributes |
| RS-HUB | Signing route component | Not the entire signing service |
| CA/RSSP | Trust/signature provider | Credential/certificate/signature scope |
Source of truth
Business data and business decisions remain with their source systems; an integration does not make Mobile-ID the source of truth for every object.
BROWSE
Explore detailed guidance
Choose a topic to review implementation details.
CA/RSSP & Signing ProvidersNormalize how applications work with multiple signing providers without hard-wiring business UX to each provider.Desktop Compatibility CenterTrack GoPaperless Agent compatibility by application, version and operating system.RAR/C06 IntegrationSeparate SSO, ShareInfo and remote-signing routes in the integration architecture for services provided through RAR/C06.RS-HUB in the Signing RoutePosition RS-HUB as an external component/route in signing, separate from SSO, ShareInfo and Mobile-ID orchestration.ShareInfo & Controlled Attribute SharingDescribe consent/authorization and attribute sharing within actual service scope without expanding it into an entire KYC process.VNeID SSOAuthentication/session establishment is an identity layer and is not the same as a digital-signing transaction.
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