Certified email · for people and businessesClear email evidence, from your usual mailbox
mailcerty

The planned ID Nixa identity check for registered email.

The target journey combines document or NFC checks, a live selfie, recipient signature and express acknowledgement. The ID Nixa integration is not yet enabled in MailCerty production.

  • ✓Document or NFC · planned
  • ✓Selfie and signature · planned
  • ✓Integration in preparation
MCMailCertyMAIL TRACKINGIN PREPARATION
EMAIL / RECORDID Nixa enhanced route
SubjectService agreement · review
Recipientcamille@exemple.fr
ReferenceMC-DEMO-0000
RECIPIENT JOURNEY
…Identity checkIN PREPARATION
…Liveness and signatureIN PREPARATION
…Planned · not enabledShown only when observed

Illustrative preview · all names and statuses are fictional.

ONE REFERENCE, DISTINCT FACTS✓Document or NFC · planned✓Selfie and signature · planned✓Integration in preparation

REGISTERED ELECTRONIC MAIL (LRE) WITH ID NIXA

The target journey, clearly separated from live features.

The ID Nixa connection is not active in MailCerty production yet. The page illustrates the planned document/NFC, live-selfie, signature and acknowledgement flow without claiming it can be started today.

REGISTERED EMAIL · TARGET JOURNEY

ID Nixa verifies identity before the signed acknowledgement.

The planned LRE combines an email notice, SMS one-time code, ID document or NFC check, live selfie and recipient signature. ID Nixa and MailCerty certificates remain separate but linked. This integration is not live.

  • Email, SMS and OTP

    The recipient would confirm access with a one-time code.

  • Document or NFC and selfie

    ID Nixa would verify the identity and presence of the recipient.

  • Signature and two certificates

    Both documents would remain distinct and linked by reference.

MailCertyEnhanced certificate · target preview
PDF
REFERENCE MC-DEMO-0000

Registered electronic mail

ID Nixa identity journey · not active

SMS and one-time codeTarget step; no production event claimed
Pending
ID document and live selfieID Nixa integration awaiting validation
Pending
Signed acknowledgementCertificate only after a completed journey
Pending
Target concept — integration not liveIllustration
Illustrative mockup: fictional names, times and events, with no evidentiary value.

PLANNED ID NIXA DELIVERY — VISUAL JOURNEY

A target journey, not yet enabled in production.

The planned flow combines an identity document or NFC, live selfie, recipient signature and express acknowledgement. The MailCerty production integration is not active; the certificates will remain separate and linked by reference.

01

Enhanced notice

Planned recipient instructions

02

ID Nixa control

Document or NFC and live selfie · planned

03

Finger signature

Recipient signs before express acknowledgement · planned

04

Separate certificates

MailCerty and ID Nixa documents linked by reference · planned

LRE WITH ID NIXA

An identity-verified target journey.

ID document or NFC, live selfie, OTP and signature remain a planned MailCerty–ID Nixa integration.

01

Identity document or NFC

Planned for the target journey; not currently available in MailCerty production.

02

Presence check

A live selfie is planned; MailCerty does not currently launch it.

03

Handwritten signature

The recipient signature is planned before an explicit acknowledgement.

04

Linked evidence

MailCerty and ID Nixa documents are intended to remain separate and linked by reference.

WHAT MAILCERTY RECORDS

A readable map of the available evidence.

Availability depends on the selected journey and on facts actually returned by the mail infrastructure or completed by the recipient.

FunctionRecorded factAvailability
Original message and headersLinked to the evidence referenceEvery mode
Attachment fingerprintsSHA-256 per documentEvery mode
Sending timestampObserved when MailCerty receives the messageEvery mode
Delivery-server responseRecorded when returned by the receiving infrastructureWhen available
Protected content accessSuccessful controlled access onlyProtected modes
Explicit acknowledgementVoluntary recipient confirmationAcknowledgement mode
Identity journeyPlanned ID Nixa result and separate certificateNot enabled in production
Evidence certificatePDF timeline and technical referencesEvery completed file
Integrity verificationFingerprints can be checked against the exported fileEvery completed file
Workspace trackingSearch, status, quotas and downloadsAccount workspace

FIVE EVIDENCE LEVELS

Choose the journey according to the risk.

The interface makes the difference between transport evidence, controlled access, acknowledgement and identity verification explicit.

