# Data and reporting
source: https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/data-and-reporting/index.md

## Recommended paths {#recommended-paths}

Select the path that matches your role and integration requirements.

|                                 If you are a...                                  |                       For Reporting focus on...                       |           For Funding and fee management focus on...           |                    For Supplementary data focus on...                     |            For Import merchant data focus on...             |
|----------------------------------------------------------------------------------|-----------------------------------------------------------------------|----------------------------------------------------------------|---------------------------------------------------------------------------|-------------------------------------------------------------|
| **Enterprise merchant**, a large merchant integrating directly with Gateway APIs | Uses reports for transactions, settlements, refunds, and chargebacks. | Tracks funds credited and debited, along with applicable fees. | Uses order references, invoice IDs, and customer data for reconciliation. | Used for bulk setup or migration activities.                |
| **Payment service provider**, a PSP, aggregator, or payment facilitator          | Supports portfolio‑level and merchant‑level reporting.                | Reconciles merchant payouts and fees at scale.                 | Standardizes metadata across merchants.                                   | Used for bulk onboarding and merchant lifecycle management. |
| **Software vendor**, an ISV embedding payment flows into platforms               | Used indirectly for embedded dashboards and analytics.                | Displays payout and fee status to merchants.                   | Links payments to platform entities such as subscriptions or bookings.    | Automates merchant setup and configuration synchronization. |
| **Acquirer**, a bank or acquiring institution that enables merchants             | Provides oversight of settlement and compliance reporting.            | Manages settlement and funding provision.                      | Required for scheme and regulatory data elements.                         | Enables merchant registration and updates.                  |

## API reference {#api-reference}

Reporting uses the Transaction API to retrieve transaction details through the [Retrieve Transaction](https://mtf.gateway.mastercard.com/api/documentation/apiDocumentation/nvp/version/100/operation/Transaction%3a%20%20Retrieve%20Transaction.html?locale=en_US) endpoint.  

Funding and fee data uses the Transaction API through endpoints such as [Retrieve Transaction](https://mtf.gateway.mastercard.com/api/documentation/apiDocumentation/nvp/version/100/operation/Transaction%3a%20%20Retrieve%20Transaction.html?locale=en_US) and [Retrieve Order](https://mtf.gateway.mastercard.com/api/documentation/apiDocumentation/nvp/version/100/operation/Transaction%3a%20%20Retrieve%20Order.html?locale=en_US).  

Supplementary data is accessed through the [Transaction](https://mtf.gateway.mastercard.com/api/documentation/apiDocumentation/nvp/version/100/operation/Transaction:%20%20Authorize.html?locale=en_US) API.  

Import merchant data is supported through token migration using API integration or Hosted Batch Upload.

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 Data and reporting.

|       If you need...       |                                                                                                                                                                                                   Then...                                                                                                                                                                                                   |
|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **To integrate to an API** | Use Version 100 of the Mastercard Gateway API for all new integrations. For earlier versions, support is available as follows: - **Reporting** is supported for versions 14 and later. - **Funding and fee data** is supported for versions 49 and later. - **Supplementary data** support depends on the data type. - **Import merchant data** availability depends on the merchant profile configuration. |

## FAQs {#faqs}

These questions address common topics about Reporting.
Reporting allows you to download order‑level and transaction‑level data from the Mastercard Gateway for reconciliation, analysis, and operational reporting. Reports include all events associated with a transaction within a specified time period. You can retrieve reports using the following methods:

* Reporting API
* Web browser downloads
* CSV file downloads from the Merchant Administration portal

<br />

All methods return consistent transaction data. Transaction reports include:

* All transaction lifecycle events, such as PAY, AUTHORIZE, CAPTURE, and REFUND
* Any transaction updates that occur within the reporting period
* Separate entries for payer authentication and financial processing when EMV 3DS is used
No. Your merchant profile must be enabled for Reporting, and a Reporting password must be generated before you can use the Reporting API.

These questions address common topics about Funding and Fee Data.
Funding and Fee Data shows the actual movement of funds between your service provider and your bank account, including:

* Funds credited for payments and captures
* Funds debited for refunds
* Processing fees, which are always negative amounts
No. Funding and fee data is available only for:

* Transactions where the service provider supplies the data to the gateway
* Financial transactions, such as PAY, CAPTURE, and REFUND

<br />

Verification and authorization‑only transactions are typically not funded.

These questions address common topics about Supplementary Data.
Supplementary Data allows you to pass additional transaction‑related information to the gateway, including:

* Customer internet data
* Airline, cruise, healthcare, or debt‑repayment data
* Merchant, acquirer, or risk custom data
* Statement descriptor details
No. Supplementary Data is included as part of standard transaction requests. There is no standalone Supplementary Data API endpoint. Supported data types and required fields depend on your acquirer configuration. You should confirm support with your payment service provider. Supplementary data provided in a transaction:

* Is stored against the transaction in the gateway
* Can be retrieved using Retrieve Transaction, Retrieve Order, and Reporting exports

These questions address common topics about Import Merchant Data.
Import Merchant Data allows you to migrate existing payment data, such as gateway tokens or payment service provider tokens, from another provider into the Mastercard Gateway. This helps preserve transaction history and enables future payments using existing credentials. Merchant data can be imported using:

* Mastercard Gateway API with tokenization capability
* Hosted Batch Upload integration

<br />

The merchant profile must be enabled for API, Batch, and Tokenization services. Yes. PCI DSS compliance is required if you collect or handle raw card data during the migration process.