Data integrity checks
Using the selected public key, verification checks the signature over the received data. Changes to signed content are detected during the check.
RRID — verifiable digital records for your product
Connect product, document or access data with a digital signature. A user submits a token for verification and receives a clear result about the integrity of its signed data.
The web verifier is available now. Token issuance, usage rules and integration are scoped around your workflow.
Packaged software under your own brand
RRID is a packaged software solution for a fast business launch. OEM delivery lets you launch the product under your own brand, with agreed branding, domain and capabilities.
The package, licence, hosting, integrations and support are defined in the delivery scope.
See how RRID verification works
Open the web verifier, insert the demonstration token and explore the result. A step-by-step product video will be added here later.
Video overview coming soon
This space will show RRID in action: from receiving a token to viewing its verification result.
Verifiable data through a clear user journey
RRID is useful when customers, partners or staff need to check digital records and understand what supports the result.
One path to a result
Token entry, a file or a QR code can lead into a common verification journey. The interface and status explanations can be adapted for your audience.
Separate usage conditions
Validity periods, limits and bindings are defined as business rules. They can be discussed and developed separately from the digital-signature mechanism.
A gradual rollout
Start with one type of record and a pilot group. Validate the user journey and integrations before extending the scenario across your product.
Who can benefit from RRID
We choose a specific workflow, participants and data. These scenarios illustrate potential uses; the implementation scope is agreed separately.
Brands and manufacturers
Digital product, warranty or service records. Customers and partners gain a way to verify signed information associated with your system.
Education and professional platforms
Verifiable digital confirmations of training, qualifications or participation. Recipients can refer to the signed record and its verification result.
SaaS and partner services
Tokens for service workflows with validity conditions, expiry and bindings. Access rules become part of the product’s agreed business logic.
Field teams and devices
Workflows with limited connectivity that need local signature checks. Application behaviour and subsequent synchronisation are defined during the pilot.
Developers and integrators
A foundation for adding verification to an existing product. Record issuance, signature verification and rule enforcement have separate, clear boundaries.
From a digital record to a verification result
The issuing party signs the data, and the verifying party uses a trusted public key.
1. Prepare and sign
We agree the record fields and the party responsible for issuance. The issuing system signs the data with its key.
2. Deliver the token
The user receives the token through the chosen medium: a link, QR code or file. Delivery is selected to suit the workflow.
3. Verify the signature
The web verifier accepts JWS and JSON with Ed25519. It displays the verification result, key source, identifier and available token fields.
4. Apply the rules
The product separately defines permitted actions, validity, revocation and restrictions. Current shared counters and statuses need an appropriate online layer.
What we scope for your project
Implementation starts with a testable scenario. Features, integrations, hosting and responsibilities are recorded in the scope of work.
Scenario and data
The record’s purpose, participants, trusted keys, statuses and criteria for a successful check.
Verification interface
The user journey, brand styling, clear results and actions to take after an error.
Integrations and rules
Connections to your issuing and record-management systems, token usage conditions and required online checks.
Operations and handover
The environment, key management, logging, documentation and an agreed support scope.
From an introduction to implementation
We validate product value and technical compatibility step by step.
Demonstration
We show the web verifier and discuss your team’s task.
Pilot
We select one scenario, test data, participants and acceptance criteria.
Integration
We configure the agreed interfaces, rules and system connections.
Launch
We validate working scenarios, hand over documentation and define ongoing support.
Questions before implementation
What does verification establish?
Data integrity and the signature’s match to the selected public key. Trust in the issuer and the connection between a record and a particular physical item are established through the implementation process.
How do RRID and QR codes relate?
A QR code carries information. RRID adds digital-signature verification to the data; a QR code can be one way of carrying the token.
Can it work without internet access?
Signatures can be checked locally when the application has the token, a trusted key and a verification implementation. Current revocations, shared counters and other network rules require a separate mechanism.
Can verification be integrated into our product?
The integration scenario is selected for your architecture. During the pilot, we agree the data format, issuance, verification interface, keys and usage rules.
How much does implementation cost?
After discussing the task, we define the pilot, integrations, infrastructure and support. This forms the basis of the scope of work and cost estimate.
Let’s find where RRID can help your product
Tell us what data needs checking, who issues the records and who uses them. We will show a demonstration and propose a clear first implementation scenario.