Skip to content
Last updated

QeRDS with EviNotice

QeRDS (Qualified Electronic Registered Delivery Service) is the qualified delivery option for EviNotice. It combines hosted notice delivery with identification of the sender and recipient, protection of the transmitted content and evidence of the communication.

The recipient receives a notification containing a secure link. The content stays on Namirial Notify, where identification and the applicable access checks take place before the recipient can read it.

When to use QeRDS

Choose QeRDS when your process calls for a qualified registered delivery service and verified identities for both parties. Prepare the identification requirements before sending: having the recipient's email address or mobile number does not by itself establish their identity.

The notification channel still determines how the recipient receives the link. QeRDS adds requirements to the delivery process, including identification and the access rules for the selected variant.

Typical scenarios include:

ScenarioWhy qualified delivery may fit the process
Financial product noticesCommunicate revised terms, repayment dates or outstanding payments with a record tied to an identified customer.
Contract and policy changesDeliver changes to service terms, insurance conditions or lease arrangements and retain the communication evidence.
Legal correspondenceSend contracts, claims or pre-litigation proposals through an identified-party delivery process.
Human resources communicationsKeep a traceable record of notices about employment conditions, workplace changes or disciplinary matters.

Confirm the delivery and notification requirements of the intended procedure when selecting the service.

For other EviNotice certification options, see Certification levels.

What qualification adds

A qualified registered delivery service is provided by a qualified trust service provider. The process identifies the sender with high confidence and identifies the recipient before delivering the data. It protects transmission through an advanced electronic signature or advanced electronic seal of the provider and uses qualified timestamps for sending, receipt and applicable data changes. Any changes needed for sending or receiving the data must be clearly indicated to both parties. These are service requirements under eIDAS Article 44.

For data sent and received through a qualified service, eIDAS Article 43(2) establishes presumptions concerning integrity, the identified sender and recipient, and the recorded sending and receipt times. Retain the transaction's evidence and affidavits so the recorded events can be inspected.

Under eIDAS Article 24a(8), a qualified registered delivery service provided in one EU Member State is recognised as qualified in the other Member States. The ES/IT variant selection still determines the onboarding and recipient-access requirements for your account.

Identification and access

Identification establishes who a person is. Enrollment records a verified identity through an enabled identification process. Access authentication, such as entering a PIN, checks access to the notice using the configured contact channel.

These serve different purposes. A recipient whose verified identity is already available can avoid a new enrollment, while identification remains a requirement for the qualified notice.

Sender identification

The issuing account must be prepared for qualified delivery. Contact your Namirial commercial contact or project manager to arrange sender onboarding and confirm the QeRDS variant enabled for your account.

For the Italian variant (QERDS_IT), Namirial can verify the sender's identity in person or remotely using the onboarding contract signed with a qualified electronic signature. Provide the required identity documentation for either route. Namirial verifies the documents and, where applicable, validates the signature before activating qualified sending. See the Namirial Notify operational manual (Italian), section 8.1.1.

For qualified API submission, the integration needs a client certificate specifically issued and provisioned for this use, together with the Namirial Notify credentials. This certificate authenticates the API connection and is separate from any qualified signing certificate used during onboarding. The customer's existing company certificate cannot simply be substituted. See Integrate QeRDS notices.

Recipient identification

The recipient must have an identity that can be verified for the notice. This can come from an existing verified identity or from enrollment during the notice flow, when the issuer has enabled it.

Available identification methods depend on the selected variant and the profiles enabled for the account. Confirm the intended recipient's eligibility and the applicable method before sending.

AML ID for financial institutions

AML ID is available only for the Italian qualified variant (QERDS_IT) to financial institutions that have a specific agreement with Namirial. These conditions cover both identity registration and identity reuse through AML ID.

Confirm eligibility and the applicable setup with your Namirial commercial contact or project manager. See AML ID eligibility for the registration guidance.

Spanish and Italian variants

EviNotice exposes Spanish and Italian qualified variants. The variant affects prerequisites, the identification process and the recipient's access experience. Use the variant provisioned for your account and intended process.

VariantRecipient access requirement
Spanish variantThe PIN is sent to the same email address or mobile number used for the notification.
Italian variantThe PIN is sent through the other contact channel: a mobile PIN for an email notification, or an email PIN for a mobile notification. The issuer also supplies the recipient's legal document type and number.

For the API values and required fields, see the integration guide.

What the recipient experiences

  1. The recipient opens the secure link in the notification.
  2. Namirial Notify checks the identity required for the notice. The recipient provides or confirms document details when prompted.
  3. If a matching verified identity is available, the recipient continues through the notice's applicable access checks.
  4. If no matching identity is available and enrollment is enabled, the recipient completes the configured identification process and returns to the notice. Successful enrollment in that same session can provide direct access without another access check.
  5. If no matching identity is available and enrollment is unavailable, or an enrollment attempt does not produce the identity required for the notice, access is blocked. The recipient must contact the issuer to resolve the identity requirement.

Before accessing content, the recipient may be asked to accept the QeRDS service terms and privacy conditions. A further prompt may be unnecessary when acceptance is already recorded for the identity, including from enrollment or an earlier qualified notice, or was collected during in-person identification.

Once access is granted, the recipient can read the hosted content and attachments. Acceptance or rejection of the content is available when configured by the issuer. Service-terms acceptance, identification and the recipient's response to the message are separate steps.

For the screens and detailed steps, see How a recipient receives an EviNotice.

Example: a financial institution notifying a customer

A financial institution can send a qualified notice about a product change or repayment obligation to an identified customer. Confirm that the identity and linked contacts are available to the selected service before sending.

Customer identity available to the service?Enrollment enabled for this notice?Recipient path
YesEither; a new enrollment is unnecessaryThe customer confirms the required identity details and follows the applicable service-terms and PIN steps before reading.
NoYesThe customer completes the configured identification/enrollment process. Successful enrollment in that notice session can provide direct content access.
NoNoThe customer cannot access the qualified content until the issuer resolves the missing identity.
No (enrollment attempted; no match)YesAccess is blocked; the customer contacts the issuer to resolve the failed or mismatched identification.

The PIN follows the selected ES/IT access rules above. See How a recipient receives an EviNotice for the detailed steps.

Evidence and progress

EviNotice records events as the communication progresses. Submission acceptance, notification delivery, access to the hosted notice and reading are different events; acceptance of an API request does not mean the recipient has completed identification or read the notice.

Use the notice's recorded state, outcome and available affidavits to follow the result. See States and outcomes and Evidence and affidavits.

Get started

  1. Contact your Namirial commercial contact or project manager to confirm the qualified variant, sender onboarding and recipient identification options for your process.
  2. Prepare the recipient's contact and identity information, including both contact channels for the Italian variant.
  3. For API integration, arrange the specifically issued certificate and follow Integrate QeRDS notices.
  4. For both Web and API submission, the issuing account must be identity-verified with an eligible legal-document kind and have the identity-verification configuration for the selected qualified variant. Web submission also requires two-factor authentication. Confirm onboarding with your Namirial commercial contact or project manager, then follow How to create a new EviNotice.