Provider lock-in
Different APIs, status models, document formats and authentication mechanisms.
← Home
CONTUM PRODUCT · SIGNING API
The business API for signing.
Business applications do not need a separate integration for every signing solution. Contum’s Signing API provides one business-facing API for signing services, manages the workflow and returns the result to the application.
In production at NN Hungary and K&H Bank
An integration core that handles signing in the language of the business system — process, document, participant, status and result.
Business APIApplications use a consistent interface to start and track signing workflows.
WorkflowCoordinate multiple signers, documents and dependent signing steps.
Multi-providerAccess multiple signing platforms and trust providers through one integration.
Starting point
The business application should not need to understand every detail of signing.
Direct point-to-point connections multiply quickly. Signing API maintains a stable contract between changing signing technologies and business channels.
Business complexity
Multiple signers, different methods, document packages and conditional steps.
Many channels
Portal, mobile, branch, advisor and back-office systems consume the same capability differently.
Changing regulation
Add new providers and signing methods without rebuilding every business application.
Capabilities
Turning technical signing into a business service.
REST business interface
Create processes, provide documents and signers, query status and retrieve results.
Complex signing workflows
Multiple participants and documents, with predefined signature methods and authentication steps configured for the business use case.
Webhooks and status polling
The business application can receive automatic change notifications (webhooks) or regularly request the current signing status (polling).
Connecting signing services
Comprehensive Namirial support and integration of additional trust services for the functions required by each project. DÁP eSignature integration is under development.
Journey integration
Native signer UI, embedding, redirects, link-based launch or mobile webview.
Audit and operations
Trackable states, errors, retries, logs and business-level monitoring.
Signature validation
The solution uses EU DSS (Digital Signature Services), the European Commission’s open-source software for signature validation. It is available through Signing API or as a standalone component.
Integration
One common core between many business applications and many signing services.
Signing API decouples enterprise channels from the provider layer, concentrating change in one integration point.
Business channels
Mobile banking, portal, CRM, core system, branch or partner application.
→Business contract
Unified request, document, participant and status model.
→Signing API
Validation, templates, workflow, orchestration, exception handling and audit.
→Provider adapters
Namirial Sign Enterprise and trust services selected for the use case; DÁP eSignature connectivity under development.
→Document and evidence chain
Signed result, audit package, validation and hand-off to DMS / Trusted Archive.
Journey
How the integration works.
The developer interface stays simple while the complete business signing process remains configurable behind it.
Create request
Pass use-case template, documents, participants and business metadata.
Assemble process
Select signing method, provider, sequence, authentication and customer UI.
Execute
Serve signers, call providers and manage conditional actions.
Status and events
Webhook or query for individual actions, exceptions and completion.
Result package
Deliver signed documents, audit data and validation to the target system.
Use cases
Where Signing API adds the most value
Many countries, one application
A common business API with country-specific provider and legal-effect variations behind it.
Many channels, one process
Web, mobile and branch experiences share one central workflow.
Provider change
Connect a new QTSP or signing component while minimising business-system changes.
DÁP and EUDI extension
Add new identity and signing channels to the existing enterprise process.
Production references
NN Hungary uses Signing API as its signing platform. K&H Bank introduced the solution in April 2026.
Delivery
Product and expert integration together.
Signing API is not a generic ESB. It is built on more than a decade of Contum electronic-signature delivery and proven industry patterns.
Use-case catalogue
Process and signature types, channels, exception paths and business states.
API and security design
Authentication, network model, data transfer, logging and entitlements.
Adapter and workflow
Provider links, templates, callbacks and business rules.
Live support
Monitoring, incidents, versioning, new use cases and new providers.
Interfaces and connections
REST / JSONSES · AES · QESPDF / PAdESNamirial Sign EnterpriseEU DSSECM / Trusted Archiving
INTEGRATION QUESTION
How many signing connections does your application landscape maintain today?
We can show how provider and channel complexity can be simplified behind one stable business API.
Signing API consultation↗