> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/integrations/using-limio-for-salesforce/manage-subscriptions-flow/subflow-refund/add-refund-reasons.md).
# Add Refund Reasons to Refund Journey
By default, the refund journey does not require specifying a reason for the refund.
A list of reasons however can be configured, captured as part of the flow, and in turn the selected reason will be sent to Limio.
The values set for the picklist are stored in the Subscription Action metadata of ic Assist Config.
Values being rendered are listed in the refundReasons array, and then retrieved in apex by the method "Get refund reasons" and then stored in the flow variable refundReasons, an apex class of type List\
Should a more sophisticated logic be required for dynamically fetching picklist values, it is possible to replace this apex action with another custom action, as long as the results are of the same type i42as\_\_PicklistChoice and then stored in the flow variable refundReasons.
The Refund Screen flow element will read this value and render the list dynamically.
---
# 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://docs.limio.com/integrations/using-limio-for-salesforce/manage-subscriptions-flow/subflow-refund/add-refund-reasons.md?ask=&goal=
```
`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.