The prerequisites for this phase are

  1. The contractual on boarding of the End User is evaluated positive and the End User has received approval for access to the Verification System
  2. The development at the side of the End User is finished and finalised by the execution of the Baseline testing confirmed by BeMVO

The activation of the access of the End User to the Verification System can be done in 2 ways:

  • Manual activation of the access
  • Automated activation of the access

Manual End User implementation

The End User, i.e. the different contact persons indicated to receive the access credentials in the Access request form, receive an email at the provided email address with following information elements:

  • Client ID of the user
  • User ID of the user
  • Initial password : that will be used to download the Certificate. Also used for the first connection to the system, where a password change will then be mandatory.

The End User will also receive in a separate communication through a separate channel (eg by postal mail) :

  • PKI: url where the Certificate can be downloaded 
  • TAN  : i.e. the password for the Certificate

Further details on the End User access implementation are available in the Development documentation retrieved by the IT provider of the End User. The main steps are:

  1. Connect to the PKI portal using the initial password
  2. Download the certificate using the TAN
  3. Install the certificate in the End User’s system (for webservices and GUI)
  4. Connect to the Verification System using the initial password
  5. The End User is forced to change the password
  6. The End User can now connect to the Verification System for pack code verifications

Automated End User implementation

The process for implementing the access for the End User can also be automated by the IT department or provider.

This procedure is documented in the support document ‘Enduserimplementation-automation’. The main steps in this procedure are:

  1. Submit webservice ‘G615-download certificate’ to the PKI portal with the User login, initial password and Tan
  2. In return the user’s system receives the Certificate Name, the Passphrase and the Certificate itself
  3. Install the certificate in the End User’s system (for webservices and GUI) using the Passphrase
  4. Request the user to enter a new password
  5. Submit webservice ‘G445 – Change password’ to the Verification System with the initial password and the new password
  6. The user is now ready to access the Verification System and run verifications and decommission packs

Multiple users implementation

In case the IT software provider needs to implement a large group of End Users, an alternative approach based on the automated End User implementation procedure is possible. The IT provider needs to contact the BeMVO to agree on the details of the implementation in alignment with the End Users.

End User training

The training material for the End User should contain:

  1. A set of general information documents on FMD, such as
  • FMD background information
  • What is expected from the End Users within the FMD regulation
  • What are the general procedures to be followed by the End User
  • What to do in case of a falsification alert

This information is to be provided by BeMVO

2. A specific documentation on how the FMD module/system has been developed and set up by the IT department / IT software provider

  • How has the FMD functionality been implemented in the End User system

This information is to be provided by the IT department/service