> 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/txalerts-dispute-alerts/overview.md).
# Overview
PayShield is focused on payment dispute resolution & chargeback prevention. The objective of the system is to accelerate dispute resolution and significantly reduce chargebacks by notifying merchants of disputes that have been raised by card programs (Visa / Mastercard), and allowing the merchants to respond to and mitigate the disputes before they become chargebacks. \
\
There are several options available for merchants on how to handle the alert:
1. Implementing tight integration into the merchants payment system, which will empower merchants to respond more efficiently and effectively to alerts raised by card programs (Visa / Mastercard) within the mandated timeframes.
2. Responding to alerts through the PayShield Dashboard and managing them directly from there.
3. Using PayShield's Dispute Intelligence to automatically resolve the alerts with custom rules around the volume, amount, and types of dispute to handle automatically, and the rest to notify the merchant about.
4. Receive the alert notifications via email.
---
# 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/txalerts-dispute-alerts/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.
