> For the complete documentation index, see [llms.txt](https://triple-plus-global.gitbook.io/tpt-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://triple-plus-global.gitbook.io/tpt-whitepaper/protocol-mechanics/for-sellers.md).

# For Sellers

{% @mermaid/diagram content="flowchart TB
subgraph Protocol\["TPT Protocol"]
direction LR
P2P\["P2P Trading"]
INV\["Invoice Marketplace"]
SCF\["Supply Chain Finance"]
TF\["Trade Finance"]
end

```
S["👔 Sellers"] -->|submit assets| Protocol
Protocol -->|yields| I["💰 Investors"]
V["✓ Verifiers"] -->|validate| Protocol
T["⚡ Traders"] <-->|trade TPT| P2P" %}
```

{% stepper %}
{% step %}

### Submit Asset

Sellers upload their trade finance asset with supporting documentation.

For Invoices:

* Invoice document
* Proof of delivery
* Debtor information

For Purchase Orders:

* PO document
* Buyer details
* Delivery timeline

For Trade Documents:

* Bill of lading
* Letter of credit
* Customs documentation
  {% endstep %}

{% step %}

### Verification

The verification process confirms:

* Asset authenticity — Not duplicated or fraudulent
* Debtor creditworthiness — Ability to pay
* Documentation completeness — Legally enforceable
* No existing encumbrances — Not already pledged elsewhere

Verification may be automated (for repeat sellers with history) or manual (for new relationships or larger amounts).
{% endstep %}

{% step %}

### Set Terms

Once verified, sellers configure their listing:

| Parameter              | Description                                             |
| ---------------------- | ------------------------------------------------------- |
| **Discount Rate**      | Percentage below face value (determines investor yield) |
| **Listing Duration**   | How long the asset remains available                    |
| **Minimum Investment** | Smallest acceptable investment (for fractional)         |
| **Currency**           | USDC, USDT, or other supported stablecoins              |
| {% endstep %}          |                                                         |

{% step %}

### Get Funded

When an investor commits capital:

* Investor funds deposited to smart contract escrow
* Seller receives funds immediately (minus protocol fee)
* Asset ownership transfers to investor
* Maturity countdown begins
  {% endstep %}

{% step %}

### Settlement

At maturity, the debtor pays the invoice amount:

| Scenario              | Outcome                                                    |
| --------------------- | ---------------------------------------------------------- |
| **Normal Settlement** | Debtor pays → Investor receives principal + yield          |
| **Early Payment**     | Debtor pays early → Investor receives prorated yield       |
| **Late Payment**      | Grace period applies → Late fees may accrue                |
| **Default**           | Collection process initiated → Recovery mechanisms engaged |
| {% endstep %}         |                                                            |
| {% endstepper %}      |                                                            |


---

# 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://triple-plus-global.gitbook.io/tpt-whitepaper/protocol-mechanics/for-sellers.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.