> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/api-reference/resources/visas-commercial-enhanced-data-program.md).

# Visa's Commercial Enhanced Data Program

This section helps you integrate with Xplor Pay to qualify for lower interchange rates when processing payments with Visa commercial cards.

### What is the Commercial Enhanced Data Program?

Visa’s Commercial Enhanced Data Program (CEDP) helps merchants qualify for lower interchange rates by submitting detailed transaction data when processing payments with Visa commercial cards.

Enhanced transaction data includes:

* [Sales tax amount](/api-reference/resources/visas-commercial-enhanced-data-program/submit-enhanced-transaction-data/sales-tax-amount.md)
* [Summary](/api-reference/resources/visas-commercial-enhanced-data-program/submit-enhanced-transaction-data/summary.md)
* [Line-item](/api-reference/resources/visas-commercial-enhanced-data-program/submit-enhanced-transaction-data/line-item.md)

{% hint style="info" %}
Visa’s **Product 3** interchange program is part of CEDP. It uses a scoring system based on enhanced data quality and presence. Visa evaluates data completeness and formatting to determine interchange eligibility.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xplorpay.com/api-reference/resources/visas-commercial-enhanced-data-program.md?ask=<question>&goal=<user_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.