Visible electronic stamp
The document is checked where it is presented
An official document travels printed, photocopied, photographed. At the counter, nobody has access to the system that issued it. The visible electronic stamp prints a scanner-readable signature onto it: the evidence travels with the document and is checked offline, by any third party.
Every document you issue will be imitated
Identified issuer, sealed content, verification with no access to the system: the requirements do not change from one document to the next. What changes is who presents the document, and to whom.
States, agencies, registries
Public bodies and citizen services
Certificates, extracts, diplomas, permits: every document issued to a citizen is one somebody will try to reproduce, and one another counter will have to accept.
- Official documents and e-government services
- Verification by any third party, with no account or system access
- Built to 2D-DOC, the scheme run by ANTS
- Verification app for Android and iOS
Banks, insurers, operators, manufacturers
Enterprises and issuers
Invoices, certificates of conformity, delivery notes, labels: the stamp binds the document to its issuer and makes counterfeiting detectable at the first scan.
- Anti-counterfeiting and identification of products
- Traceability and asset tracking
- Document templates and CEV certificates managed centrally
- Generation by API inside your document chains
CIOs, integrators, business software vendors
Application teams
The stamp is added to an existing document chain: one API call at generation, one SDK at verification. Nothing changes in the document itself.
- Generation and verification APIs
- Mobile SDK to carry verification into your own application
- Separate generation and verification servers
- Signed Data Matrix, ISO/IEC 16022
The product, and what surrounds it
QRSecure is the product. Which documents to stamp, which authority issues the CEV certificates and how counters will verify are decisions we work through with you.
Our products
QRSecure
Visible electronic stamp
- Generation and verification of the visible electronic stamp
- Offline verification, with no access to the issuing system
- Verification app for Android and iOS
- Simple APIs and SDKs to carry generation and verification into your applications
- Management of CEV certificates and document templates
Advisory, integration, training
- Scoping which documents to stamp and what content to seal
- Connection to your certification authority for the CEV certificates
- Integration into document chains by API and SDK
- Preparation for homologation and compliance audit
- Training for the issuing teams and for the verifying teams
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.