EUDI-Wallets: A Practical Demonstration Of Use Cases [Intermediate]

So, we start from the start. So, hello again. Awesome that you're here. We talk a lot about the European Digital Identity Wallet, and at some point we need to stop talking about it, actually do it.

So, to experience how it works, to do some use cases, and to go into the nitty-gritty of using the topics. And that's something we want to do together today. I'm your guide for today. I'm Adrian, co-founder of Lissi. We are a software technology provider enabling relying parties to interact with the European Digital Identity Wallet. And I say very specifically that I will be your guide today, given that this is not a presentation. I will rather guide you, and you will have an active part, all of you.

Yes, that's also the reason why I asked some of you already to download the wallet, to facilitate that process a bit. Yes, and let's get into it directly, so we don't lose any time. For the ones of you which have not yet downloaded a wallet, I would like to ask you to download a wallet. This is a wallet which is compliant with the current proposals as part of the Architectural Reference Framework. It is aligned with the interoperability specs within the large-scale pilots of the European Wallet Consortium, as well as the potential pilot.

And we're also part of the German Wallet Project, hosted by Sprint. So, yes, we're quite involved in the topics. For the ones who have missed the QR code, last chance to scan the QR code to get a wallet, but apparently everybody has it already. Amazing.

So, what you're going to do today is, you got your first wallet. Amazing, that's a really good first step. But obviously, you want to use it now.

So, first of all, we're going to derive your identity. So, the PIT, the Person Identification Data, you can now use then that PIT for a bank account opening process. You can then derive your payment attestation in the wallet, which is basically your IBAN credential, which you then can use to go shopping to approve a payment in a shopping scenario.

And then, finally, given we spent too much money, we will apply for a loan by a bank, get a loan with a qualified electronic signature. So, you're ready for that? Nice. Okay.

So, let's get into it. And I will ask you to scan the QR code, not with the wallet, please, but with your camera. Not with the wallet, with the camera. And I will also go with the flow. And you arrive at a page where you're welcomed.

You have, again, the option to download the wallet, but you did that already. The PIT is a Person Identification Data.

And, basically, it is the derivation of your national identity provided by the government. In this case, we highly simplify this process. You would potentially use, like, your ID card in Germany, and this process will be different from member state to member state. We've notified AID solutions, which we have, according to IDAS 1 already.

However, we highly simplify this process here. So, you then can proceed with the LISI wallet. You have it already. And you ask to, that's the second step here, what you see, to personalize the demo.

So, you get, really, your real name, and you get created with your name, depending on if you give your real name or not. We're obviously in a demo environment here. But I ask you to fill out the data so that we can personalize it for you to experience. I'll give you some time here to fill out this.

Oh, I have to do that again as well. So, that was the first time that I do that with, like, 100 people simultaneously.

So, let's see how scalable that is. So, now you put in your data, and imagine, like, you're doing it on an official government website. You're just logged in with your official EID, and you want to receive your PID.

So, that's the blue button you click to get into the wallet. And in the wallet, you will then see the third screen, which is basically a demo PID provider. That will be basically the government authority issuing the identity of you into the wallet. And interesting enough, what you see here, in the issuance process, you only see the field names and not the claim values itself. But if as one, as soon as you accept it in the wallet, then you can do it. As a reminder, please scan the QR code with the, not with the wallet itself, but with the browser. And then you proceed with the LISI wallet.

Then you put in the data as there. You can continue and click the blue button, receive your PID. And from the receive the PID button, you jump into the wallet, where you can then accept the PID from the PID provider. A short hands up on the room who has the PID already in the wallet. That's not too much. That was like 30%.

So, it gives you some more time to go through the journey, because that's a very important first step. If you don't have the PID, we can't continue.

So, I did that already two or three times. So, you have multiple credentials now in the wallet.

But, yeah, the journey is there. I'll give you one more moment to go through it. Okay. Maybe a short hand, like from the guys who are participating.

Of course, a short hand up. Who's having the PID? All good? That looks like a good amount. 60? Yes. Yes. The data is predefined. Yes.

But, yeah, the birth data is predefined. But the names and stuff is according to how you put it. Yes.

