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. The highest level. The identity of both sender and recipient is verified, the integrity of the process is guaranteed, and affidavits are generated with a qualified signature and timestamp. Requires the recipient to complete an identity verification step before accessing the notice. EviNotice only.
- 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 | Unqualified/default variant; EviNotice only |
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:
- the sender must use the QERDS-enabled EviNotice API flow with the required client-certificate and two-factor authentication configuration
- API calls must be sent to the Namirial Notify API host for the environment, not to the customer's site host
RecipientLegalIdRequiredmust betrue- 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 QERDS_IT, the issuer must also have the QERDS_IT identity-verification schema enabled. 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 current EviNotice, EviMail, EviSMS, and EviPost Swagger contracts expose bare values such as Standard, Advanced, and QERDS, plus regional variants that use an underscore separator, such as Standard_EU, Advanced_EU, QERDS_ES, and QERDS_IT. The values enabled for a specific account depend on its subscription and configuration.
For QERDS submissions, the recipient must complete an identity verification step before accessing the notice. 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 support to find out which profiles are active on your site or to request a change.