> For the complete documentation index, see [llms.txt](https://docs.payshield.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payshield.ai/txfind-payreveal-order-insight-ican/overview/overview.md).
# Overview
TxFind stores transaction and cart data from the merchant, making it available to Card Schemes (e.g. Visa, Mastercard) or other select providers.
Card Schemes use this data to allow customers and issuing banks to look up unique details for a transaction, helping to resolve cardholder billing confusion and disputes in near real-time.
For customers, enhanced order details are made available to them through their banks' online banking platform or phone app. If a customer chooses to contact their issuing bank, the issuer's call centre or back-office personnel will have access to the same detailed order information.
Access to comprehensive transaction information helps cardholders recognise transactions immediately and empowers issuers to help resolve confusion by validating purchases, or flag as true or first-party fraud, reducing the instance of unwarranted chargebacks.\
\
It is important that Merchants maintain a minimum of 365 days of prior orders available to maximize match rates and service benefits.
{% hint style="info" %}
#### Solution Highlights
* Eliminate unwarranted chargebacks
* Confirm buying decisions and reduce billing confusion
* Identify fraud and stop first-party / “friendly” fraud
{% endhint %}
In this documentation, `{baseUrl}` is used as a placeholder for the base domain of your environment.
Please replace `{baseUrl}` with the appropriate domain:
* **Staging/UAT**: `uat-txfind.payshield.ai`
---
# 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.payshield.ai/txfind-payreveal-order-insight-ican/overview/overview.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.
