Secure identity. Verify intent.
One card. Four credential capabilities. Protection beyond sign-in.
FIDO2
Digital access
Phishing-resistant sign-in to websites, applications and online services. A credential registered to the intended service authenticates access, helping protect against fake login sites. Supports access within your organization and to participating external services.
X.509 Certificates
Employee identity
An organization-issued certificate connects a public key to a known employee or authorized user. Used today in enterprise smart-card and government PIV environments for computer and network sign-in, digital signatures, and secure email where supported.
Seed-Derived Keys
Trusted device verification
Keys derived from a protected TOTP seed generate fresh cryptographic proofs. These help the service confirm that the originally enrolled device is participating, without revealing the seed. A derived confirmation key also supports protection of specific transactions and communications.
MIFARE DESFire
Physical access
Contactless credentials for authorized doors, gates and secured facilities. The card authenticates with compatible readers; your access-control system determines where and when entry is allowed. Bring physical and digital access together on the same card.
Identity + digital access in one authentication transaction
In an integrated Chrome Roads workflow, X.509 establishes the user's organizational identity and FIDO2 authenticates access to the requested service in the same transaction.
On-Card Biometric Verification
The card's fingerprint sensor verifies the person using it. Apply biometric verification to supported credential and approval workflows according to your organization's policy.
Transaction & Communication Protection
FIDO2 subcredentials and seed-derived proofs support protection of transactions, calls, SMS and email - on the Chrome Roads Card or in a bank or other mobile app using the Chrome Roads SDK.
Tune user friction to the workflow and user population
Notify
Show expected contact, such as an upcoming call-center call. No response required.
Acknowledge
Add an OK, confirmation or other action to a notification.
Match & approve
Show the exact transaction details on the phone or card and require explicit approval.
Each workflow defines what the response confirms or authorizes.