> For the complete documentation index, see [llms.txt](https://docs.chargebackstop.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chargebackstop.com/systematic-dispute-deflection/integrating.md).

# Integrating

Systematic Dispute Deflection builds on top of the same data set used for [Digital Receipts](https://docs.chargebackstop.com/digital-receipts), in addition to the qualifying data.

* Customer's IP address or device fingerprint
* Customer's email address

The qualifying data identifiers listed above are mandatory for deflection. If you're setting up Digital Receipts alongside this product, pay close attention to the required fields for Consumer Clarity, First Party Trust, Order Insights, and Compelling Evidence 3.0 during your integration.

{% hint style="info" %}
Both products share the same underlying data pipeline. Getting your Digital Receipts integration right means Systematic Dispute Deflection works out of the box.
{% endhint %}


---

# 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://docs.chargebackstop.com/systematic-dispute-deflection/integrating.md?ask=<question>&goal=<endgoal>
```

`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.