CapabilityDiscreet proofNotified copyProtected contentAcknowledgementID Nixa delivery · planned
Recipient notified—✓✓✓Planned
Content kept behind access control——✓✓Planned
Explicit recipient action——AccessAcknowledgementPlanned
Identity check————Planned
PDF evidence file✓✓✓✓Planned

The ID Nixa MailCerty production integration is not enabled yet. This column describes the target journey only.

FROM MESSAGE TO EVIDENCE

Six understandable stages, from your mailbox to the certificate.

  1. 01
    Choose the evidence level

    Discreet proof, notice, protected content, acknowledgement or registered electronic mail (LRE).

  2. 02
    Send from your usual tool

    Use MailCerty from the workspace, Outlook, Thunderbird or an evidence address.

  3. 03
    MailCerty records the source

    Message, recipients and attachments receive one evidence reference.

  4. 04
    The recipient follows the selected journey

    No account is required to access the delivery page.

  5. 05
    Observed events build the timeline

    No opening or acknowledgement is claimed before it actually occurs.

  6. 06
    Retrieve the completed file

    Search the workspace and download the available PDF certificate.

DOCUMENT PREVIEW

What an enhanced-delivery evidence file may look like.

A two-document specimen, based on the evidence structure: MailCerty deposit/receipt certificate plus a separate ID Nixa certificate.

Not a live production certificate

The enhanced ID Nixa route is not enabled in the current MailCerty production backend. This visual is a fictitious preview only; the final issued documents may differ after the integration is activated and verified.

SPECIMEN · FICTIONAL DATA
MailCerty
PAGE 1 / 2

EMAIL EVIDENCE

Deposit certificate

Message deposited · demonstration only
Reference
MC-DEMO-0000
Sender
service@entreprise.example
Recipient
destinataire@exemple.invalid
Subject
Fictional delivery notice
Deposited at
24/09/2026 10:14 UTC · UTC
Delivery mode
Enhanced · ID Nixa (preview)
MESSAGE SHA-256 · FICTIONAL, SHORTENEDf14a 8d20 … 0b71 c932
RFC 3161 timestamp token · illustrative
SPECIMEN · FICTIONAL DATA
MailCerty
PAGE 2 / 2

RECIPIENT ACTION

Receipt and identity certificate

Explicit acknowledgement · demonstration only
Recipient
destinataire@exemple.invalid
ID Nixa check
Verified before acknowledgement · sample
Identity reference
IDN-DEMO-0000
SMS channel
Fingerprint abbreviated · fictional
Acknowledged at
24/09/2026 10:19 UTC · UTC
Signature
Recorded in the separate ID Nixa certificate
LINKED EVIDENCE · FICTIONALID NIXA PDF · f8c1 03ad … 4e20 b917
Timestamp evidence is attached separately when issued

All names, addresses, references, fingerprints and dates above are fabricated for illustration. This is not a valid evidence document. The identity document and selfie are not reproduced.

REAL-WORLD EXAMPLES

Here is what MailCerty does in each situation.

Each scenario names the sender’s action, the recipient’s journey and what the evidence file can show.

Deliver a document to a verified person

SITUATION

The planned journey links the email to an ID Nixa check and then to the recipient’s confirmation.

WHAT THE FILE SHOWS

The specimen below shows separate certificates and their linked references; it contains no identity document or selfie.

Collect named-person acknowledgement

SITUATION

After identity and liveness checks, the recipient confirms receipt and signs in the journey.

WHAT THE FILE SHOWS

The ID Nixa certificate remains separate; MailCerty links available references to the email file.

Build an registered electronic mail (LRE) file

SITUATION

The sender retrieves the original message and recipient action under one tracking reference.

WHAT THE FILE SHOWS

The file separates deposit, identity check, express acknowledgement and timestamp rather than conflating them.

CLEAR ANSWERS

Know exactly what is being evidenced.

All frequently asked questions →
Is the journey available now?+

No. The ID Nixa integration is not enabled in the MailCerty production engine; this page describes the planned journey.

How will identity data be handled?+

The final architecture and retention periods must be confirmed before activation. This page does not describe a live customer-facing process.

What will the sender receive?+

After activation and end-to-end testing, the MailCerty file is intended to link references to the separate certificates issued by each service.

MAILCERTY

Start with the evidence level your exchange requires.

The Free plan provides essential email evidence. Business and On-Premise scopes can be reviewed with our team.

View plans ↗Talk to an expert →