How to work with Idin in Seated Ticketing

What is iDIN

iDIN is a service provided by banks that allows consumers to:

• Identify
• Login
• Confirm age
• Sign

To set up iDIN, please contact your CSM.

Settings Seated

Verification only needs to be set in the sales plan. This also allows you to play with it, e.g. for Kids ticket you don't activate it in the sales plan and for Adult you do.

Online shop

In case verification is activated in the sales plan and you log into the shop you will immediately see that ‘tickets are not available’. You can consider to add this as additional text on the top in the shop. Unless certain ticket types do not require verification, in which case only these tickets are immediately visible and available. In any case, it is important to set ‘before entering the shop’ as a login policy.

You will have to log in first and then go to the My Account - Details. If the blue iDIN bar on top is not yet shown, adjust a field and click on save. Then you can start verification.

To succeed the verification correctly, you must set the following mandatory fields in the online shop:

·       Surname

·       Email

·       Phone number

·       Gender

·       Address details

In the next screen, some more information is shown and you can make the choice of bank. This text is not customisable and is displayed in each organisation. After selecting the bank, confirmation of your identification starts.

Once successfully completed you will return to the My Account where you will see a successful notification.

If you want to make changes again, you will first receive the message below and then restart the process. Please note: even when making a change in the backend, the person in the online shop will have to restart his verification.

Backend Seated

The sales plans only apply to the online shop, you can always issue tickets in the backend without verification. If you want to manually verify in the backend, you always do this at relation level, not at order level. Do this using the 3 dots and you will get a verification question.

Once verified, this will be immediately visible at the top as soon as you open the relationship. In the activity logs, you can retrieve data on when this took place. Use the filter and search for verification.

With this filter, you can also search for failed verifications and the reason why. This way, you can easily inform the relation why the verification failed.

You can also find here whether the verification took place in the backend (then it says type dashboard) or in the online shop (then it says type iDIN).

Via Relations (Bezoekers) in the left menu, you can download a report of everything. In the AH and AI columns you can find when someone was verified and whether this is via backend (dashboard) or online (IDIN).