Electronic signature
Signing binds you. Only if you can prove it did.
An electronic signature is worth what the chain around it is worth: the signer’s identity, the key that signed, the timestamp and the audit trail. When one link is missing, the file reopens and the burden of proof sits with you. That holds for an administrative act, a banking contract or a business application flow.
What you sign binds you for years to come
Identity, key, timestamp, audit trail: the requirements do not change from one use to the next. What changes is who will contest the signature, and when.
States, agencies, public procurement
Public bodies and national programmes
Digitising an act moves its evidentiary value onto the signature. It has to rest on an authority the country’s law recognises, not on a foreign service.
- Digital public procurement and electronic invoicing
- Administrative acts and official correspondence
- Qualified signature backed by the national authority
- Operated on your own territory
Banks, insurers, telecoms, energy
Enterprises
Contracts, subscriptions, orders, slips: every signed flow becomes evidence you will have to produce years later, at a customer’s or a regulator’s request.
- Multi-signer workflows, in branch or at a distance
- Server sealing for documents issued in volume
- Profiles, SSO and two-factor authentication
- Audit trail and a dashboard of transactions
CIOs, integrators, business software vendors
Application teams
Signature integrates into your applications by API, without sending the user off to a third-party portal. Keys stay in an HSM or on the signer’s token.
- Signature, authentication and verification APIs
- Remote keys (HSM, Cloud Signature Consortium) or a local token
- PAdES, XAdES and CAdES formats: creation and validation
- On your own infrastructure or as hybrid SaaS
The product, and what surrounds it
NGSIGN is the product. The signature level to adopt, the authority that issues the certificates and the integration into your applications are decisions we work through with you.
Our products
NGSIGN
Electronic signature and server sealing
- Remote keys (HSM, Cloud Signature Consortium) or a local token, at the signer’s choice
- PAdES, XAdES and CAdES formats: creation and validation to ETSI EN 319 102
- Signature, authentication and verification APIs for your business applications
- Multi-signer workflows, parallel or sequential, and customisable
- Signature and visible electronic stamp combined in a single signing file
Advisory, integration, training
- Scoping the signature level (simple, advanced, qualified) against the regulatory frame
- Connection to your certification authority, existing or yet to be built
- Integration into business applications by API
- Preparation for homologation and compliance audit
- Training for the teams who will operate the platform
The certificate comes from an authority. Yours, or the one we build with you →
No vendor agreement steers our recommendation
We are tied to no vendor. The platform we recommend follows from the programme’s constraints: sovereignty, certification level, existing estate, cost of operation. We stay accountable for the result in production whichever product is chosen. The choice follows the requirement, never the other way round.
Standards we build to
PAdES signatures for PDF, XAdES for XML, created and validated to the ETSI standards. The references that make evidence hold up.
- PAdES · ETSI EN 319 142 · Baseline B, T, LT, LTA
- XAdES · ETSI EN 319 132 · Baseline B, T, LT, LTA
- CAdES · ETSI EN 319 122
- Validation · ETSI EN 319 102
- eIDAS (UE) n° 910/2014
- ETSI EN 319 411-1 / 411-2
- ETSI EN 319 421 / 319 422
- X.509 · RFC 5280
- Common Criteria (HSM)
- 2D-DOC (ANTS) · ISO 22376:2023
Let’s talk about your needs before we talk about product.
Tell us the regulatory framework and the scale you’re aiming at. We’ll tell you what actually needs building, including if it turns out to be less than you thought.