Skip to main content

Qualified Registered Mail Service

In addition to traditional registered mail which doesn't require an acknowledgment of receipt, e-Box now supports a new type of registered mail: qualified registered mail.

Attention that this integration is reserved for qualified electronic registered mail service (QeRDS) providers, for services that have been accredited by the FPS Economy.

The integration is divided into 2 phases:

  • Phase 1: qualified registered mail notification: enterprises will receive the notifications of qualified registered mail in their e-Box Enterprise. They have to click on the link in the detailed page of the notification to redirect to the message content on the QeRDS platform.
  • Phase 2: qualified registered mail: enterprises will be able to consult the content of qualified registered mail directly in thier e-Box Enterprise. We've currently finished the implementation of the phase 1.

Integration procedure for the phase 1​

Onboarding DocSender​

First of all, an onboarding DocSender should be done in order to have an OAuth client ID and configurations of senderEnterpriseNumber & senderApplicationId & messageTypeId that are needed during the publication e-Box.

The publication is not limited to G2B (Government to Business) registered mail, but any x2B (B2B, G2B, C2B, etc.) qualified registered delivery is allowed.

Here are the references of the law e-Box and the Royal Decree that form the legal basis for this new type of integration:

In order to redirect the user e-Box to the platform of qualified electronic registered mail service (QeRDS) (where they can consult the content of the registered mail), the URL of QeRDS platform and the logo of the platform should also be provided, so that e-Box team can give back the messageActionId that should be used during the publication. If needed, it's possible to configure one URL/Logo by language (FR/NL/DE).

Implementation of the message parameter​

A parameter URLQeRDS/registeredMail/fromEbox?messageId=xxx&originalMessageId=xxx&language=xx will be used at e-Box's side to redirect enterprise directly to the page of the message on the QeRDS platform. Thus, Implementation of this parameter is also necessary at the QeRDS's side.

How to publish a qualified registered mail notification?​

The endpoint POST /ebox/messages from the Message Registry Service should be used. In the json file of the publication, the flag "registeredMailType": "qualifiedRegisteredMailNotification" and the messageActionId communicated by the e-Box team should be used in order to publish a qualified registered mail notification. A body should be added to explain to user e-Box that a new qualified registered mail has arrived and he should click on the bouton to read the message on the QeRDS platform. No attachment should be added to the json file.

Minimun publication example of qualified registered mail notification​

messageToPublish: This part contains the meta information of the message. Example:

messageToPublish: {
    "recipient": {
      "eboxType": "enterprise",
      "enterpriseNumber": "0123456789"
    },
    "sender": {
      "eboxType": "enterprise",
      "enterpriseNumber": "0123456789"
    },
    "subject": {
      "fr": "Notification de recommandé qualifié"
    },
    "senderApplicationId": "my-QeRDS-platform.be",
    "messageTypeId": "notification-QeRDS-to-ebox",
   "bodyContent": {
    "fr": "Vous avez reçu un nouveau recommandé avec avis de réception sur [nom du QeRDS plateforme], veulliez cliquer sur le bouton ci-dessus pour aller sur le site d'[nom du QeRDS plateforme] et voir le contenu du recommandé."
  },
   "registeredMailType": "qualifiedRegisteredMailNotification",
  "messageActions": [
    {
      "messageActionId": "2000"
    }
  ],
  "isBodyMainContent": true
}

Proof of consultation​

During the phase 1, since the qualified registered mail will be consulted on the QeRDS platform, it's the sender's responsability to generate the proof of consultation when the message has been read.

During the phase 2, since the qualified registered mail will directly be read on e-Box Enterprise, the proof of consultation will be sent automatically to the e-Box of the sender when the message has been read.

How is the qualified registered mail presented in e-Box Enterprise ?​

Phase 1: qualified registered mail notification​

In phase 1, the qualified registered mail notification is labeled Recommandé/Aangetekend bericht in the e-Box Enterprise's interface. When an enterprise filters the messages by Recommandé/Aangetekend bericht, the results will include the registered mail AND the notification of qualified registered mail.

A notification will be sent to e-Box when an enterprise receives qualified registered mails. The QeRDS provider itself will appear as the sender of the notification. Note that the enterprise must visit the QeRDS platform to consult the content of the message. After the consultation on the platform, a proof of consultation will be generated on the platform for the sender.

Phase 2: qualified registered mail​

In Phase 2, the qualified registered mail will be labeled Recommandé Qualifié/Aangetekend Verzekerd. There will be a specific filter for this type of messages in e-Box Enterprise.

The content of the qualified registered mail will be sent directly to e-Box, and the (actual) original sender of the registered mail will appear as the sender of the message.The enterprise can then consult the message directly in their e-Box Enterprise. However, the enterprise must give consent to receive the qualified registered mail. The right to consult will also be limited. Details regarding consent and the right to consult will be published later on this page.

Attention that the phase 2 is not yet supported at the moment.