# Display Consumer Clarity
source: https://developer.mastercard.com/consumer-clarity/documentation/clarity-in-clearing/cic-display-clarity/index.md

There are several options for how you can use the merchant details data and the Digital Receipts URL within your banking applications.

This guidance focuses on enhancing the transaction list and transaction detail views in banking applications. When applying these recommendations, consider the design and constraints of your application, including factors such as pagination and available screen space.

This table of suggested uses shows the clearing data fields you receive and offers direction on which fields should be customized, along with recommendations for how those customizations can be applied.

### Suggested uses {#suggested-uses}

|         Response field name         | Use as received | Customize before use |      Suggested use      |
|-------------------------------------|-----------------|----------------------|-------------------------|
| Enhanced Acceptor Name              | x               |                      |                         |
| Enhanced Acceptor Geolocation       |                 | x                    | Convert to map          |
| Enhanced Acceptor Longitude         |                 | x                    | Convert to map          |
| Enhanced Acceptor Latitude          |                 | x                    | Convert to map          |
| Enhanced Geolocation Proximity Type | x               | x                    | Convert to map          |
| Acceptor Logo URL                   | x               |                      | Display a logo          |
| Digital Receipts URL                | x               |                      | Provide Digital Receipt |

## List View and Detail View {#list-view-and-detail-view}

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 the banking application. Here, you can display the transactions with recognizable merchant names by using **Enhanced Acceptor Name** . And if it's available, use **Acceptor Logo URL** to display the merchant's logo.

* **Detail view** : Details for a single transaction that are displayed after the cardholder selects a transaction from the list view. For detail view, you can use the same **Enhanced Acceptor Name** and **Acceptor Logo URL** and also present response data for **Enhanced Acceptor Geolocation** . And if a **Digital Receipts URL** is received, display it as a button or link.

![Examples of list view versus detail view](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/clearing/list-view-vs-detail-view.png)

## Convert Geolocation to Map {#convert-geolocation-to-map}

**Enhanced Acceptor Geolocation** coordinates can be used to generate a map using these features:

* **Enhanced Acceptor Latitude**
* **Enhanced Acceptor Longitude**

For more information about how to do this, follow the instructions for whichever mapping tool you'll be using.

The latitude and longitude coordinates can vary in proximity to the actual location depending on how accurate or reliable a merchant address is. **Enhanced Geolocation Proximity Type** helps you understand the proximity of the latitude and longitude data that's returned to the actual merchant store location.

Here are details about the values returned by **Enhanced Geolocation Proximity Type** including a graphic showing how each value can be displayed to your users:

### Proximity types {#proximity-types}

|   Proximity type    |                                                            Description                                                            | Estimated distance from actual location |
|---------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|
| Storefront          | Most precise location of a merchant store. Typically points to the exact store location.                                          | Less than 10m                           |
| Rooftop             | Approximate physical address of the building where the merchant store is located.                                                 | 10m to 160m                             |
| Block               | Based on a complete street address. Points to the block where a merchant store is located.                                        | 160m to 600m                            |
| Street              | Less proximate than Block. Points to the street where a merchant store is located.                                                | 600m to 1km                             |
| Postcode            | Based on postal code. In some locations, this can be quite accurate such as in the UK where every block might have a postal code. | 1k to 2km                               |
| Administrative area | Least precise. Usually a city, region, or village.                                                                                | More than 2km                           |

![Examples of Geolocation Proximity Types](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/clearing/geolocation-type-2.png)

## Display a Logo {#display-a-logo}

The **Acceptor Logo URL** can be managed so that it displays nicely in the banking application and doesn't use too much of your available real estate.

### Suggestions for using response data for logos {#suggestions-for-using-response-data-for-logos}

For the best user experience, we recommend you use a square frame with softened edges to display logos. If you prefer to use a circle frame instead, you might need additional configuration to ensure fit, and the logo may appear smaller. Also, since most logos are padded with a white background, they render best on white or light-colored backgrounds.

![Example of how to display logo](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/clearing/logo-size.png)

## Provide a Digital Receipt {#provide-a-digital-receipt}

To let cardholders access Digital Receipts in your banking application, you can provide the Digital Receipt link under a **View Receipt** button. When selected, another page in the application would open where the cardholder can see all the information available in the Digital Receipts URL, such as descriptions and prices for each item purchased.

![Example of digital receipt displayed in banking app](https://static.developer.mastercard.com/content/consumer-clarity/documentation/img/clearing/sample-digital-receipt.png)

For more guidance on appending a Digital Receipts URL with the access token required to make it usable in your banking app, see [Request Access Token](https://developer.mastercard.com/consumer-clarity/documentation/clarity-in-clearing/cic-request-access-token/index.md).

## Next Steps {#next-steps}

Now that you've reviewed the guidance for displaying the clearing data in your banking app, see [Test Clarity in Clearing Data](https://developer.mastercard.com/consumer-clarity/documentation/clarity-in-clearing/cic-testing/index.md) for examples of digital receipt responses you'll receive from some sample test case.