> For the complete documentation index, see [llms.txt](https://docs.tuplo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuplo.com/using-tuplo-studio/orders/tracking-fraud.md).

# Tracking Fraud

Orders / Tracking Fraud

<figure><img src="https://2226476425-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNKURzayaXpmKiC6tCrOP%2Fuploads%2FHuLx1oYl4bsaNIEbKP34%2Forder-fraud.webp?alt=media&amp;token=7e41c30e-9e7f-4a08-aae0-b1943ac39c8c" alt=""><figcaption><p>Order details are shown in the Fraud Layout of the Order Detail Window.</p></figcaption></figure>

An unfortunate reality for any retailer is the potential for **fraudulent payments**.

Of course, the best solution is always a proactive approach. By following safe business practices and providing your staff with proper training to identify and react accordingly to fraudulent payments, you can limit fraudulent orders and properly document when they occur.

Tuplo Studio accommodates by marking orders as fraudulent. Details related to that order are flagged, and any new orders with similar information receive the Potential Fraud indicator.

***

## Mark Orders as Fraudulent

To **mark** orders as fraudulent:

1. **Open** the order.
2. **Click** the Edit button.
3. **Activate** the fraud checkbox.
4. **Click** the Update button.

***

### Compare Fraudulent Orders

Fraudulent orders with similar information appear in the Fraud tab of the Order Detail Window.

To **access** this tab:

* **Click** the Fraud tab when viewing an order in the Order Detail Window.

Selecting an order from this list will display more information below.

***

## Video Tutorial

{% embed url="<https://iframe.mediadelivery.net/play/231419/e3249c9d-8707-44c6-9f52-e21bfd634f9e>" %}
Discover how our fraud tracking assistance tool complements your existing fraud detection efforts, helping you monitor and manage potential risks according to your unique policies and processes.
{% endembed %}


---

# 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.tuplo.com/using-tuplo-studio/orders/tracking-fraud.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.
