# Transaction Enrichment Data
source: https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/trans-enrich-data/index.md

## Recommended paths {#recommended-paths}

Select the path that matches your role and integration requirements.

|                                 If you are a...                                  |                           Then focus on...                           |
|----------------------------------------------------------------------------------|----------------------------------------------------------------------|
| **Enterprise merchant**, a large merchant integrating directly with Gateway APIs | Adds enriched data to transactions for reporting and reconciliation. |
| **Payment service provider**, a PSP, aggregator, or payment facilitator          | Enables and standardizes enrichment data across merchants.           |
| **Software vendor**, an ISV embedding payment flows into platforms               | Generates and maps enrichment data on behalf of merchants.           |
| **Acquirer**, a bank or acquiring institution that enables merchants             | Defines enrichment requirements and consumes the data downstream.    |

## API reference {#api-reference}

To submit enrichment data as part of a transaction, use the [Transaction](https://mtf.gateway.mastercard.com/api/documentation/apiDocumentation/nvp/version/100/operation/Transaction%3a%20%20Authorize.html?locale=en_US) API.  

To retrieve enrichment data associated with a transaction, use the [Retrieve Transaction](https://mtf.gateway.mastercard.com/api/documentation/apiDocumentation/nvp/version/100/operation/Transaction%3a%20%20Retrieve%20Transaction.html?locale=en_US) operation.  

To retrieve order‑level enrichment data, use the [Retrieve Order](https://mtf.gateway.mastercard.com/api/documentation/apiDocumentation/nvp/version/100/operation/Transaction%3a%20%20Retrieve%20Order.html?locale=en_US) operation.

For a complete list of supported APIs, see [API Reference](https://developer.mastercard.com/mastercard-gateway/documentation/api-reference/index.md).

## Versions {#versions}

These versions apply to Transaction Enrichment Data.

|       If you need...       |                                                                 Then...                                                                  |
|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
| **To integrate to an API** | Transaction enrichment data is supported across applicable Mastercard Gateway API versions, subject to merchant and acquirer enablement. |

## FAQs {#faqs}

These questions address common topics about Transaction Enrichment Data.
Transaction enrichment data is additional information attached to a payment transaction to provide more context about the payer, the purchase, or the merchant. Examples include customer internet data, order‑level and line‑item details, industry‑specific data such as airline or healthcare information, and merchant or acquirer custom data. Using transaction enrichment data helps to:

* Improve issuer decision‑making and approval rates
* Support more accurate reporting and reconciliation
* Enhance customer statements and dispute handling
* Meet scheme or acquirer requirements for specific merchant types or industries
Transaction enrichment data is submitted as part of standard transaction requests, such as AUTHORIZE or PAY. There is no separate enrichment API or standalone endpoint, as the data is included in the transaction payload. Transaction enrichment data can be retrieved using:

* Retrieve Transaction operations
* Retrieve Order operations
* Reporting exports, including custom report columns

<br />

Availability depends on the data submitted and the capabilities enabled for your merchant profile. Supported enrichment data types and mandatory fields depend on your acquirer and merchant configuration. You should confirm supported data requirements with your payment service provider.