> 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/v200c/how-tos/how-to-process-a-sale-ctls-contactess.md).

# How to Process a Sale CTLS (Contactess)

Take a contactless (tap) card payment when the customer is present.

{% hint style="info" %}
**Use this when** the customer is present at the counter and is paying by tapping a contactless card or device on your terminal.
{% endhint %}

{% hint style="warning" %}
**Do NOT use this when** the customer is paying by inserting a chip card or swiping a magnetic stripe card, the customer is not present (see How to Process a Customer Not Present Transaction), or you are refunding a customer (see How to Process a Refund).
{% endhint %}

This page walks through a contactless (CTLS) sale, from entering the amount to the terminal returning to the main screen. Contactless payments do not require a PIN or signature for transactions within the contactless limit.

{% hint style="info" %}
**Before you start.** Make sure the terminal is plugged in and you are logged in. The messages you see on screen depend on the settings enabled on your account and on how your POS provider has integrated the terminal, so your screens may differ slightly from those described here.
{% endhint %}

## Take the sale

{% stepper %}
{% step %}

### Enter the sale amount

On the main screen, key in the required amount, then press the green button (green circle) to start the transaction.
{% endstep %}

{% step %}

### Add a gratuity (if required)

When the terminal asks **Add a gratuity?** press the green button to add a gratuity or the red button to skip.
{% endstep %}

{% step %}

### Tap the card

The terminal prompts **Insert, Swipe or Tap Card**. Gently tap the customer’s contactless card or device onto the display where the contactless logo appears or hold it within 4 cm of the surface.
{% endstep %}

{% step %}

### Wait for approval

After the card is tapped, the terminal briefly shows **Card read OK** (this screen flashes for only a second). The terminal then connects to the PAYWare Ocius gateway. When the sale is authorized, a **Transaction Approved** message appears. Press the green bar at the bottom of the screen, the green circle button, or **Enter** to complete.
{% endstep %}

{% step %}

### Collect the receipt

The terminal shows **Printing – Please wait receipt is printing** while the receipt prints.
{% endstep %}

{% step %}

### Confirm the terminal is ready

When printing is complete, the terminal returns to the main menu, ready for the next sale.
{% endstep %}
{% endstepper %}

## Guidelines

* Contactless payments do not require a PIN or signature within the contactless limit.
* The **Card read OK** screen flashes briefly — this is normal.
* If the contactless tap fails, try again or ask the customer to insert the chip card instead.

## FAQ

<details>

<summary>Does a contactless payment need a PIN?</summary>

No. Contactless payments within the contactless limit do not require a PIN. The terminal may occasionally request a PIN for security — this is normal.

</details>

<details>

<summary>What if the tap doesn’t work?</summary>

Ask the customer to try tapping again, holding the card flat against the contactless logo on the display. If it still fails, ask the customer to insert the chip card instead.

</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 on the level of integration performed by your POS provider.

</details>

<details>

<summary>Keywords</summary>

Also called: contactless sale, tap sale, CTLS sale, NFC payment, tap and go. Search terms: contactless, CTLS, tap, NFC, card read OK, transaction approved, gratuity.

</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/v200c/how-tos/how-to-process-a-sale-ctls-contactess.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.
