# Evidence and affidavits

Namirial Notify records evidence during certified communication and signature workflows so that relevant events and outcomes can be certified.

An **affidavit** is a PDF document that certifies one or more recorded evidence items. Namirial Notify electronically signs and timestamps the document, and it summarizes the relevant events and results according to the configured certification level. Users can independently validate an affidavit by using the QR code or signature certificate included in the document.

## Evidence versus affidavit

An **evidence item** is a recorded event or data point associated with a transaction, such as:

- a communication being processed
- a notification being delivered
- a recipient opening or rejecting a notice
- a signer completing a signature step
- a postal operator reporting delivery or failure


An **affidavit** is the formal PDF document generated from one or more of those recorded evidence items.

In practice:

- **evidence** is the recorded transaction data
- **affidavits** are the signed PDF documents that certify that data


## What an affidavit typically contains

Depending on the service and event type, an affidavit can include:

- identification of the evidence, such as the unique identifier, date, and service type
- issuer and recipient information
- content information, such as subject, size, attachments, or document references
- the certified events and timestamps associated with the transaction
- technical and contextual data, such as authentication method, IP address, browser, or geolocation when applicable
- validation information, including a QR code and signature certificate details


![Affidavit options example](/assets/affidavits_fields.7cb9dfbab02ebd8de0f92a9cd7b6d2d65905a1a11944953faf2d451063eeeaad.6fd6141d.png)

## Affidavit fields reference

The first page of an affidavit is structured around the following sections and fields. Not all fields appear in every affidavit — availability depends on the service, certification level, and the event being certified.

### Evidence identification

| Field | Description |
|  --- | --- |
| **Identifier** | Unique alphanumeric UUID that identifies the evidence within the platform (e.g. `b70c6811-532c-4eb3-bebc-e47d5d2d3132`). |
| **Admission date** | Date and time at which the communication was admitted for certification. |
| **Type of evidence** | The service that generated the evidence (EviNotice, EviMail, EviSMS, EviSign, or EviPost). |


### Issuer details

| Field | Description |
|  --- | --- |
| **Issuer** | The platform user or account that issued the communication. |
| **Address of sender** | The address (email, phone number, etc.) used to send the communication. |


### Recipient details

| Field | Description |
|  --- | --- |
| **Recipient** | Name or identifier of the person or organization receiving the communication. |
| **Recipient's address** | The email address, phone number, or other channel address of the recipient. |
| **With copy to (CC)** | Additional recipients who received a copy, when this feature was used. |


### Content details

| Field | Description |
|  --- | --- |
| **Subject** | Brief description of the content of the communication. |
| **Size** | Size of the message in bytes. |
| **Number of attachments** | Count of files attached to the communication. |
| **Message authentication codes** | SHA-256 cryptographic hash of the message content, used to verify integrity. |


### Actor data

Actor data is recorded for each event in the process and captures contextual information about who triggered it and from where.

| Field | Description |
|  --- | --- |
| **Authentication method** | How the actor authenticated to the platform (e.g. username and password, PIN). |
| **Actor identifier** | Identity of the actor — for issuers, typically their email address. |
| **IP address** | IP address of the actor at the time of the event. |
| **Geolocation** | Coordinates derived from the IP address or browser geolocation, when available. |
| **Operating system** | Operating system details of the actor's device. |
| **Browser ID** | Browser name and version used by the actor. |
| **Browser language** | Language setting of the actor's browser. |
| **Browser user agent** | Full user-agent string of the actor's browser. |


### Cryptographic and verification elements

| Field | Description |
|  --- | --- |
| **QR code** | A QR code or data matrix printed on the affidavit. Scanning it gives access to the platform URL where the evidence can be verified. This allows the affidavit to retain its legal guarantee even when printed on paper. |
| **Public key of the signing certificate** | The public key of the X.509v3 certificate used to sign the affidavit, included so the signature can be independently verified. |
| **Universal locator** | A unique URL-based identifier generated following IETF RFC 4122 / ISO/IEC 9834-8. It allows issuer and recipient to access the evidence from the internet and appears on every page of the affidavit. |


### Attachment and content pages

If the communication included attachments, a dedicated page follows the first page with details and the cryptographic summary (SHA-256 hash) of each attached file.

Subsequent pages contain the content of the certified event — for example, the body of the certified email or the text of the certified notice.

## How affidavits are generated

Namirial Notify generates affidavits from specific events recorded during the transaction lifecycle.

Depending on the service, certification level, and selected affidavit options:

- a process can generate **multiple affidavits**, each linked to a relevant event
- a process can generate a **summary affidavit** when tracking ends
- some affidavit kinds are created only when a specific event occurs, such as opening, acceptance, rejection, or signature completion


In general:

- **advanced certification** can generate separate affidavits for multiple events
- **standard certification** can generate a summary affidavit at the end of the process


Namirial Notify typically generates a summary or closure affidavit when the transaction reaches its final state.

## How evidence and affidavits differ by service

### EviNotice

EviNotice records evidence for notification delivery and for recipient actions on the hosted notice.

Typical affidavit-triggering events can include:

- admission and content certification
- notification sending and delivery
- recipient access to the notice
- opening of the hosted content
- acceptance or rejection
- refusal without opening
- attachment download (an individual attachment or a ZIP containing attachments)
- process closure or summary generation


### EviMail

EviMail records evidence for certified email delivery and, when configured, recipient interaction with the message.

Typical affidavit-triggering events can include:

- admission and content certification
- transmission result
- delivery result
- message opening
- acceptance or rejection
- closure or summary generation


### EviSMS

EviSMS records evidence for certified SMS or RCS delivery.

Typical affidavit-triggering events can include:

- admission and content certification
- transmission result
- delivery result
- message opening, where supported by channel and configuration
- closure or summary generation


EviSMS does not generally use the same acceptance or rejection workflow as EviNotice or EviMail.

### EviSign

EviSign records evidence for the signature workflow rather than for message delivery alone.

Typical affidavit-triggering events can include:

- admission and content certification
- delivery of the signature request
- signer acceptance or rejection
- signature completion
- signed main document or attachments
- final notification after signing
- summary generation at the end of the workflow


### EviPost

EviPost records evidence for physical postal delivery.

Typical affidavit-triggering events can include:

- content submission
- postal processing
- printing and dispatch steps
- delivery
- delivery failure
- recipient rejection, where reported
- final outcome reported by the postal operator


## Retrieving affidavit PDFs through the API

Affidavit metadata and affidavit files are retrieved separately:

1. Obtain an affidavit ID from an `AffidavitPublished` callback or from a Query
response that includes affidavit metadata.
2. Use the appropriate download endpoint to retrieve the signed PDF.