So, okay. Then, what is important is if you don't want to continue, then we have to go back by ourselves.

As a user, we currently don't have a callback URL. So, the problem is the user guidance ends when we have the issuance session. We could obviously implement that, but it would be proprietary.

So, we're waiting still for the ecosystem community to provide that. So, what you have to do is you go back to your browser, whatever you're using. You might use Chrome for that. You might use some others. Safari or whatsoever. And then you can click next. Or you should maybe already in an overview where you see different kind of use cases.

So, it's a use case overview. I hope you're still with me.

So, you see the different kind of use cases. You're back in the browser. You see the use cases. And you want to start with the bank account opening.

So, you select the bank. That's basically the first screen what you see. Start the bank account opening. Once you click on continue on the blue button there, then you get forwarded to the bank website. It could also be the app. But imagine now you're at the bank. You have decided you want to open the bank account already. You continue with opening the bank account. And you get again forwarded to the wallet. You're in the wallet now. And the bank is requesting information.

And obviously, they're requesting the PIT to make an identification in order to onboard you as part of the know your customer process. You can confirm that. You have the short ID scan basically or the PIN depending on how you set up the wallet itself. I give you some more time to go through the flow. And you arrive again back at website or the app basically on your bank. And you should see the screen. Short hands up in the room. Who is still with me? That's a considerable amount. Amazing. And you can click this field in order to get your IBAN issued into the wallet.

So, it says get your payment at a station into your UD wallet. And you can click the receive IBAN into wallet.

Again, there's a deep link behind the wallet. And we jump directly again into the wallet. We're on the next page here.

So, you click the receive IBAN into wallet. You again jump directly into the wallet over. And then again, your example bank, in this case the ABC bank, is providing you with a payment at a station.

So, that's your IBAN credential. And you can accept that again. There's happening some fancy cryptography in the background.

So, it takes maybe two, three seconds. Because there's a back and forth between the different parties. And then you should have your payment at a station in the wallet.

I mean, you just opened a bank account and got your payment at a station in the wallet. That's something.

So, well done. Well done. But we obviously want to use that for something now.

So, yeah, we got some money to spend. So, again, it was an issue session. We have a callback now.

So, we have to go back to the browser. And you see two buttons. You see the go shopping and do bank transfer. But we don't want to pay our rent. It's too boring. We want to go shopping. I want to spend some money.

So, you pressed on the go shopping button. And you are now in the e-commerce shop. Imagine you're in your favorite e-commerce shop. You selected your products already. We're in the checkout process. You know it maybe.

There are, like, a lot of different payment options. You can do credit cards, PayPal, and so on. And in the future, the European Digital Identity Wallet will be one of the options you will be able to use for a checkout process. That is configured now here already.

So, basically, you can just scroll a bit down. You see we're buying an ugly pair of jeans and an even more ugly jacket. It's cheap, though. Size is wrong.

Yeah, it's rather small. So, maybe you have to give it back at some point. But for now, we still want to buy it.

So, you say pay with the European Digital Identity Wallet. Again, you get back into the wallet. Then the demo shop is requesting that information only from you. You see what kind of amount is requested. The 100 euros. You also see who is the recipient, how often it is, and obviously what do you want to pay it.

So, the funding source. In that case, it's the bank account. And you can say pay. And you get forwarded back. And you get to the screen, which is basically e-commerce shop again, which says congrats for the shopping experience. And you should always also see the personalization.

So, the name you put in the first step when you're registering, you should see that name again. Okay, a short hands up. Who's still with me? Nice. This seems like a good experience. The thing is now that we spend too much money. We're maybe a pure student. We spend 100 euros.

So, dammit, we want to go shopping again at some point. And we can't pay our rent anymore.

So, we want to go back to the bank. We go back to the browser.

Actually, we say view other use cases. And at this point, we want to go for a loan process. We get some money so we can continue shopping.

So, yes, from the list of use cases, you see we don't do the bank account opening. It's the fourth one, loan process for the qualified electronic signature. You select that. You continue. And you should see the first screen here.

