> 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-customer-present-swipe.md).

# How to Process a Sale Customer Present Swipe

Take a card payment when the customer is present and swipes a magnetic stripe card.

{% hint style="info" %}
**Use this when** the customer is present at the counter and is paying by swiping a magnetic stripe card through your terminal.
{% endhint %}

{% hint style="warning" %}
**Do NOT use this when** the customer is paying by inserting a chip card or by contactless tap, 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 sale paid by swiping a magnetic stripe card, from entering the amount to the terminal returning to the main screen. A swiped sale is confirmed by checking the customer's signature rather than by PIN entry.

{% 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.

![Terminal screen asking Add a gratuity with red and green buttons](https://1291794278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0c7B1GHEHT6ss0tZUMMZ%2Fuploads%2FVO4WRyWnaTmgotEbBzuD%2Fsale-swipe-add-gratuity-prompt.png?alt=media)
{% endstep %}

{% step %}

### Swipe the card

The terminal prompts **Insert, Swipe or Tap Card**. Hold the magnetic stripe card with the stripe facing the keypad and swipe it through the magnetic card reader on the right side of the terminal.
{% endstep %}

{% step %}

### Check the customer's signature

After the card is swiped, the terminal prints a merchant receipt with a box for the customer's signature and prompts **Signature Valid – Check Customer Signature**. Have the customer sign, check the signature, then respond using the on-screen buttons.
{% endstep %}

{% step %}

### Wait for the connection

You may see **Connecting 1/3 – Please wait** while the terminal establishes a connection. This should only show for a couple of seconds.

![Terminal screen showing Connecting 1/3, Please wait](https://1291794278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0c7B1GHEHT6ss0tZUMMZ%2Fuploads%2F2xN8mnE4bMeAhlNvjF32%2Fsale-swipe-connecting-screen.png?alt=media)
{% endstep %}

{% step %}

### Confirm the approval

When the sale is approved, the terminal displays **Transaction Approved**. 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

* Swipe with the magnetic stripe facing the keypad.
* A swiped card is verified by signature, not PIN.
* The **Connecting** screen should only appear for a couple of seconds.

## FAQ

<details>

<summary>Do I need to enter a PIN for a swiped card?</summary>

No. When a card is swiped, the terminal asks you to check the customer's signature instead of asking for a PIN.

</details>

<details>

<summary>Why does the terminal show Connecting 1/3?</summary>

The terminal is establishing a connection to process the transaction. This screen should only show for a couple of seconds.

</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: swipe sale, magnetic stripe sale, MSR sale, customer present swipe, card swipe payment. Search terms: swipe, magnetic stripe, MSR, signature valid, check customer signature, gratuity, transaction approved.

</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-customer-present-swipe.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.
