A BLE/mobile and legacy 125 kHz reader for pdk.io-controlled openings.
Product and selection guidance
Touch io combines ProdataKey mobile credentials with legacy proximity support and connects to pdk.io door controllers. It requires a PDK Cloud Node and annual subscription. Select adjustable BLE range, reader mounting, Wiegand path, credential migration and phone onboarding. Legacy 125 kHz credentials remain clone-prone and should not be the long-term security target.
- BLE mobile credential and ProdataKey App workflow
- 125 kHz legacy card/fob coexistence and migration
- Cloud Node, pdk.io controller and subscription requirement
- Adjustable read range, IP65 mounting and Wiegand wiring
- Door preparation, life safety and accessibility
- Current availability, subscription and lifecycle support
- Administrator, credential and emergency override policy
- Training, documentation and preventive maintenance
Request a site-specific review
Supported from Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
How to compare and specify this product family
For PDK Touch io Reader and Mobile Credentials, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
Questions that come up when a site moves from 125 kHz fobs to Touch io mobile credentials.
Will Touch io still read the 125 kHz fobs our staff carry?
Yes. Touch io combines ProdataKey mobile credentials with legacy proximity support, so existing 125 kHz cards and fobs keep working at the reader while phones are enrolled. Treat that as a transition rather than the finished state, because this product page is direct that 125 kHz credentials remain clone-prone and should not be the long-term security target at a controlled opening.
What else has to be in place before a Touch io reader will open a door?
A pdk.io door controller, a PDK Cloud Node and the annual subscription, since Touch io connects to pdk.io controllers instead of standing on its own. Settle who holds that subscription and whose name sits on the account before the order goes in, because account ownership is harder to unwind once the system is live and staff are already enrolled.
Can the reader cable already at the door be reused?
Sometimes, and the deciding factor is the Wiegand path: whether the existing cable carries the conductors the reader needs, and whether run length and shielding suit that wiring. Check it opening by opening during the walk instead of assuming one answer for the building, because doors in one facility can have been wired in different years by different contractors.
Is Touch io suitable for an exterior door?
Suitability depends on the exposure at that opening weighed against the listed IP65 mounting and the surface the reader lands on. Reader mounting, adjustable read range and the Wiegand path are selected together, so set the range for the standoff you intend outdoors rather than leaving it wide enough to catch a phone in a nearby vehicle. Confirm the current datasheet for an exposed location before ordering.
How does an employee get a mobile credential onto a phone?
Through the ProdataKey App, which is the onboarding workflow the design has to plan for: someone issues the credential, the employee installs the app, and the phone is enrolled before it opens anything. Fold that sequence into the new-hire routine, because a credential nobody walks the user through is a credential that sits unused while the person borrows a fob.
Do all doors have to be converted at the same time?
No. Because Touch io reads both mobile credentials and legacy proximity cards, openings can be converted in stages while one fob still works at the doors that have not changed yet. Set an end date for credential migration when the phasing is planned, so the legacy card population actually shrinks instead of living on beside the phones indefinitely.
ProdataKey owner, administrator and buyer resources
Discuss ProdataKey installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official ProdataKey touch io software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.