Build with identity verification
that just works.
Three integration paths. One verification ecosystem.
Zero customer data stored.
ShareRing provides identity verification infrastructure that businesses can integrate into their own products and workflows. Whether you are building a mobile app, a web platform, or an enterprise backend, there are multiple ways to connect to ShareRing’s verification ecosystem.
Integration Paths
ShareRing Link: QR Code and Embedded Verification
The fastest way to add identity verification to any application. ShareRing Link generates a QR code or embeddable iframe that your customers scan with the ShareRing Me app. The verified result is delivered to your system via webhook. No SDK required. Works with any tech stack.
Best for: Web applications, point-of-sale systems, customer onboarding flows, and any platform that needs verified identity without building native mobile components.
How it works:
- Design and publish a verification workflow in the ShareRing Link dashboard
- Embed the QR code or iframe in your application
- Your customer scans with ShareRing Me and approves the data request
- Verified results are delivered to your webhook endpoint in real time
Learn more about ShareRing Link
Native SDKs: Embed Verification in Your App
For businesses that want to build identity verification directly into their own mobile applications. ShareRing provides native SDKs that handle vault creation, document scanning, biometric verification, and credential storage.
SDK access is provided directly through our developer relations team. We will set up your sandbox environment, provide API keys, and walk you through integration.
Best for: Mobile-first businesses, fintech applications, and platforms that need deep integration with identity verification at the native layer.
VCT Issuer: Issue Credentials on ShareLedger
For organisations that want to issue their own verifiable credentials onto ShareLedger, ShareRing’s purpose-built identity blockchain. Universities, government agencies, healthcare providers, and other identity issuers can become authorised VCT issuers, allowing them to mint credentials directly into a user’s Vault.
Best for: Credential issuers, enterprise identity providers, and organisations building on decentralised identity infrastructure.
View ShareLedger documentation
Technical Resources
- ShareRing Technical Overview – Architecture and system design
- Digital Me Briefing – Product and capability overview
- Digital Me Technical Whitepaper – Detailed technical specification
- DID and ZKP Specifications – Decentralised identity and zero-knowledge proof standards
- ShareLedger Documentation – Blockchain architecture and node setup
- ShareRing GitHub – Open-source repositories
Security and Certification
ShareRing holds UK DIATF certification (Medium Confidence, M1C) and ISO 27001 cyber security accreditation. All identity data is encrypted and stored on the user’s device using a self-sovereign model. No customer data is held in centralised databases. Verification hashes are recorded on ShareLedger for immutable audit trails.
Read more about ShareRing’s three verification levels and the VCT architecture.
Get Started
To access API keys, sandbox environments, and integration support, get in touch with our team. We will walk you through the right integration path for your use case and get you set up.
ShareRing Link: the rest of the integration surface
The Link path above covers QR codes and embedded verification. These are the other three ways teams connect it, and the code they end up writing.
What you actually write
$ npm install @shrr/link2
{
"event_type": "workflow_run.completed",
"run_id": "3f6c1b90-0d2a-4c77-9a51-8b2e5d4a1c6f",
"status": "completed",
"timestamp": "2026-08-08T00:45:35.389Z"
}Webhooks tell you what happened. The workflow’s delivery task sends what was collected, signed with HMAC-SHA256, with OAuth outbound auth and configurable retry with exponential backoff.
