DKR TapX — Identity, Context & Workflow Platform
DKR TapX connects verified identity, physical access and business workflows in your enterprise app. Compatible iOS and Android phones authenticate with DKR Inside devices over NFC, receive the result and site context, and trigger authorized workflows.
Compatible iOS / Android phones · No platform-wallet enrollment for NFC access
Bring telecom and enterprise identity into physical spaces →An internal innovation team at Chunghwa Telecom
01 / INNOVATION
DKR combines trusted identity, app-initiated authentication, returned site context and authorized workflows in one connected interaction.
Phone as NFC Reader
The phone sends identity-derived authentication data as an NFC reader. DKR Inside validates it and decides access, without phone-side HCE card emulation.
Use your app on compatible iOS and Android phones.Identity-Anchored Provisioning
Link verified identities to enterprise accounts and permissions. Integrate credential issuance and use into your existing app and business processes.
Control credential issuance without wallet enrollment.Bidirectional Context Exchange
The same NFC channel returns the authentication result and device site context to the app, linking the verified identity to the interaction point.
Give digital services the context to act.Policy-Driven Orchestration
The app sends the event to TapX over its network connection. Identity and site policies trigger workflows with linked execution records.
Connect access, device policies and business processes.02 / SEE IT WORK
A real demonstration: UA100 door access connected to an MDM camera policy.
60 seconds · English narration / on-screen subtitles · Integrated MDM and managed phone
The film introduces in-app NFC identity, then shows a phone interacting with a wall-mounted UA100, door access, and an MDM camera restriction. A separate verification sequence releases the policy and restores camera access. It ends with a CHT Tech Day showcase and team-reported deployment figures. This is an edited product demonstration, not a latency benchmark.
Authenticate at UA100 from the app
Apply an MDM camera restriction
Authenticate again to restore camera access
NFC → App → TapX → MDM
Business value: connect access verification and device policy in one workflow, reducing separate manual steps.
Apply camera restrictions through an integrated MDM service.
Present documents and identity-linked confirmation and signing in the same app.
Connect authorized interactions to air conditioning or other equipment.
03 / IN THE FIELD
DKR deployment scale, field applications and public demonstrations. Use of individual TapX integrations varies by project.
Team-reported DKR totals, not active-user counts or adoption of every TapX integration. Exhibition photos document public showcases.
04 / ADOPTION & TRUST
Choose an identity source, verify it, link the enterprise account and permissions, then issue the app credential.
Identity sources & integration scope
For pre-issuance checks alongside enterprise account binding and authorization. Integration scope is agreed per project.
Connect IdP / SSO systems to reuse enterprise accounts and lifecycle policies, with integration tailored to the enterprise.
Evaluate sources such as Taiwan’s Digital Identity Wallet by issuer, credential type and verification interface.
Operator foundation: Chunghwa Telecom has publicly announced SIM Swap and Device Status network APIs. Official operator announcement
DKR integration of SIM Swap / Device Status requires separate confirmation. The operator announcement is not evidence of DKR integration or certification.
Apply checks at each boundary. SIM control alone is not proof of a person or access rights. The device validates access; TapX executes authorized workflows.
DKR devices use high-security OSDP links with compatible access-control systems.
NFC data exchange uses NFC Forum and ISO/IEC 14443 communication standards.
User authentication: FIDO / WebAuthn. Telecom verification: Open Gateway APIs.
Extend telecom identity into enterprise services through app, device and systems-integration partners.
Pilot access or MDM integration. Check compatibility and measure issuance effort, policy execution time and manual steps.
App developers embed credentials; manufacturers integrate DKR Inside; system integrators connect controllers and business services.
Use pilot results to guide rollout across more sites, enterprise users and TapX workflows.
Compatible phones supporting the relevant NFC reader APIs, app enrollment and authorization, and DKR Inside-compatible devices are required. NFC access does not require platform-wallet enrollment. Retaining existing controllers and wiring requires a compatibility assessment.
Review identity binding, credential revocation, device-response validation, and event records for the deployment. Signing workflows require review of documents, consent, and identity evidence. DKR use does not automatically establish compliance or certification. Ask the team for applicable test evidence and scope.
NFC authentication and TapX cloud workflows are separate stages. Uploads and MDM or IoT execution depend on connectivity and integrated systems; offline policies must be agreed for the deployment. Site context identifies the interaction point, not proof that a person passed through a gate.
Bring your app, site, or workflow requirements. Let’s define a practical first deployment.