> 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/digital-receipts/intergrating.md).

# Intergrating

You may need to perform additional integration work to support Digital Receipts. Depending on your payment processor or CRM, we may need extra information to return data to cardholders and their banks.

During your initial conversations with our team, we'll evaluate which of three paths applies to your setup:

1. **No additional work needed:** We can gather enough data from your payment processor, CRM, or eCommerce platform. No work required from your technical team.
2. **Partial order enrichment:** We can pull most of the data from your existing integrations, but some additional enrichment is needed from your side.
3. **Complete order data:** Most of the data we need lives outside of our reach. Your systems need to pass complete order data to ours.

{% hint style="info" %}
Both partial enrichment and complete order data flows are powered by our [Orders API](/developer/api-documentation/orders.md). Depending on your use case, integration method, and available data, we'll tell you exactly what fields you need to provide.
{% endhint %}

### How partial order enrichment works

{% stepper %}
{% step %}
**We connect to your systems**

We integrate with your payment processor, CRM, or eCommerce platform.
{% endstep %}

{% step %}
**Order data is imported**

As much order data as possible is pulled into our systems automatically.
{% endstep %}

{% step %}
**You enrich remaining data**

You make an API request to enrich existing order IDs with any data we couldn't pull ourselves.
{% endstep %}
{% endstepper %}


---

# 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/digital-receipts/intergrating.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.