![]()
This is an id_token_hint attestation flow which is using a pin code. The relying party app that presented the QR code should have displayed the pin code.
You need to enter the pin code at "pinCode": "" and press continue
This is an id_token attestation issuance flow. It means that part of the issuance process, you must do an interactive login to an identity provider
in order to prove who you are. The identity provider will return an id_token which claims will be used to set the VC claims from.
In order to do the sign in, you need to use the link in the authorizationURL below. The sign in sequence will not complete due to
that a web browser do not understand the protocol vcclient://. Therefor, you need to use the debugging tools in the browser, grab an interim code
and pass that code on to this test web wallet, which will complete the signin and acquire the id_token for you.
- Right-click on this link autorizationURL and open it in an incognito/inprivate window.
- Login with your account. It will look as the login screen is stuck
- Open Console (F12) and copy code in error message \'Failed to launch\' (look for \'&code=xxxx\' and only copy the xxxx)
- Paste in the code as the code value at
"code": "" and press continue
This is a self isued attestation flow, which means you enter the claim values for your VC yourself in the wallet during issuance.
The window below have a set of claims that you can set the values for. There is no validation. When you are done, press continue to complete the issuance.
This is a Presentation attestation flow, which means you need to present a VC of a certain type, possibly from a preselected set of issuers.
If you only have one matching VC, the wallet picks it automatically, but in your case you have more than one, so you need to enter the index number of the VC you want to present to continue.
You will find the index number in View Wallet