> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/incomm/using-incomm/store-credit.md).

# Store Credit

Store Credit is a two part transaction.

#### First Transaction

The transaction request is initiated when a customer comes to the store to return a previous purchase.

{% stepper %}
{% step %}
**Refund**

Press **\[REFUND]**.
{% endstep %}

{% step %}
**PLU**

Scan or enter the item **\[PLU]**.
{% endstep %}

{% step %}
**Cash**

Select **\[CASH]**.
{% endstep %}
{% endstepper %}

#### Second Transaction

Once the refund is complete, the cashier initiates a new transaction to activate an InComm Closed Loop card with the amount to be returned. The activated card is then given to the customer.

{% stepper %}
{% step %}
**Scan**

Scan the card’s bar code at the POS.
{% endstep %}

{% step %}
**Total**

Press **\[TOTAL]**.
{% endstep %}

{% step %}
**Cash**

Select **\[CASH]**.
{% endstep %}
{% endstepper %}

If the card is activated, the POP device displays an Approved message, and the terminal prints a receipt displaying:

* masked account number
* authorization number
* balance amount


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/incomm/using-incomm/store-credit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
