> For the complete documentation index, see [llms.txt](https://devs.snowdropsolutions.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devs.snowdropsolutions.co.uk/implementation-guides/additional-ux-considerations.md).

# Additional UX Considerations

* Consider providing the **original merchant description** and perhaps other transaction info at the bottom of the Detail View page. This can be useful for your customer service function, should they be contacted about a transaction and they do not have access to the enriched information.
* The transaction categories can be used to present summarised spending to your users (see [Additional UX Considerations](/implementation-guides/additional-ux-considerations.md)).
* Consider allowing your users the ability to re-categorise specific transactions themselves.
* You may also wish to summarise transaction info in other ways:
  * List the merchants that your users spend the most money with.
  * You can summarise recent spending on a map.

#### Examples

<figure><img src="https://lh7-us.googleusercontent.com/1QQcPVSE3WbvmMH85vtKjki3gsFP9pc_SvZHtTBfPnU3OOkOQLg95EdmhOoBy-aiCAXPeXdy-ZXVCjTAvEtVpFlZW4BwL80IngK5qHi3hgsL0rQDxP5P96XZTacPQsoqUHDhqDc8JbdyI9MtQreppuQSLQ=s2048" alt="" width="375"><figcaption><p>Transaction Categorization</p></figcaption></figure>

<figure><img src="https://lh7-us.googleusercontent.com/ZR17qd3eUwkYfFEIczeNh5JSkycZKGwOJ8RLsb9Dn7SlSU34mm5TviF-PJLcvS4qjevfm0pyn3SIR3CtnrtNd5TDYRMiAjB56D2U_c8_1Hkucdy308P8VX0YP4HH74qE8tVeRruaZyl8RbSImPlvhiDpWQ=s2048" alt="" width="375"><figcaption><p>Top Merchant</p></figcaption></figure>

<figure><img src="https://lh7-us.googleusercontent.com/VsgJQUOvoX5SRrCuvSsYHp50WbEyWS6K2ae2WQvPG4tZF7Nd7rF3-mG65DYE3IS4HPo7gW8n1lKjZPbgzyiYdYm6jEYId5nuBRA-CtSRLk7b2L4YfqHFyydoytH3Y2bcAvZ4OZwd0mSUGnGtu0l4rrcBYQ=s2048" alt="" width="375"><figcaption><p>Recent spends map</p></figcaption></figure>

<br>

<br>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://devs.snowdropsolutions.co.uk/implementation-guides/additional-ux-considerations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.