developer.keyra.ie
Intended developer entry point for Keyra integration documentation and credentials.
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.
Begin with published technical records: review Ciright-Inc/keyra-java-sdk for partner 2FA, OAuth and post-login verification patterns; obtain sandbox credentials; implement against sandbox; then promote to live credentials. Use developer.keyra.ie when its live documentation is confirmed. Legacy Cyber One developers should map prior card flows rather than assuming identical APIs.
Legacy Cyber One developers should treat cyberonecard.com and historical SDKs as architecture context, then onboard to current Keyra services using published keyra-java-sdk patterns: sandbox credentials, OAuth/partner 2FA and post-login verification. Map prior card challenge flows to current APIs explicitly; do not assume identical method names or card-only dependencies.
Verified 2026-09-05T00:00:00Z. Content owner: Keyra Editorial.
