> 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/ux700/how-tos/how-to-process-a-purchase-transaction.md).

# How To Process a Purchase Transaction

Process a purchase transaction on the UX700 terminal, from amount entry to receipt.

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

{% hint style="warning" %}
**Do NOT use this when** you need a refund, void, or split payment instead — see the relevant guide for those transaction types.
{% endhint %}

This page explains the full purchase transaction flow on the UX700, including amount entry, card presentation, PIN or signature verification, and receipt handling.

## Process the purchase

{% stepper %}
{% step %}

### Enter the amount

Enter the transaction amount. The maximum possible amount is configurable and defaults to €1,000,000. Purchase transactions with an amount of 0.00 are not allowed. Press **C** at any point to reset the current amount.
{% endstep %}

{% step %}

### Start the card payment

Select the **Card** button to start the card payment. Selecting **Other** instead presents other transaction options, such as refund.
{% endstep %}

{% step %}

### Present the card

Once the amount is entered and **Card** selected, the customer can insert, tap, or swipe the card. The terminal shows a "Please Wait…" screen while it processes the card data.
{% endstep %}

{% step %}

### Enter the PIN (if required)

If the card's verification method is PIN, the terminal prompts for it after the "Please Wait…" screen. The **Enter** key is not active until 4 digits have been entered. Press **C** to reset the PIN entry. If an incorrect offline PIN is entered and **Enter** is pressed, the terminal shows a warning. Cards that don't use PIN verification skip this screen entirely.
{% endstep %}

{% step %}

### Wait for authorisation

The terminal displays "Authorising…" while it communicates with the acquirer's host system to authorise the transaction online.
{% endstep %}

{% step %}

### Confirm approval and remove the card

Once authorised, the terminal shows an "Approved" screen and plays a notification sound until the card is removed. The customer must remove the card.
{% endstep %}

{% step %}

### Sign the receipt (if required)

If the card's verification method is Signature, and the transaction amount is above the signature-required minimum, the customer signs the receipt. Press **Clear** to redo the signature, then **Done** once signed. Cards that don't require a signature skip this step and go straight to receipt printing.
{% endstep %}

{% step %}

### Return the device for signature verification

The customer returns the device to the merchant. The merchant presses **Done** once the device has been returned, then approves or rejects the signature: **No** if it doesn't match the card (the transaction is declined and reversed), or **Yes, Approve** if it matches.
{% endstep %}

{% step %}

### Choose the customer receipt option

If receipt printing is enabled in device configuration, select how to handle the customer receipt: **Print**, **Email** (you'll be asked to enter an email address), **Print & Email**, or **No Thanks** to skip straight to the merchant receipt.
{% endstep %}

{% step %}

### Tear off the receipt (if applicable)

If the terminal is configured to print two receipts back-to-back, you'll be prompted to tear off the first receipt before the next prints. Press **Continue** once torn off — if this screen times out, the merchant receipt prints anyway.
{% endstep %}

{% step %}

### Merchant receipt prints

The terminal prints the merchant receipt. The payment process is now complete, and the device returns to the default amount entry screen.
{% endstep %}
{% endstepper %}

## Guidelines

* The default maximum transaction amount is €1,000,000, and this is configurable.
* A PIN prompt only appears for cards whose verification method is PIN; a signature prompt only appears for cards whose verification method is Signature and only above the signature-required minimum amount.
* If a signature doesn't match, pressing **No** declines the transaction and sends a reversal.

## FAQ

<details>

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

This depends on the card's cardholder verification method (CVM). Cards that don't use PIN or Signature verification skip those screens entirely.

</details>

<details>

<summary>What happens if the signature doesn't match?</summary>

Press **No** at the signature approval prompt — the transaction will be declined and a reversal sent.

</details>

<details>

<summary>Keywords</summary>

Also called: purchase, sale, card transaction. Search terms: transaction selection, amount input, PIN, signature, authorising, approved, receipt, UX700.

</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/ux700/how-tos/how-to-process-a-purchase-transaction.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.
