Identity is the credential.

Everything else is friction.

One NFC tap verifies identity and delivers the right credential — a room key, building pass, or digital ID. No app required.

See It In Action Explore Solutions
KeyShare Puck — NFC identity verification device
FIPS 140-2
Validated crypto
No app required
Uses native wallet
Hotel Government Physical Access

Delivers Wallet keys directly — no app download, no account creation.

Reads and verifies ISO 18013-5 mobile driver's licenses and government-issued digital IDs.

FIPS 140-2 validated cryptographic module with hardware security module integration.

Integrates with existing infrastructure — PMS, Mercury panels, OSDP readers. No rip-and-replace.

Built for international deployment — supports ICAO DTC, mDL, and sovereign credential ecosystems.

Edge Wallet SDK for iOS and Android — full credential lifecycle management for partners.

KeyShare Puck delivering a credential to a phone

How It Works

Three steps. Universal.

Whether it's a hotel guest, a building employee, or a citizen at a government kiosk — the interaction is the same.

1
Tap — the person holds their phone to the KeyShare Puck. NFC initiates a secure, standards-based exchange — no app required.
2
Verify — the Puck reads the person's digital ID or wallet credential — cryptographically verified, on-device, in under a second.
3
Authorize — the right credential is delivered to their device — instantly. A room key, an access pass, a digital ID — whatever the context requires.

Built for speed and trust

KeyShare is the only NFC identity platform with a hardware root of trust for cryptographic verification — designed for massive adoption where competing solutions have stalled.

"KeyShare solves what mobile key apps couldn't — universal adoption. No downloads, no friction."
Phocuswright Innovation Summit People's Choice Award 2025

  • 4

    US patents granted — hardware root of trust architecture

  • 80%

    reduction in hotel check-in time versus traditional front desk

  • <1s

    cryptographic identity verification — on-device, offline-capable

  • 0

    apps required — uses your existing mobile wallet and digital ID

Solutions by Vertical

One platform. Every credential.

KeyShare solves identity verification and credential delivery wherever a person needs to prove who they are — and then be authorized to do something.

Hotel

Wallet key delivery, loyalty enrollment, and digital ID acceptance — with a single NFC tap. Designed for 70%+ adoption where mobile key apps have stalled.

Wallet Keys Loyalty Digital ID Brand SDK Payments Night Ops
80% check-in time reduction
70%+ designed adoption rate

For every property size — independent hotels to global portfolios.

Explore Hotel Solution

Government

Sovereign digital identity platform for national credential ecosystems. Workflow-driven, offline-first, and built on open standards.

Credential Issuance Citizen Wallet Offline-First DPI-Native ICAO DTC mDL
3 continents with programs
<1s identity verification

Built by KeyShare. Deployed by partners for national-scale ecosystems.

Explore Government Solution

Physical Access

Identity-based building access and visitor management. Eliminate per-user credential costs and verify people, not tokens. No rip-and-replace.

Building Access Visitor Mgmt Mercury OSDP v2.2 Face Match NDA Capture
$4–$17 credential tax eliminated
5s visitor check-in time

Integrates with existing Mercury panel and OSDP reader infrastructure.

Explore Physical Access Solution

Trusted Standards

Built on open standards

ISO 18013-5 Digital ID Standard
FIPS 140-2 Validated Cryptography
OSDP v2.2 Reader Communication
W3C VC Verifiable Credentials
DIF Decentralized Identity
DIDs Decentralized Identifiers
EUDI EU Digital Identity
HSM-Secured Hardware Root of Trust
& more Open by design

Frequently Asked Questions

Have questions? We have answers.

KeyShare is an identity verification and credential delivery platform. The core product — the KeyShare Puck — is a patent-protected NFC device that verifies a person's digital ID and then takes the right action: delivering a wallet room key in a hotel, provisioning a building access credential, or confirming a government-issued identity. One device, three verticals. No app required.

The person taps their phone on the Puck. The Puck reads their digital ID or wallet credential using NFC — cryptographically verified, on-device, in under a second. Then it triggers the appropriate action: a room key appears in their mobile wallet, a building access credential is provisioned, or an identity is confirmed for a government service. The entire interaction takes seconds. No app download. No account creation. No QR code scanning.

KeyShare serves three verticals: hospitality (hotel check-in, wallet keys, loyalty enrollment, digital ID acceptance), government (sovereign digital identity platforms for national credential ecosystems), and physical access control (identity-based building access and visitor management). The platform and hardware are shared across verticals — the configuration and software layer differ by use case.

No. KeyShare uses the person's existing mobile wallet and government-issued digital ID — no proprietary app, no account creation, no pre-registration required. This is the primary reason KeyShare is designed for 70%+ adoption where competing mobile key solutions have stalled below 10%.

KeyShare is built on open standards: ISO 18013-5 for mobile driver's licenses, FIPS 140-2 validated cryptography, OSDP v2.2 for reader communication, W3C Verifiable Credentials, and decentralized identity protocols (DIDs/DIF). The platform also supports ICAO Digital Travel Credentials, EU Digital Identity (EUDI), and sovereign credential ecosystems — all secured by a hardware root of trust (HSM).

Yes. KeyShare is built for international deployment with active programs across three continents. The platform supports ICAO Digital Travel Credentials (DTC), mobile driver's licenses (mDL), and sovereign credential ecosystems — enabling deployment in any country with a digital identity framework. The Puck's standards-based architecture means it works with local credential ecosystems without customization.