A certification level defines the degree of legal and technical assurance applied to a certified communication. It determines the type of electronic signature used on the affidavits, the regulatory framework that governs the process, and the jurisdiction under which the evidence is valid.
Available levels depend on your account subscription. Submitting a level your account is not provisioned for returns a 400 error.
There are three active certification families. EviSign also supports a special non-certified value:
- Standard — affidavits are certified with a simple electronic signature. Identifies who signed and guarantees the content has not been modified. May not include a qualified timestamp. Suitable for low legal-risk processes.
- Advanced — affidavits are certified with an advanced electronic signature with a qualified timestamp. Guarantees signer identity, document integrity, and the exact moment of signature. Suitable for processes requiring stronger legal assurance.
- QeRDS — Qualified Electronic Registered Delivery Service. Identifies both sender and recipient and protects the integrity and timing of the qualified delivery process. Requires a verified recipient identity before notice access. EviNotice only. See QeRDS with EviNotice for qualification and evidence. The API authentication certificate, identity-enrollment profile and evidence-signing process serve distinct purposes.
- None — EviSign only. No certification is applied, but the signature process can still be completed without certified affidavit generation.
| Code | Family | Jurisdiction |
|---|---|---|
Standard | Standard | Unqualified/default variant |
Advanced | Advanced | Unqualified/default variant |
QERDS | QeRDS | Legacy qualified value; the effective variant depends on site mapping. EviNotice only. Prefer an explicit provisioned QERDS_ES or QERDS_IT value for new integrations. |
Standard_EU | Standard | European Union |
Standard_CO | Standard | Colombia |
Standard_CR | Standard | Costa Rica |
Standard_EC | Standard | Ecuador |
Standard_MX | Standard | Mexico |
Standard_PE | Standard | Peru |
Advanced_EU | Advanced | European Union |
Advanced_CO | Advanced | Colombia |
Advanced_CR | Advanced | Costa Rica |
Advanced_EC | Advanced | Ecuador |
Advanced_MX | Advanced | Mexico |
Advanced_PE | Advanced | Peru |
QERDS_ES | QeRDS | European Union – certified by Spanish authority (eIDAS) |
QERDS_IT | QeRDS | European Union – certified by Italian authority (eIDAS) |
None | — | EviSign only; no certification applied. |
For regions not covered, the EU value is usually used, as European regulations are widely accepted.
QeRDS is only available for EviNotice. The Standard and Advanced families apply across all services, using the regional codes listed above.
| Family / value | EviNotice | EviMail | EviSMS | EviSign | EviPost |
|---|---|---|---|---|---|
| Standard | Yes | Yes | Yes | Yes | Yes |
| Advanced | Yes | Yes | Yes | Yes | Yes |
| QeRDS | Yes | No | No | No | No |
| None | No | No | No | Yes | No |
QeRDS submissions have additional requirements beyond the normal EviNotice required fields:
- For both ES and IT, the issuing account must be identity-verified with a QeRDS-eligible legal-document kind and have the identity-verification configuration for the selected qualified variant
- API submission requires client-certificate authentication as the second factor in addition to issuer credentials; see Integrate QeRDS notices
- Web submission requires the issuing account's two-factor authentication; see How to create a new EviNotice
- API calls must be sent to the Namirial Notify API host for the environment, not to the customer's site host
RecipientLegalIdRequiredmust betrueAffidavitKindsmust include bothSubmittedAdvancedandRead, or includeCompleteAdvanced; other kinds may be addedEvidenceAccessControlMethodmust bePublicfor Web and API submission; set it explicitly in API requests- When collecting recipient comments or rejection reasons, use
CommitmentChoice: RejectwithCommitmentCommentsAllowed: true; keep comments disabled when acceptance is available and do not configure acceptance reasons for QeRDS acceptance - if in-flow enrollment is allowed,
QERDSEnrollmentProfilemust match one of the site's configured QeRDS profiles - if
QERDSIdentityTenantis supplied, it must be configured for the selected QeRDS certification level
For QERDS_ES, recipient access uses same-channel PIN rules:
- email recipients require
DeliverySignMethod: EmailPinandDeliverySignFixedEmailmust matchRecipientAddress - mobile recipients require
DeliverySignMethod: MobilePinandDeliverySignFixedMobilemust matchRecipientAddress
For API requests, use identical destination values: lowercase email addresses without surrounding spaces, or mobile numbers in the same E.164 form. See the variant requirements.
For QERDS_IT, recipient access uses a cross-channel PIN rule:
- email recipients require
DeliverySignMethod: MobilePinand a validDeliverySignFixedMobile - mobile recipients require
DeliverySignMethod: EmailPinand a validDeliverySignFixedEmail RecipientLegalIdKindandRecipientLegalIdValueare required and must validate together
The REST contracts expose values by service. For EviMail, use Standard, Advanced, or a supported regional value such as Standard_EU or Advanced_EU. EviNotice also exposes qualified values such as QERDS_ES and QERDS_IT. The values enabled for a specific account depend on its subscription and configuration.
For QeRDS submissions, the recipient must have a verified identity before accessing the notice. A recipient with an existing verified identity may still need to confirm document details; a new recipient can enroll during the notice flow only when enrollment is enabled. Identification is mandatory, while a new enrollment is conditional. See QeRDS with EviNotice and Integrate QeRDS notices.
The signature profile used to certify the notice is separate from the enrollment profile used when the recipient must register in the identity verification service during the notice flow.
QeRDS enrollment profiles are configured at the site level by a platform administrator and must match one of the site's configured QERDSProfiles values. The available profiles depend on which identity providers and verification methods are enabled for your account. Contact your Namirial commercial contact or project manager to confirm the profiles active on your site or arrange a change.