> 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-nordics/t650/how-tos/how-to-process-a-sale.md).

# How to Process a Sale

Take a card or alternative payment on a T650 terminal, get approval, and print a receipt.

{% hint style="info" %}
**Use this when** you need to take a standard card or alternative payment on a T650 terminal.
{% endhint %}

## Process a sale

{% stepper %}
{% step %}

### Enter the amount

Enter the **payment amount** and tap **Card**.
{% endstep %}

{% step %}

### Take the payment

The customer can insert, swipe, or tap their card/device, or select another payment option such as **Klarna**.
{% endstep %}

{% step %}

### Wait for approval

The terminal connects to the payment processor and receives **approval**.
{% endstep %}

{% step %}

### Choose a receipt option

Select the receipt option you prefer.
{% endstep %}
{% endstepper %}

{% embed url="<https://www.youtube.com/watch?v=FNobeUvOihM>" %}

<details>

<summary>Keywords</summary>

Also called: process a sale, take a payment, card payment, make a sale, contactless, chip and pin. Search terms: sale, payment, card, contactless, tap, Klarna, receipt.

</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-nordics/t650/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.