Passkeys (FIDO2) simulator

Run a full WebAuthn ceremony on a demo phone. The risk score and recommended action use the same rules as the service.

Ceremony

Context signals

These toggles feed the risk engine. Change them and run again.

Service response

Level : LowRecommended action : Allow

Risk score0.13

Reasons

synced_passkeySynced passkey: depends on the cloud account security

API response (JSON)

{
  "verified": true,
  "user_handle": "u_8f3a2c91",
  "credential_id": "AbC123...",
  "user_verified": true,
  "backup_state": true,
  "risk": {
    "score": 0.13,
    "level": "low",
    "reasons": [
      "synced_passkey"
    ]
  },
  "recommended_action": "allow",
  "result_token": "eyJhbGciOiJFUzI1NiIsImtpZCI6...",
  "verified_at": "2026-10-21T07:42:03Z"
}

The passkey is cryptographically bound to bank-x.mg, never to sifip.net: the client stays the Relying Party, SIFIP is only the verification server.

09:41SIFIP demo

BBank X

No password needed