So, basically, you're at either your bank. Could be also any other kind of bank for that matter. And it's a five-year loan. We're quite committed here to go shopping.

34,000 euros. So, we can buy a lot of ugly stuff. And you can also click on a document if you like to. And the document opens. That's the document we want to sign. It's the loan agreement. It's not yet signed yet. But it's a process where we can take a look and make an informed decision as a user to be completely idiotic and spend 34,000 euros on closing.

Anyways, we want to get the money. So, we continue sign with the European Digital Identity Wallet. And when you do that, then, again, the wallet opens. And you see who's requesting the information. That's the ABC bank again. They ask for your PID because as part of a qualified electronic signature, you need to be identified. And you also see the document again. And it comes up what kind of document. It's a loaner document we just saw. And it also says, hey, this is a legal binding action you're doing here.

So, be careful of what you're doing. We just heard the talk before, right? Making an informed decision is not always that easy.

So, here, certainly, we might want to be even more careful with really making sure that the user is aware that he's doing something really important here which has legal consequences. But we're still happy to do it and get some money.

So, we sign the document. You might need to import your PIN or your face ID again to make sure it's really you who's signing the process. And then we can get back to the confirmation process where it says the document is signed. You should see the confirmation and contributions. You spent quite some money but had a good experience with opening a bank account. Get a payment attestation. Go shopping. And get a loan with a qualified electronic signature in 10 minutes.

So, applause for you. You did quite well. Awesome.

So, what did we learn? We learned when it comes from the user experience, user perspective, it's super important that we guide the user through the onboarding flow. In this case, it was rather easy. We prepared the wallet in advance already. But most of the time, nobody's downloading a wallet to prepare the identity, right? It's always part of the flow and it's a major hurdle.

So, that's important to take into consideration. Also, with only the single device flow, mobile only, some people start the process from a desktop.

So, we have cross-device flows which makes QR codes and stuff more complicated. Also, we have to redirect. That's something we have to also always include. We also need to make sure that the purpose of the requests are clear enough that we get status feedbacks like with success pages we've just seen. And we also need to have consistent triggers with the buttons and so on. They should look similar and so on. And we also should minimize the clicks. That's something we'll have to improve ourselves in the demo here. But it should give you a feeling of what to take care of.

On the other side, when it comes to a relying party, we need to make sure that we use suitable credential issuance flows. There's the pre-authorized. That's the one we just did where the user is known and we have a trusted communication channel. But this might not be the case.

So, there are other flows where we have a second factor for issuance as well. Something to consider. You also need to leverage request and presentation templates.

So, you construct a use case one, have it as a template, then can just execute it. We also want to make sure that we consider the remote and proximity flows. We only did remote flows now.

However, you also have in the future go to airport, tap to ID. So, that's something which we receive via Neo4j communication. And that's something, obviously, you want to consider as a relying party as well.

Also, you want to make sure that you ensure issue and credential discovery processes. As part of a KYC process, you might need a text ID or a credential certificate of residence.

So, you need to guide also the user of where they get that. And you also want to make sure you have callback URL handling for sessions.

So, in the callback URL, you need to integrate a session ID in order that your front end and your backend system knows who's actually coming back to you and what is the state of the transaction. So, that's also super important for the user experience to personalize the flow. And then we have also the mapping. With the PID, it's rather easy. The credential data is rather well-known. But once we get credentials where there's a lot of variety with income statements, for example, you need to map that into your internal system. And you have to do the compliance stuff with registering and so on.

So, if you might ask yourself who this looks like a lot of topics to consider in addition to all the complex technical topics, which you might have a team already in your organization diving into that, then at some point you might want to work with a partner. And that's something we provide at Lissy. We're experts.

We provide a startup program to make sure that you get a good go-to-market, that you're prepared with all the necessary software, which is scalable, compliant, and so that you can have a good go-to-market strategy and accept all wallets in the future, especially in a cross-border context. So, thank you very much. If you'd like to talk about that in more detail, feel free to reach out to me.

Yeah, I'm happy to talk about that also here in the conference. Thank you very much. We have about 60 seconds. Any quick question that can be answered equally quickly? No question. Thank you very much.