This guide explains how issuers review a transaction in Namirial Notify and download the available evidence files, such as affidavits, original content, attachments, and ZIP packages. The details view shows what happened during the transaction lifecycle, including timestamps, recorded events, and the configuration used for that communication.
The screenshots on this page are from an EviNotice transaction. The same layout pattern usually appears across services, but labels, metadata fields, and download actions can vary.
- You are signed in as an issuer.
- You can access the transaction from one of the issuer transaction lists.
- The transaction already exists in the service list you are reviewing.
- Find the transaction in the relevant list, such as
My EviNotices,My EviMails,My EviSMS,EviSigns, orMy EviPosts. - Open the row actions menu.
- Select Details.
- Review the transaction view.
Depending on the service and transaction state, the actions menu can also include options such as opening the transaction in a new tab, reusing it, downloading files directly, or continuing to edit it if it is still a draft.
- Open the history or events section.
- Read the recorded events in chronological order.
- Review the timestamps associated with each event.
- Use this section to confirm the sequence of processing, sending, delivery, access, response, or closure events.
Common event types can include:
- admission or initial processing
- ready, processed, or dispatched status changes
- sending or delivery events
- opening or access events
- acceptance, rejection, refusal, or signature events
- archive or closure events
The exact event list depends on the selected service and the transaction configuration.
- Open the content section.
- Review the message body, notice content, or document preview.
- Use the available download actions to export the files you need.
- Use Print content if you need a printed view of the displayed content.
- Use Reuse if you want to create a new submission based on the current transaction and that action is available for the service.
Download actions depend on the service, transaction state, attachments, and affidavit profile. Common actions include:
- Download content for the original content that was sent or presented
- Download attachments for the original attachments, if the transaction includes attachments
- Download affidavits or Download Affidavit for the affidavit PDF or affidavit set exposed by that transaction
- Download all or Download all (zip) for a ZIP package that groups the available content, attachments, and affidavits
- All affidavits or All affidavits (zip) for a ZIP package that contains only affidavit files, when the service exposes that action
- Print content for a printable version of the displayed content
- Reuse to create a new submission based on the original transaction, when that action is available
The exact label can vary between service views and legacy/current layouts. Use the action that matches the file set you need.
- Open the details section.
- Review the summary and metadata shown for the transaction.
- Confirm the identifiers, lifecycle status, dates, and certification settings.
- Review custody, retention, and access-control values when needed.
Common metadata fields can include:
- unique transaction identifier or universal locator
- type of evidence or service
- status and outcome
- sender and recipient data
- notification channels and source channel
- key dates such as creation, admission, sending, opening, signature, delivery, or closing
- custody access control and retention values
- certification level and affidavit profile or kind
- service-specific configuration such as acknowledgement, agreement, or access-control settings
- language and appearance settings
- content size, total size with attachments, and content hash
- cost center and notarial deposit information, when configured
- Open the certificates or affidavits section.
- Review the list of generated affidavit files.
- Use Visualize to open the affidavit you want to inspect.
- Use Download to save the selected affidavit PDF.
- Use All affidavits or All affidavits (zip) if you need a single ZIP with all available affidavit PDFs.
- Use Download all or Download all (zip) if you need a package that includes affidavits together with content and attachments.
Affidavit availability depends on the service, certification level, configured affidavit profile, and current lifecycle phase of the transaction. In the EviNotice example shown here, each certificate is listed separately in the Certificates tab.
Some affidavits are generated only after a specific event, such as delivery, recipient access, rejection, signature, closure, or expiry. If an expected affidavit is missing, review the transaction state and check again after the relevant lifecycle event has completed.
For the conceptual explanation of affidavits and evidence, see Evidence and affidavits.
EviNoticecan show recipient answers, refusal events, hosted-notice interaction history, content downloads, and grouped evidence downloads.EviMailusually shows the subject, message body, attachments, and delivery or interaction events such as opening, acceptance, or rejection. Attachment downloads appear when the original message included attachments.EviSMScommonly exposes compact content actions such as message-content download, all-affidavits ZIP downloads, and delivery events tied to the mobile channel.EviSigncan show signer details, outcome values such as signed or rejected, workflow dates such as sending, signature, and closing, and document or evidence package downloads.EviPostcan show printing, enveloping, postal handoff, delivery, rejection, or expiry events reported by the postal process, plus the available postal evidence package downloads.
You can review the full transaction history, inspect the recorded content and metadata, and download the available affidavits and related evidence files for your records.
Problem: You can open the transaction, but you do not see the expected affidavit action, such as Download affidavits or the per-file entries in Certificates.
Cause: The affidavit may not have been generated yet for the current lifecycle phase, or the configured affidavit profile may not produce an affidavit for that event.
Solution:
- Review the current transaction status.
- Check whether the transaction is still in progress.
- Review the configured certification level or affidavit profile if that information is available in the details view.
- Check again after the transaction reaches a later phase if the affidavit is generated only at closure or another milestone.
Problem: You can access the transaction row, but content or file downloads are blocked or unavailable.
Cause: The configured custody access control may restrict access, or the requested file may not be available for that service or transaction state.
Solution:
- Review the custody access control shown in the details section.
- Confirm that the transaction type supports the file you expect.
- Retry the action if an additional verification step is required in your environment.
- Open another available grouped-download action, such as Download all or All affidavits, if the single-file action is not exposed.
Problem: The transaction details open correctly, but the attachment list is empty or the attachment download action is not available.
Cause: The original transaction may not include attachments, or attachments may not be available for that service and configuration.
Solution:
- Review the content section to confirm whether attachments are listed.
- Check the original sending configuration if you need to confirm whether attachments were included.
- Verify whether the selected service and transaction actually support attachments in that flow.