> 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/v660p/how-tos/how-to-split-a-payment.md).

# How to Split a Payment

Split a bill into several card payments on your V660P.

{% hint style="info" %}
**Use this when** a customer wants to split a bill into more than one payment.
{% endhint %}

{% stepper %}
{% step %}

### Enter the total amount

On the **Connect Express** screen, enter the **total** amount.
{% endstep %}

{% step %}

### Open Split Payment

Tap **Other**, then tap **Split Payment**.
{% endstep %}

{% step %}

### Choose how to split

* **Equal Parts** — use **+** and **–** to choose how many equal parts to split the bill into.
* **Amount** — enter the amount this customer wants to pay.
  {% endstep %}

{% step %}

### Take the payment

Tap **Card** and take the payment as normal — see [How to Process a Sale](/support-nordics/v660p/how-tos/how-to-process-a-sale.md). Repeat for each part until the remaining amount is paid.
{% endstep %}
{% endstepper %}

<details>

<summary>Keywords</summary>

Also called: split payment, split the bill, pay in parts, equal parts. Search terms: split payment, split bill, equal parts, amount, other.

</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/v660p/how-tos/how-to-split-a-payment.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.