> 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/support-uk/p400/how-tos/how-to-process-a-sale.md).

# How to Process a Sale

What happens on-screen when processing a sale on the P400+ in an integrated (POS-driven) setup.

{% hint style="info" %}
**Use this when** the customer is present and paying by card on a P400+ terminal integrated with a POS.
{% endhint %}

{% hint style="warning" %}
**Do NOT use this when** the customer is not present (see How to Process a Customer Not Present Transaction), or when you are processing a refund (see How to Process a Refund).
{% endhint %}

This page explains what happens on-screen when processing a sale on the P400+. The messages shown depend on the settings enabled on your account and the level of integration performed by your POS provider, so your screens may differ slightly from those described here.

{% hint style="info" %}
**Before you start.** The sale is initiated from the POS; the terminal is ready to receive the instruction.
{% endhint %}

## Process the sale

{% stepper %}
{% step %}

### Terminal receives the sale

The terminal is ready to receive an instruction from the POS.
{% endstep %}

{% step %}

### Add a gratuity (if enabled)

The terminal may ask **Would you like to add a gratuity?** — this only shows if gratuity is enabled on your account. If you select yes, enter the gratuity amount.
{% endstep %}

{% step %}

### Present, insert, or swipe the card

The terminal prompts for the payment card. Present, insert, or swipe the card as appropriate.
{% endstep %}

{% step %}

### Enter the PIN (chip cards only)

If the card was inserted, the terminal asks for the PIN. This step is skipped for swiped or contactless payments.
{% endstep %}

{% step %}

### Wait for the gateway response

The terminal connects to, and awaits a response from, the Verifone PAYWare Ocius Gateway.
{% endstep %}

{% step %}

### Transaction approved

The transaction is successfully approved.
{% endstep %}

{% step %}

### Receipts print

The merchant copy of the receipt prints first. Once card processing is complete, the cardholder can remove their card, and the customer copy of the receipt prints.
{% endstep %}

{% step %}

### Terminal ready for the next transaction

The transaction is complete and the terminal is ready to receive the next instruction from the POS.
{% endstep %}
{% endstepper %}

## Guidelines

* On-screen messaging depends on the settings enabled on your account and the level of integration performed by your POS provider.
* The gratuity prompt only appears if gratuity is enabled on your account.
* The PIN prompt only appears for inserted (chip) cards.
* Wait for the cardholder to remove their card before the customer receipt prints.

## FAQ

<details>

<summary>Why don't I see a gratuity prompt?</summary>

The gratuity prompt only appears if it is enabled on your account.

</details>

<details>

<summary>Why wasn't I asked for a PIN?</summary>

A PIN is only requested if the card was inserted (chip). Swiped and contactless payments do not require a PIN.

</details>

<details>

<summary>Why don't the screens on my terminal match this page?</summary>

On-screen messaging depends on the settings enabled on your account and the level of integration performed by your POS provider.

</details>

<details>

<summary>Keywords</summary>

Also called: integrated sale, POS-driven sale, card sale. Search terms: sale, gratuity, PIN, PAYWare Ocius Gateway, transaction approved, P400+.

</details>


---

# 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/support-uk/p400/how-tos/how-to-process-a-sale.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.
