> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-media/duplicate-medias.md).
# Duplicate Medias
Use the Duplicate Media report to trace efficiently duplicate of credit card used during a specific period of time. This report is a powerful tool to make sure that server did not use the same credit card for several check by mistake. Take note each media type must have the field "included in report" enabled to show up on the duplicate media report. From the report filter window, select the appropriate date and time range, Revenue Centers, media and employees to be included in the report. The following is a sample of the duplicate media report:
**Media:**
Media type name.
**Folio:**
Credit card number.
NOTE: Card Numbers are masked.
**Expi.:**
Credit card expiration date.
**Invoice:**
Check number.
**Amount**
Total $ amount closed on the media.
**Tip:**
Tip amount of the credit card transaction with payment surplus set as tip entry.
**Tip fees:**
Amount held back from the tip amount to help pay for the tip credit fees.
**Server:**
Employee name from P.O.S. Control.
---
# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-media/duplicate-medias.md?ask=&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.