> For the complete documentation index, see [llms.txt](https://monke-or-refund-service.gitbook.io/monke-or-refund-service/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monke-or-refund-service.gitbook.io/monke-or-refund-service/getting-started/quickstart.md).
# What Are the Most Common Refund Methods?
🔹 **DNA / Empty Box (Did Not Arrive or Empty Package)**\
This method involves claiming that the package either never arrived or was delivered empty.\
Even though the store may see that the courier marked the item as delivered, things can still go wrong — maybe the courier gave it to the wrong person, left it at the door and it was stolen, or simply kept it themselves.\
If the order value is relatively low (usually around €200–250), many stores choose to process the refund with little resistance.
🔹 **FTID / LIT (Fake Tracking ID Delivery / Lost in Transit)**\
This method manipulates the tracking number. It's typically done with the help of a “boxer” — someone who handles the return shipment in a specific way.\
After it's done correctly, the tracking status updates to something like *"Returning to sender"* or *"Lost in transit,"* making it appear as if the item is on its way back but then vanishes.
🔹 **RTS (Return to Sender)**\
Another variation of the tracking manipulation technique. The package is marked as “returned to sender” before it even reaches the customer — but in reality, it never returns.\
It looks legitimate from the store’s perspective, which often leads to a refund being issued.
🔹 **Police Report Method**\
This one involves submitting a police report about the “incident.”\
Of course, the report is fabricated. But once support sees an official-looking document, many companies decide it’s not worth the hassle to investigate further and approve the refund with no questions asked.
I haven’t covered **all** the methods — just the most popular ones.\
These alone are enough to successfully refund **around 70% of major stores and marketplaces**.
---
# 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://monke-or-refund-service.gitbook.io/monke-or-refund-service/getting-started/quickstart.md?ask=&goal=
```
`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.