# List View vs. Detail View
source: https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/list-view-detail-view/index.md

This article offers some suggestions for how you can use the response data you receive from Consumer Clarity API calls and highlights the differences between using the data in a list view vs. a detail view.

## Overview {#overview}

Typically, there are two areas in your banking app where you use the response data: a **list view** and a **detail view** .  

* **List view:** A list of all transactions for a particular account, which is displayed to the cardholder through your banking app.
* **Detail view:** A detailed transaction that is displayed to the cardholder after they have selected it from the **list view** .   

This image shows an example of how each of these views might look in a banking app:
![List View versus Detail View](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/list-view-vs-detail-view.png)

## Present the response data in list view {#present-the-response-data-in-list-view}

You can populate the transactions in a **list view** with recognizable merchant names by using the **merchantName** response field. And if it's available, you can also present the **logos** response to your cardholders. This image shows an example of how you might typically present this response data in your app:
![List View Matching with Response Data](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/list-view-matching.png)

## Present the response data in detail view {#present-the-response-data-in-detail-view}

When a cardholder selects a specific transaction from the **list view**, a new page opens where they see more details about the merchant and the transaction.

You can use the same **merchantName** and **logos** responses in your **detail view** as you did for your **list view** . In addition, you can present the response data for fields such as **description** . And if you receive response data for **websiteUrl**, you can display it to your cardholder in the form of a button or link.

Use these response data fields to populate your **detail view** as shown in this image:
![List View Matching with Response Data](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/detail-view-matching2.png)

## Next Steps {#next-steps}

* [Guidance for Caching Response Data](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/caching-response-data/index.md) provides guidelines to follow for caching the Consumer Clarity API response data.
* [Display Merchant Details](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/displaying-merchant-details/index.md) suggests different ways you can use the merchant detail response data in your banking app.
* [Display Transaction Details](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/displaying-transaction-details/index.md) offers tips for how to display transaction detail response data in your banking app.
* [Display Smart Subscriptions](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/how-to-use-response-data/displaying-subscription-controls/index.md) offers tips for how to display Smart Subscriptions response data in your banking app.
* Review [Tips for Sending Requests](https://developer.mastercard.com/consumer-clarity/documentation/tutorials-and-guides/tips-for-sending-requests/index.md) for suggestions to consider when sending your requests.