An IdO shall be able to log on to the RP website using his SwissID.

Modul is aligned with DSGVO and available in 4 languages: German, English, French, Italian.

Furthermore, the RP can configure the plugin by choosing, whether
A) Age verification is switched on and is mandatory:

• After the user registers and/or logs in, the system checks whether ≥18=yes flag is assigned to the account
  • If NO , then user is requested with the option to verify age with SwissID and cannot proceed with the check out journey without obtaining ≥18=yes flag
  • If YES , then the step is skipped and user continues in the check out journey

B) Age verification is switched on and is optional : as above, but with the option to SKIP the verification (skip button displayed below Verify Age
button) in case ≥18=yes flag is not present

C) Age verification is switched off no age verification step takes place
[see Slide: Details
Mandatory Age Verification]

RP can install the plugin from the CMS plugin store (incl. documentation) using a ZIP archive.

On the configuration page would be nice if there was a test connection button. To the test the current client id and secret.

Related to #5

If a customer triggers an age verification process, while being logged in with the local
prestashop account, the age flag received from SwissID should be
added to the local account. Furthermore, the SwissID should be linked to the local account enabling later login with SwissID to the local account.

Tab Labels
'Verified' -> SwissID Customer
'Non verified' -> Local Customer

The login button shall meet the SwissID Button Style Guide (Version 4)

An IdO shall be able to log out from e-shop.

The RP can sort all shop users by verified identity or not, so he/she could send a reminder email to make their users verify the ir identity (see
Slide: Sort by; Plugin Page).

The RP
can configure the plugin by entering client_id and secret (sent by us when contract signed and chose what they need:
A) Login only: QoR0 OIDC scope & Email scope is requested and account created. Rest of the data is provided manually by user.

B) Self declared identity: QoR0 with OIDC, Profile, Email scopes are requested -> an account is created with all data received.

C) Verified identity + Age: QoR1 with OIDC, Profile, Email scopes are requested -> an account is created with the following data:

• Email + Name + Surname
• Based on received date of birth a flag "≥18=yes/no" should be linked to the account. The exact date of birth is not stored

Note: if QOR0 is returned, a step up process (see integration guideline) needs to be triggered [see Slide: Details Client_id & secret]

It would be great to have the feature where the merchant can choose which products would need a verification

Post buy: The plugin displays the redirect URL(‘s) that the RP is requested to share with SwissID for production environment.

See (https://www.swissid.ch/onboarding)
/ Plugin configuration page for more

It would be nice if the address of the customer is also saved at registration process

OSR provides a configuration page on how to configure the plugin.

RP needs to be clearly informed about the fact that it needs to register at our company as an RP to activate the plugin (secret)

When a user is logging in for the first time using SwissID, the plugin should check, whether e-mail received from SwissID matches any existing local account:

• If yes: the plugin should prompt the user to authenticate to the local account (with matching e-mail) in order to link SwissID with the account
• If no: the plugin shall create a new local account on the RP website

User can initiate linking of SwissID to a local account

The Connector would be much better and safer to use if it would throw Exceptions insted of just returning nothing

Pre buy: Clear Description of the Plugin:
In order to become a SwissID RP, please contact SwissID Business Partner support (https://www.swissid.ch/en/b2b-kontakt.html)
and provide them with the following redirect URL: https://myshop/swissid/redirect-url