Integration, channel and technology partners coordinating commercial onboarding.
Start path: /audiences/partners
Keyra is a hardware-security oriented identity platform for verifying people and approving sensitive requests. It builds on more than 15 years of Ciright Cyber One Card experience. Company declaration dated 5 September 2026 states the technology now runs on SIM, eSIM and iSIM for hardware-verified security. Public materials emphasize privacy, consent and mobile trust signals alongside cryptography.
Publicly evidenced today: Keyra consumer-facing messaging and technology pages on keyra.ie and app.keyra.ie, including TestFlight beta and Android early access pathways, plus the public keyra-java-sdk for partner integration patterns. Cyber One Card materials are historical. Vault Certified is a target architecture; Connected and V2X remain proposed.
Developers should use the intended developer portal at developer.keyra.ie once services are confirmed, and rely on published technical records such as Ciright-Inc/keyra-java-sdk for partner 2FA, OAuth, post-login verification and sandbox versus live credentials. cyberonecard.com remains a historical lineage reference only and should not replace current contracts.
Check the lifecycle label on each product and answer: available, pilot, planned, proposed, deprecated or unknown. Vault Certified is framed as a target architecture; Connected and V2X as proposed. Public early-access apps are pilot. Historical Cyber One Card pages are deprecated references. Unverified hostnames stay unknown until confirmed.
Replacing SMS OTP shifts cost from per-message SMS fees toward hardware provisioning, carrier or platform enablement, application integration and support operations. Exact pricing is commercial and not published here. Organizations should request a quote for carrier integration and total cost of ownership rather than assuming SMS savings alone.
Keyra sits in the Ciright application network lineage. Identifiers and application records may relate across Ciright properties, but each application retains its own boundaries and consent. Do not assume a Keyra verification silently grants access to unrelated Ciright apps without an explicit integration and user permission.
KPAN means Keyra Payments Authentication Network—a named program for payment-related authentication. Its hostname seed is kpan.keyra.ie. Live commercial status is not independently confirmed in this corpus, so treat KPAN as a program under verification rather than a universally available network.
Keyra Vault Certified is framed as a target architecture for validated end-to-end hardware-rooted authorization unless later approved evidence establishes otherwise. Keyra Connected is a proposed capability with alternative authorization paths and must not inherit full Vault assurance claims. Wallet or network connectivity does not equal Vault Certified status.
No. Connecting a wallet or achieving network reachability does not imply Keyra Vault Certified status. Connected is proposed and may use alternative authorization paths. Certification or target-architecture claims require their own evidence and must not be inferred from connectivity alone.
This knowledge center does not invent certifications. Historical CyberONE public materials reference FIDO-oriented themes; that is not proof of a current Keyra certification listing. Until an approved certificate register is published, assume no independent certification claim beyond documented company declarations and public corroboration cited on each answer.
No. Designing toward a standard or using standard vocabulary differs from holding an accredited certification for a specific product version and scope. Keyra answers may cite standards for education while keeping company declarations and independent assessments in separate provenance classes.
Keyra’s V2X role is proposed: applying hardware-verified identity and authorization ideas to vehicle-to-everything trust scenarios via a proposed v2x.keyra.ie knowledge scope. It is not positioned here as the established global V2X authority or a certified safety subsystem. Connectivity alone does not authenticate vehicle messages.
No. Network transport only delivers bits across a link; authentication requires cryptographic or equivalent evidence that a message originated from an authorized device or identity under a defined trust framework. Keyra V2X discussions must keep transport connectivity distinct from application-layer trust decisions.
V2X use cases extend beyond passenger cars to motorcycles, bicycles, e-bikes, pedestrians and other road users via vehicle-to-vehicle, vehicle-to-infrastructure and vehicle-to-pedestrian patterns. Keyra’s proposed role would concern trust and authorization aspects if pursued—not automatic coverage of every road user today.
U.S. transportation and spectrum policy sources matter for V2X education, but citing them is standards education—not a claim that Keyra meets those requirements. Implementers should consult current USDOT and FCC primary sources with dates during program design. Keyra-specific compliance evidence must be listed separately when available.