For EviMail, EviSMS, and EviPost, send one or more affidavit IDs to
`POST /AffidavitsDownload`. The endpoint returns an `application/zip` archive
containing the requested PDFs. Callbacks and the standard Query metadata options
do not embed PDF content. The v1 Query contracts retain deprecated blob options
that can return a Base64 PDF for one result, but `/AffidavitsDownload` is the
recommended flow for new integrations. See
[Shared download APIs](/fr/products/namirialnotify/apis/downloads-api#download-affidavit-pdfs-by-id)
for an executable request and the error contract.

EviNotice provides dedicated endpoints: download all affidavits for a notice
with `GET /v2/EviNotice/{Id}/Affidavits`, or download one affidavit PDF with
`GET /v2/EviNotice/Affidavits/{Id}`. See the
[EviNotice API](/fr/products/namirialnotify/apis/evinotice-api#download-all-affidavits).

Do not use `/AttachmentDownload` for affidavit PDFs. That shared endpoint
returns attachment metadata and Base64-encoded attachment content.

## Common affidavit kinds by service

The available affidavit kinds depend on the service and configuration. Digital services generally expose defined affidavit kinds, while EviPost is more closely tied to postal workflow outcomes.

### EviNotice

- `Submitted` — admission of the message for certification
- `SubmittedAdvanced` — admission with graphic representation
- `TransmissionResult` — successful transmission or transmission failure of the notification
- `DeliveryResult` — successful delivery or delivery failure of the notification
- `Received` — acknowledgement of receipt before the content is read
- `Read` — acknowledgement of opening or reading of the notice
- `Committed` — formal acceptance or rejection by the recipient
- `CommittedAdvanced` — acceptance or rejection with graphic representation
- `Refused` — formal refusal without viewing the message (refusal without opening)
- `Closed` — end of tracking for the notification
- `ClosedAdvanced` — end of tracking with graphic representation
- `Event` — certification of a relevant technical event
- `Complete` — summary affidavit for the dossier
- `CompleteAdvanced` — summary affidavit with graphic representation
- `OnDemand` — auxiliary affidavit requested during the process
- `Dispatched` — certification of the notification send request (email recipients only)
- `ContentDownload` — certifies that the recipient downloaded an individual attachment or a ZIP containing attachments


Failures before processing completes close the notice without generating affidavits. Later transmission or delivery failures can generate the corresponding result affidavit when requested. Although `Failed` is a value in the API contract, the notice lifecycle does not generate a separate `Failed` affidavit. See [generation conditions](/fr/products/namirialnotify/services/evinotice#when-each-affidavit-is-generated).

#### EviNotice affidavit identifiers

`AffidavitKinds` uses the request names below. `AdditionalData.AffidavitKind` in an EviNotice `AffidavitPublished` callback and `Affidavits[].Kind` in Get use the response identifier.

| Request value | Response identifier |
|  --- | --- |
| `Submitted` | `EviNotice:Submitted` |
| `SubmittedAdvanced` | `EviNotice:Submitted:Advanced` |
| `Dispatched` | `EviNotice:Dispatched:Advanced` |
| `TransmissionResult` | `EviNotice:Transmission:Result` |
| `DeliveryResult` | `EviNotice:Delivery:Result` |
| `Received` | `EviNotice:Received` |
| `Read` | `EviNotice:Read` |
| `Committed` | `EviNotice:Committed` |
| `CommittedAdvanced` | `EviNotice:Committed:Advanced` |
| `Refused` | `EviNotice:Refused` |
| `Closed` | `EviNotice:Closed` |
| `ClosedAdvanced` | `EviNotice:Closed:Advanced` |
| `Event` | `EviNotice:Event` |
| `Complete` | `EviNotice:Complete` |
| `CompleteAdvanced` | `EviNotice:Complete:Advanced` |
| `OnDemand` | `EviNotice:OnDemand` |
| `ContentDownload` | `EviNotice:Content:Download` |


`Failed` is accepted by the request contract but has no separate lifecycle-generated affidavit. Get can return `Legacy` when an old affidavit has no kind identifier. Callback `RequestId` is present for an on-demand request; `Regenerated: true` is added when the affidavit was regenerated.

#### Download certification and voucher eligibility 

`ContentDownload` is a special EviNotice affidavit kind. When it is requested, the submission must also set `EnforceTrackingUntilTimeToLive: true`; the platform rejects requests that enable only one of those two options.

For individual (non-batch) submissions under **by-submission billing**, attachment download certification (`ContentDownload`) is available in **Advanced**, **Qualified**, and **Ultimate**, but **not in Essential**. A balance consisting only of Essential vouchers cannot cover an individual submission that requests `ContentDownload`.

Each individual EviNotice uses one submission from the balance of a voucher tier that supports all requested features and has an available balance. For voucher redemption and consumption history, see [Vouchers and charges](/fr/products/namirialnotify/admin/vouchers-charges).

Voucher tier names describe billing eligibility; `Advanced_EU` is a certification-level value. The requested certification level is one of the features used to determine which voucher tiers can cover the submission.

### EviMail

- `Submitted` — admission and content certification of the certified email
- `SubmittedAdvanced` — admission and content certification with graphic representation
- `TransmissionResult` — result of sending the message to the destination server
- `DeliveryResult` — a recorded delivery result or qualifying hosted-link access. Check the event details and `DeliveredOn` before interpreting it as confirmed delivery.
- `Read` — a recorded opening or read signal
- `Committed` — formal acceptance or rejection by the recipient
- `CommittedAdvanced` — acceptance or rejection with graphic representation
- `Closed` — end of tracking for the certified email
- `ClosedAdvanced` — end of tracking with graphic representation
- `Complete` — summary affidavit for the dossier
- `CompleteAdvanced` — summary affidavit with graphic representation
- `OnDemand` — auxiliary affidavit requested during the process
- `Event` — certification of a relevant fact without a specific kind
- `Failed` — an accepted affidavit kind. A failure outcome alone does not guarantee a separate PDF. Check the final outcome and the available affidavits.


### EviSMS

- `Submitted` — admission and content certification of the certified SMS
- `SubmittedAdvanced` — admission and content certification with graphic representation
- `TransmissionResult` — recorded result of sending the message to the SMS or RCS provider, including unsuccessful sends
- `DeliveryResult` — recorded delivery feedback, which can report success or failure
- `Read` — a recorded RCS read receipt. SMS does not provide read receipts
- `Closed` — end of tracking for the certified SMS
- `ClosedAdvanced` — end of tracking with graphic representation
- `Complete` — summary affidavit for the dossier
- `CompleteAdvanced` — summary affidavit with graphic representation
- `Event` — certification of a relevant fact without a specific kind


### EviSign

For the generation stages, see [When each affidavit is generated](/fr/products/namirialnotify/services/evisign#when-each-affidavit-is-generated). If you enabled on-demand affidavits at submission and the workflow is still open, see [Request an on-demand affidavit](/fr/products/namirialnotify/apis/evisign-api#request-an-on-demand-affidavit).

- `Submitted` — admission and content certification of the signature request
- `SubmittedAdvanced` — admission and content certification with graphic representation
- `SignatureRequestResult` — result of sending the signature request to a specific signer
- `FinalNotificationResult` — result of sending the final notification after signing
- `PartyCommitted` — certification that a specific signer accepted or rejected the document
- `Attachment` — certification of an attachment being signed or rejected
- `AttachmentMasked` — masked affidavit for an eligible attachment at signed or rejected closure
- `Main` — certification of the main document being signed or rejected
- `OnDemand` — auxiliary affidavit requested during the process
- `Summary` — summary affidavit with recorded events, when enabled during normal finalization
- `Event` — certification of a relevant fact that does not map to a standard kind
- `Failed` — processing failure that ends the workflow
- `SignatureRequestDispatched` — certification of the issuance content for the signature request
- `FinalNotificationDispatched` — certification of the issuance content for the final notification


### EviPost

EviPost affidavit generation is based on postal workflow events. If you already configured an advanced content profile and enabled on-demand affidavits at Submit, you can also [request an affidavit for an open Letter or LetterLite](/fr/products/namirialnotify/apis/evipost-api#request-an-on-demand-affidavit), subject to the per-communication limit.

Typical EviPost affidavits can certify:

- content submission
- postal processing
- printing and dispatch
- delivery
- delivery failure
- recipient rejection, where reported
- final outcome reported by the postal operator


## How to read the dossier for a transaction

When reviewing a transaction and its affidavits:

1. Identify which service was used: **EviNotice**, **EviMail**, **EviSMS**, **EviSign**, or **EviPost**.
2. Review the transaction history to see which events were recorded.
3. Check which affidavits were generated for those events.
4. Open the affidavit PDF to confirm the certified event, timestamp, participants, and supporting data.
5. Use the transaction outcome together with the affidavit set to understand the full result.


## Validating an affidavit

Affidavits can be independently validated in two ways.

### Via QR code

Every affidavit includes a QR code on its first page. Scanning the code with any QR reader opens the platform URL where the evidence can be reviewed online. This method works even with a printed copy of the affidavit and does not require any software installation.

### Via PDF digital signature in Adobe Reader

Affidavits are digitally signed PDFs. Adobe Reader (version 9 or higher) can be used to verify the electronic signature:

1. Open the affidavit PDF in Adobe Reader.
2. A banner at the top of the document indicates whether the document is digitally signed.
3. Open the **Signature Panel** (click the signature icon or use the View menu).
4. Select the signature entry to view its properties.
5. Click **Certificate Details** to inspect the signing certificate — you can confirm the issuing certification authority (CA), the certificate validity period, and the key usage.


### Common issues

#### Signature shows as unknown or unverified

Adobe Reader ships with a set of trusted root certificates from Adobe's Trusted Certificate List (AATL). European certification authorities (CAs) used by Namirial Notify may not be included in this list by default, which can cause the signature to appear as unknown.

To resolve this, you can:

- **Add the CA via Adobe Trusted Identity Manager** — open the Signature Panel, right-click the signature, and select **Show signature properties**. From there, navigate to the root certificate and use **Add to Trusted Identities**, marking it as a trusted root for certified documents. See [Adobe: Managing trusted identities](https://helpx.adobe.com/acrobat/using/trusted-identities.html) for detailed steps.
- **Add the CA via the operating system certificate store** — install the root certificate of the signing CA into your OS certificate store (Windows Certificate Store or macOS Keychain), then configure Adobe Reader to validate signatures using the operating system's certificates via **Edit > Preferences > Security > Digital Signatures > Advanced Preferences > Windows Integration**.


#### Timestamp cannot be verified

A similar issue can occur with the qualified timestamp included in advanced-certification affidavits. If Adobe Reader does not trust the root certificate of the Time Stamping Authority (TSA), it displays:

> *Signature is timestamped but the timestamp could not be verified.*


The resolution is the same as for the signature: add the TSA root certificate to Adobe's trusted identities or to the OS certificate store and re-validate.

## Related concepts

- [The platform and the products](/fr/products/namirialnotify/user-guides/platform-products)
- [States and outcomes](/fr/products/namirialnotify/user-guides/states-outcomes)
- [Archiving](/fr/products/namirialnotify/user-guides/archiving)