> 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/fastpin-sale-return.md).

# FastPIN Sale / Return

### FastPIN Sale

The FastPIN Sale transaction request prompts the InComm system to return a message containing a PIN. The system initiates the request at an indoor POS when the cashier adds a Fast PIN Sale to the merchandise and the customer pays the appropriate amount.

#### FastPIN Sale Steps

{% stepper %}
{% step %}
**PLU**

From the POS, scan or enter the item **\[PLU]**.

{% hint style="info" %}
If Pre-validate parameter is enabled, the POS sends a pre-authorization request for activation before swiping the card.
{% endhint %}
{% endstep %}

{% step %}
**TOTAL**

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

{% step %}
**Cash or Credit**

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

An approved message displays on the POP PIN pad. A receipt prints displaying:

* PIN
* terms and conditions

### FastPIN Return

The FastPIN Return transaction request allows a return for a previously authorized PIN request. An indoor POS initiates this request when a customer returns a Fast PIN sale is.

#### FastPIN Return Steps

{% stepper %}
{% step %}
**POS**

From the POS, press **\[REFUND]**.
{% endstep %}

{% step %}
**Item**

Enter the item **\[PLU]**.
{% endstep %}

{% step %}
**CASH or CREDIT**

Select **\[CASH]** or **\[CREDIT]**.
{% endstep %}

{% step %}
**Enter PIN**

Enter the **\[PIN]** and \<Approval Code> of the FastPIN Sale.
{% endstep %}
{% endstepper %}

The POP PIN pad displays an approved return message, and the POS prints a receipt with the return approval.


---

# 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/fastpin-sale-return.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.
