# Data. How to get the best results #### Data Richness * The quality and amount of transaction data has a **big impact** on the accuracy of results. The data available may vary at different stages of processing (e.g. Pending, Pre-authorised, Authorised but not posted) * You should attempt to include as many input fields as possible in your requests to MRS. See the [OpenAPI Docs](/openapi-docs.md) for the fields we support. All are valuable, but the most valuable are, in order: * `country` * `mcc` (see [Merchant Category Codes](/basic-concepts/merchant-category-codes.md)) * `city` * `location` * (This is in addition to the `merchant_name` and `type` parameters, which are both mandatory). #### Data Notes * MRS requires information about the merchant involved in the transaction. * MRS does not process end-user personal data * The collected data may be “messy” and not all fields may be available for all transactions. * Often only one single field with location is available. Also, the merchant description may include location information. --- # Agent Instructions: 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: ``` GET https://devs.snowdropsolutions.co.uk/implementation-guides/data.-how-to-get-the-best-results.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.