> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.mangopay.com/api-reference/reports/report-object/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server. # The legacy Report object ### Description The Report object is a tool that enables you to download a large amount of data in CSV format for accounting or analysis purposes. Reports are available for transactions and wallets. > **Note** > > **Note – Replaced by Reporting Service** > > The legacy Report endpoints are being replaced by Mangopay's Reporting Service, which underpins the Dashboard's report features. > > The legacy Transactions report data is available in the service's User Wallet Transactions report. An equivalent of the legacy Wallets report is planned in future. ### Attributes ### Schema (`ReportResponse`) ```yaml components: schemas: Id: type: string description: >- Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object. title: Id Tag: type: string description: >- Max. length: 255 characters Custom data that you can add to this object, such as unique identifiers in your system. To store multiple values, you can serialize them into a single string, for example a JSON object: `"{\"id_1\":AB123,\"id_2\":DE456}"`. title: Tag CreationDate: type: integer description: Unix timestamp (UTC) of the date and time the object was created. title: CreationDate ResultCode: type: string description: >- The code indicating the result of the operation. This information is mostly used to handle errors or for filtering purposes. title: ResultCode ResultMessage: type: string description: The explanation of the result code. title: ResultMessage ReportType_Reporting_Response: type: string description: >- **Returned values:** `COLLECTED_FEES`, `USER_WALLET_TRANSACTIONS`, `ECHO_INTENT`, `ECHO_INTENT_ACTION`, `ECHO_SETTLEMENT`, `ECHO_SPLIT` The type of the report. Each `ReportType` has different available `Columns` and `Filters`. Useful for all platforms: - `USER_WALLET_TRANSACTIONS` – All successful transactions crediting or debiting user wallets: pay-ins, transfers, conversions, and payouts, as well as refunds of all types and repudiations (from chargebacks). - `COLLECTED_FEES`– Detail of transactions crediting or debiting the fees wallet: successful transactions of all types (pay-ins, transfers, refunds, payouts, etc.) that have a positive or negative fees amount. Useful for platforms using [Echo](/guides/echo), Mangopay's solution for integrations working with third-party PSPs: - `ECHO_INTENT` – Summary of all intents declared during the selected period, detailing the total funds expected to enter the platform's technical wallets. - `ECHO_INTENT_ACTION` – Summary of all operations related to intents processed during the selected period, detailing the expected money movements to be escrowed — including payments, refunds, refund reversals, and chargebacks. - `ECHO_SETTLEMENT` – Summary of all settlement files uploaded during the selected period to initiate the reconciliation process, confirming the funds expected on the techncial wallet. - `ECHO_SPLIT` – Summary of all splits related to intents during the selected period, detailing the transfer of funds to the declared destination. title: ReportType_Reporting_Response ReportResponseFilters: type: object properties: {} description: >- The filters sent in the request. Different filters are available for each `ReportType`. title: ReportResponseFilters ReportResponseColumnsItems: type: object properties: Name: type: string description: The name of the column. IsDefault: type: boolean description: Whether the column is a default for the report or not. title: ReportResponseColumnsItems ReportResponse: type: object properties: Id: $ref: '#/components/schemas/Id' Tag: $ref: '#/components/schemas/Tag' CreationDate: $ref: '#/components/schemas/CreationDate' ReportDate: type: - integer - 'null' description: Unix timestamp (UTC) of the date and time the report was generated. Status: type: string description: >- **Returned values:** `PENDING`, `READY_FOR_DOWNLOAD`, `FAILED`, `EXPIRED` The status of the report: - `PENDING` – The report is being generated. - `READY_FOR_DOWNLOAD` – The report has been created, and can be downloaded. - `FAILED` – The report cannot be generated. - `EXPIRED` – The report was created, but is no longer available for download (it can be re-run to be downloaded again with fresh data). ResultCode: $ref: '#/components/schemas/ResultCode' ResultMessage: $ref: '#/components/schemas/ResultMessage' DownloadFormat: type: string description: |- **Returned values:** `CSV` The format in which the report is going to be downloaded. DownloadURL: type: - string - 'null' description: >- The URL at which the report file can be downloaded when the `Status` is `GENERATED`. ReportType: $ref: '#/components/schemas/ReportType_Reporting_Response' Sort: type: string description: >- The sorting direction of the CreationDate column. By default, the generated report is sorted by ascending creation date. DateRangeBy: type: - string - 'null' description: >- **Possible values:** `CreationDate`, `ExecutionDate` **Default value:** `CreationDate` The date to which `BeforeDate` and `AfterDate` apply. The `DateRangeBy` property can only be sent on `USER_WALLET_TRANSACTIONS` and `COLLECTED_FEES` reports. It is returned `null` for other types. The `ExecutionDate` value is likely to be more useful, because this is the date and time that the transaction `Status` became `SUCCEEDED`. Note also that these reports only contain successful transactions. AfterDate: type: integer description: >- **Possible values:** Any date and time (before the `BeforeDate`) between the present and 24 months ago. The date and time after which the report's transaction was created, based on the transaction's `CreationDate`. **Note:** The period between the `AfterDate` and the `BeforeDate` cannot exceed 12 months. BeforeDate: type: integer description: >- **Possible values:** Any date and time (after the `AfterDate`) between the present and 24 months ago. The date and time before which the report's transaction was created, based on the transaction's `CreationDate`. **Note:** The period between the `AfterDate` and the `BeforeDate` cannot exceed 12 months. Filters: $ref: '#/components/schemas/ReportResponseFilters' description: >- The filters sent in the request. Different filters are available for each `ReportType`. Columns: type: array items: $ref: '#/components/schemas/ReportResponseColumnsItems' description: >- **Possible values:** The columns listed in the [Reports](/reports) guide, which differ according to the report type. **Default values:** The default columns listed in the [Reports](/reports) guide, which differ according to the report type. The data columns to be included in the report. title: ReportResponse ``` ### Related resources #### [Guide](/reports) Learn more about reporting