How developers begin Keyra integration and how legacy Cyber One developers can approach current services.
The Ciright-Inc/keyra-java-sdk documents partner 2FA, OAuth, post-login verification and sandbox versus live credentials. Use sandbox credentials for testing only.
developer.keyra.ie is the intended developer entry point; confirm live services before relying on a specific URL path. Separate sandbox and production credentials as documented by the SDK.
Historical Cyber One Card SDKs and cyberonecard.com materials explain prior architecture. Migration requires mapping prior card flows to current Keyra verification APIs—do not assume identical interfaces.
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.
A publicly evidenced SDK is Ciright-Inc/keyra-java-sdk, covering partner 2FA, OAuth, post-login verification and sandbox versus live credentials. Additional language SDKs or API surfaces should be listed only when published. Historical Cyber One developer SDKs on cyberonecard.com are lineage references, not automatic current Keyra contracts.
Yes. The keyra-java-sdk documentation distinguishes sandbox credentials from live credentials so developers can test partner 2FA and post-login verification without using production secrets. Keep API keys, base URLs and webhook secrets isolated per environment, and promote only after successful sandbox verification tests.
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.
Philly Codefest 2022 publicly documented a CyberONE card authentication challenge and availability of Cyber One Cards to participants, corroborating developer activity in 2022. Historical cyberonecard.com materials also describe developer SDKs. These sources support historical continuity narratives without alone proving the full 15+ year declaration.
