Identity verification
Request 01a06fbe-af79-7f30-a82a-22cb3b38edd2Started on 5 Sept, 04:06By 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
- 04:11:36
Status
- Request createdsigned in this entity’s name
- 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
- Over 18
- 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
- age_over_18
- Issuer required
- did:web:bank.demo-te.com
- The wallet collects it at
- https://te-api.idp.tripleenable.com/v1/vp/c905670b-7d5f-4bd9-a26c-79d6af023958/request