Current Flow

Webshop checkout

User is at shop and collects the products he wants in a shopping basket. To get discount he selects "Get Student Discount"

The layout of the shop is clearly not our concern.
The get discount button however is. I would like to get a set standardized buttons that services can put on their site to kick off the validation.

The user now lands at a faily neutrally styled WAYF, currenlty provided by nordunet

The WAYF is showing information to the user. It seems this information is pulled from SAML metadata so this means we have a means of controlling it outside of the entity hosting the WAYF for us.
We need to make that information better so the user understands what is going on an why he is being send here.,
We also may want this information in multiple languages.

After authentication at the home IdP (which we again do not control at all), the user returns to the InAcademia site, at teh consent screen.

This age is showing correct information, but the presentation should be more clean and more easy to understand for the user.
The name of the service requesting the information is shown here ("niels_client"), so we need to pay attention to what the user gets represented. Setting this name is part of our registration process.
We are pointing to links for InAcademia and Terms of Service. We should I think include privacy policy link, and make sure there is something to point to.

After consenting to the attribute release, the user returns to the shop.

The layout of the shop is clearly not our concern.
We must make sure however that upon failure a clear message is provided. We already provide good errors, and we should perhaps test if the SP handles them correctly as part of the onboarding?
If the validation was successful, maybe we want a InAcademia Success logo to be displayed (Logo + smily, or logo + big fat green tick) so that users get a good feeling about using Inacademia and will be more likely to use the button on another shop