> For the complete documentation index, see [llms.txt](https://docufi3d.gitbook.io/docufi3d/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docufi3d.gitbook.io/docufi3d/how-to/proof-of-delivery.md).

# Proof-of-delivery

Digital Registered Mail

### Proof of Delivery (Digital Registered Mail)

The **Proof of Delivery (POD)** feature in Docufi3d enables a secure and verifiable confirmation of document receipt — similar to a **digital registered letter**.\
It provides legally valid proof of delivery and protects both sender and recipient.

#### Process Flow

1. **Document Owner selects “POD” type**\
   When creating or uploading a document, the owner selects the type **“Proof of Delivery (POD)”**.
2. **Recipient definition**\
   The document owner enters the recipient’s valid email address.\
   After that, the **checkout process** follows (depending on pay-per-use settings).
3. **Delivery**\
   The recipient automatically receives an **email with a secure link** to the document.
4. **Receipt confirmation**\
   Upon opening the document, the recipient must **confirm receipt** before proceeding.
5. **POD Report generation**\
   Once confirmed, a **POD Report** is automatically generated.\
   The report includes:
   * Date and time of delivery
   * Recipient’s email address
   * IP address and browser information (if allowed)
   * Unique blockchain transaction ID
6. **Report attachment**\
   The POD Report is **automatically appended as the final page** of the document.
7. **Recipient signature**\
   The recipient **signs only the POD Report**, not the original document.\
   This ensures that no “blind signature” can ever be placed on an unknown or unseen contract.

***

#### Why a Report is Attached

The attached POD Report prevents **misuse or deception**.\
Since the recipient signs **only the delivery confirmation page**, not the main document, it’s impossible for anyone to trick a recipient into signing a contract they haven’t reviewed.

This design protects both parties:

* The **recipient**, by ensuring the signature only applies to the receipt confirmation.
* The **sender**, through a verifiable blockchain-based delivery record.

***

#### Technical Details

* Each POD process creates a **verifiable transaction on the Cardano blockchain**.
* Every delivery is **timestamped**, **immutable**, and **fully traceable**.
* The appended report remains a permanent part of the document for audit and verification.

***

#### Use Cases

* Digital registered letters and formal notifications
* Proof of delivery for confidential or legal documents
* Secure handover of contracts, terminations, or official notices


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docufi3d.gitbook.io/docufi3d/how-to/proof-of-delivery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.