Identity verification
Request 01a0ab14-0c33-7175-9e4c-3ea6e3035dbaStarted on 16 Sept, 16:36By Marcus Whitaker, agent 4471
The credential did not hold
This is not an “it is not me”: it is the credential failing — expired, revoked or belonging to another holder. It can be tried again.
- Holder
- Teofilo Demo
- Customer number
- BD-77310092
- We knew at
- 16:42:46
Status
- Request createdsigned in this entity’s name
- Alert sent to their mobilethe alert went out; that their mobile rings is confirmed by nobody
- The credential did not holdtime 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.
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/4636c5a0-d1c0-497e-a397-34875babe842/request