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

# Sales

## Proprietary Transaction

{% stepper %}
{% step %}
**Start the Sale**

From the POS, enter the **\<sale items>**.

Press **\[TOTAL]**.

Press **\[CREDIT]**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/izDR4ci9gN9KGbEZuqb5/Unknown%20image)
{% endstep %}

{% step %}
**Complete Card Authorization**

A message will prompt to ***“Ask customer to swipe card. Follow PINpad Instructions.”***

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/dvTT68lTZMKjPEzuMJi8/Unknown%20image)

The customer swipes their card and completes the requested information on the PINpad.

The receipt prints when authorization is received.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/rr5x0KsaGGmu1J14A563/Unknown%20image)
{% endstep %}
{% endstepper %}

## Manual Card Entry Transaction

In some instances, the card magstripe is unreadable and the card number and expiration date must be manually entered.

{% hint style="info" %}
Manual Entry requires an existing Method of Payment definition using MOP Code: 25-Manual\_Entry.
{% endhint %}

{% stepper %}
{% step %}
**Open Other MOP**

From the POS, enter the **\<sale items>**.

Press **\[TOTAL]**.

Press **\[OTHER MOP]**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/izDR4ci9gN9KGbEZuqb5/Unknown%20image)

The Other MOP window displays.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/oCdHUOH4PXvW4E2rTbeH/Unknown%20image)
{% endstep %}

{% step %}
**Manual Entry MOP**

Select the **Manual Entry MOP**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/kqZhY1wFgjAbsU1UmFoG/Unknown%20image)
{% endstep %}

{% step %}
**Enter Card Details**

Enter the **\<account number>**.

Press **\[OK]**.

Enter the **\<month>** and **\<year>** and (MMYY) of the card expiration date.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/GNptteqviPCnF22zs03Z/Unknown%20image)

Press **\[OK]**.

The receipt prints when authorization is received.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/kH8gaMNdkx0rD7REiogH/Unknown%20image)
{% endstep %}
{% endstepper %}


---

# 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://docs.verifone.com/feature-references/features-and-products-references/proprietary-fep-interface/using-proprietary-fep-interface/sales.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.
