> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/sell-on-lid/refunds-and-protection.md).

# Refunds and protection

Refund windows from 0 to 90 days, what the buyer can do during one, how a dispute is decided, and how services will work.

You choose a refund window for each product, and the payment is protected until the window passes.

## How it works

1. When you create a product, pick a refund window from 0 to 90 days.
2. With 0 days, you are paid in seconds when the sale lands.
3. With a window, the payment is held until the window passes, then it releases to you automatically.
4. During the window, the buyer can **Release** the payment to you early, or **Dispute** it if something went wrong.
5. A dispute freezes the payment and a person on our team decides: the money goes to you, or back to the buyer.
6. If a refund goes through, the buyer gets the full amount back, including the sharer's commission.

Buyers see your refund policy on the product page before they pay.

## Services

Services are being built. When they open, the payment is protected until the buyer accepts your delivery. Then it releases to you.

## FAQ

<details>

<summary>Which window should I pick?</summary>

Short windows mean faster money for you. Longer windows help cautious buyers say yes.

</details>

Pick your policy at [lid.pro](https://lid.pro). That is the link if you want to sell.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lid.pro/sell-on-lid/refunds-and-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.