Identity verification
Request 01a068f4-04bc-795f-958e-4b794826c03bStarted on 3 Sept, 20:26By Agent at Banco Demo, S.A., agent unidentified
They are who they say they are
They have presented their credential and the verification passed. You can continue with the transaction.
- Holder
- Teofilo Demo
- Customer number
- BD-77310092
- Signed at
- 20:27:05
- We knew at
- 20:27:06
Status
- Request createdsigned in this entity’s name
- Signed from their wallettheir phone’s clock, not this console’s
- They confirmed from their wallettime at which this console knew
Show technical detail
This screen does not talk to TripleEnable: it asks this organisation’s own server every 3 seconds (GET /api/credentials/present), and that server answers from its own database. It does not query te-api either: the outcome reaches it on its own, over a signed webhook (POST /api/webhooks/te-api), which is how any line-of-business system finds out. That is checked by opening the network tab.
The request was opened in TripleEnable’s verifier, signed with this organisation’s DID. It has no verifier of its own and no verification key.
Receipt · what Banco Demo, S.A. keeps
- Confirmed
- 20:27:06 · time at which this console knew
- Request
- 01a068f4-04bc-795f-958e-4b794826c03b
- Credential required
- cliente
- Issuer required
- Banco Demo, S.A.
- Holder required
- BD-77310092
- Holder key
- BhWbU7yNGZxz56MY0RGy7qkhje-zPr-BRULNw5xC504
- Holder link
- f319048d-23e0-4039-b31c-a2b1b10550be
- Signed by the holder
- 03/09/2026, 20:27:05
- Presentation signature
- eyJhbGciOiJFUzI1NiIsInR5cCI6ImtiK2p3dCJ9.eyJpYXQiOjE3ODg0NjcyMjUsImF1ZCI6InJlZGlyZWN0X3VyaTpodHRwczovL3RlLWFwaS5pZHAudHJpcGxlZW5hYmxlLmNvbS92MS92cC8wNWM1OGFjZS05ZDkyLTQwM2YtOTJlNS01MjljZjM3MGExZDQvcmVzcG9uc2UiLCJub25jZSI6ImZjYzQ4MzgxLTU3MDktNGQ4Mi04N2ZmLWQ5OGI1NzhmNWRiYyIsInNkX2hhc2giOiJkZlREbG5QeXBJdDZMNW02N2taYmhfZXRhRkh5Ql9UT0RmQmgyT3N6aUtrIn0.b6iRrw-VgbTyxCPNwQ00plHhSXwmHnYUlzrRcidMg5qrv1330M69kEiZAu77kUp69zKZJd5PnnK9p1QIDn01AA
What they showed
- First name
- Teofilo
- Surname
- Demo
Verified against the issuer and against the holder. The signature was put there by the holder’s wallet; this receipt is what Banco Demo, S.A. files about the check.
Show technical detail
- Format
- SD-JWT VC presented over OID4VP
- Type required
- cliente
- Issuer required
- did:web:bank.demo-te.com
- Attributes disclosed
- given_name family_name
- Signature
- that of the KB-JWT, which ties this presentation to the holder’s key
- Holder public key
- {"x":"3WLZnchvionmDWgl00yYE4eGcYeoUESNWbgG4566FLo","y":"RjwNsNZfqYMJmUxgvSfozzFt48v4fNDoHXzt0QAFERc","crv":"P-256","kid":"did:key:zDnaexZUwZVtXMK9otwDnqJ58skfyueFKppxXqWKpn2EMQrEm#zDnaexZUwZVtXMK9otwDnqJ58skfyueFKppxXqWKpn2EMQrEm","kty":"EC"}
- Nonce
- fcc48381-5709-4d82-87ff-d98b578f5dbc
- Audience
- redirect_uri:https://te-api.idp.tripleenable.com/v1/vp/05c58ace-9d92-403f-92e5-529cf370a1d4/response
- SD hash
- dfTDlnPypIt6L5m67kZbh_etaFHyB_TODfBh2OsziKk
These four are what lets anybody re-check the KB-JWT without asking this organisation or TripleEnable for anything: the key that signed it, the challenge it answers, the verifier it was signed for, and the hash that ties it to this presentation and to no other.
The requestTripleEnable
- Holder
- Teofilo Demo
BD-77310092 - Credential required
- cliente
- Attributes requested
- First name, Surname
- How they were alerted
- Alert to their mobile · they were on the phone
- Issuer required
- Banco Demo, S.A.
The check is done by TripleEnable. This organisation does not have to run or hold any verifier: it asks the question and reads the answer.
Show technical detail
- Protocol
- OID4VP
- Type required
- cliente
- Attributes requested
- given_name family_name
- Issuer required
- did:web:bank.demo-te.com
- The wallet collects it at
- https://te-api.idp.tripleenable.com/v1/vp/05c58ace-9d92-403f-92e5-529cf370a1d4/request