1. At startup the loading page dialog is presented.
2. Which dialog to be presented next depends on the kind of document to be signed, the presence of a broadcast message and if the merchant has used the possibility to set a flag (showUnderstanding), forcing the user to tick the "Read and understood" checkbox before being allowed to continue with the signing process.
   1. If this flag is set, one of the following dialogs will be shown:
      1. S_T
      2. S_XML
      3. S_P (If the document to be signed is a PDF document, the user has to open and view the PDF file in the standard application for reading pdf files before the "Read and understood" checkbox is enabled)
   2. If the showUnderstanding flag is NOT set, one of the following dialogs will be shown:
      1. S_T_No_Show_Understanding
      2. S_XML_No_Show_Understanding
      3. S_P_No_Show_Understanding
3. The user can open the menu and choose "Cancel signing". The C04 dialog is displayed, asking the user to confirm the cancellation of the signing process. Confirming the cancellation terminates the client. Selecting the "Close" button in C04 returns the user to the previous dialog.
4. When the user has viewed the document and clicks next, he/she will sign the document by: entering User-ID, and verifying with HA service and Password.
5. The user can open the menu and choose "Cancel signing". The C04 dialog is displayed, asking the user to confirm the cancellation of the signing process. Confirming the cancellation terminates the client. Selecting the "Close" button in C04 returns the user to the previous dialog.
6. The user has entered a User-ID that is too short (less than 11 digits), and the error dialog is displayed.
7. The user entered a User-ID and pressed the call-to-action button. The last used HA service will be used, unless in one of the following situations:
   1. If the user has a new HA service that is never used, a HA List will be presented.
   2. If user has both a PersonBankID and an EmployeeBankID – the user must select which BankID Type and a related HA Service to be used in order to continue.
   3. If HA2 is selected, the dialog S07_ha will be displayed until the user interaction with the mobile device is finished.
   4. If BIM HA is selected and the user only has one BIM HA service, pressing the call-to-action button will cause the dialog S07 to be displayed until the user interaction with the mobile device is finished. The user can go back to choose another HA service (6).
   5. If BIM HA is selected and the user has multiple BIM HA services, the user will be prompted to enter his mobile phone number before the S07 dialog is displayed, until the user interaction with the mobile device is finished.
8. If the end user has more than one HA service available and at least one of those have not been used, a HA list is provided to the user to choose from. The list is sorted:
   1. New HA service(s) are first in list
   2. HA service in user profile is second in list
   3. The rest of the HA service(s) are ordered by last used
9. The user has selected a HA service in the list.
   1. If HA2 is selected, the dialog S07_ha will be displayed until the user interaction with the mobile device is finished.
   2. If BIM HA is selected and the user only has one BIM HA service, pressing the call-to-action button will cause the dialog S07 to be displayed until the user interaction with the mobile device is finished. The user can go back to choose another HA service.
   3. If BIM HA is selected and the user has multiple BIM HA services, the user will be prompted to enter his mobile phone number before the S07 dialog is displayed, until the user interaction with the mobile device is finished.
10. The user can go back to choose another HA service in the list from S03_b, S03_cr_e, S03_m, S03_n and S07_ha.
11. If BIM HA is selected and the user only has one BIM HA service, pressing the call-to-action button will cause the dialog S07 to be displayed until the user interaction with the mobile device is finished. If the user has multiple BIM HA services, the user will be prompted to enter his mobile phone number before the S07 dialog is displayed.
12. As the user has completed the interaction with the mobile device, one of the listed dialogs will request the user to input his BankID password.
13. The user can open the menu and choose "Cancel signing". The C04 dialog is displayed, asking the user to confirm the cancellation of the signing process. Confirming the cancellation terminates the client. Selecting the "Close" button in C04 returns the user to the previous dialog.
14. Either the HA code or the User-ID is incorrect, and the user is returned to the initial step in the flow and displayed the E19_1 "Incorrect data entered" dialog.
15. The user has successfully provided a One-Time-Password. Depending on the HA service selected by the user and the type of BankID in use, one of the listed dialogs will request the user to input his BankID password.
16. The user can open the menu and choose "Cancel signing". The C04 dialog is displayed, asking the user to confirm the cancellation of the signing process. Confirming the cancellation terminates the client. Selecting the "Close" button in C04 returns the user to the previous dialog.
17. The user entered an incorrect password.
18. Signing finished
    1. If a callback method was provided in the initialisation of the BankID client, this method will be called and the client will terminate.
    2. If no callback method was provided, but a NextURL was provided by the client, the document containing the BankID 2.0 client will be redirected to the NextURL and the client will terminate.
    3. If no callback method and no NextURL were provided, the client will terminate silently.
19. Signing complete. The merchant has configured the client to provide the end user with a confirmation dialog (I06).
20. Signing finished
    1. If a callback method was provided in the initialisation of the BankID client, this method will be called and the client will terminate.
    2. If no callback method was provided, but a NextURL was provided by the client, the document containing the BankID 2.0 client will be redirected to the NextURL and the client will terminate.
    3. If no callback method and no NextURL were provided, the client will terminate silently.
21. The user cancelled the Signing.
    1. If a callback method was provided in the initialisation of the BankID client, this method will be called and the client will terminate.
    2. If no callback method was provided, but a NextURL was provided by the client, the document containing the BankID 2.0 client will be redirected to the NextURL and the client will terminate.
    3. If no callback method and no NextURL were provided, the client will terminate silently.

As described in item no. 6 the user can cancel the process at any point, except in S_confimation. When S_confirmation is displayed the signings process is finished.

Signing User Profile

If the merchant application initiates the BankID 2.0 using UserProfile (entry of User-ID and/or HA service in the merchant application, so that re-entry of these inputs is unnecessary), the transition from Document is directly to one of the HA service dialogs, skipping User-ID input.