> 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-norway/v660p/veiledninger/slik-deler-du-opp-en-betaling.md).

# Slik deler du opp en betaling

Slik deler du opp en regning i flere betalinger på din V660P.

{% hint style="info" %}
**Bruk denne siden når** en kunde vil dele opp en regning i flere betalinger.
{% endhint %}

## Del opp en betaling

{% stepper %}
{% step %}

### Skriv inn hele beløpet

Skriv inn **regningens totalbeløp** på skjermen i **Connect Express**.
{% endstep %}

{% step %}

### Åpne Delt betaling

Trykk på **Annet**, og deretter **Delt betaling**.
{% endstep %}

{% step %}

### Velg hvordan regningen skal deles

* **Like deler:** bruk **+** og **–** for å velge hvor mange like store deler regningen skal deles i.
* **Beløp:** skriv inn beløpet denne kunden vil betale.
  {% endstep %}

{% step %}

### Ta betalt

Trykk på **Kort** og ta betalt som vanlig — se [Slik gjennomfører du et salg](/support-norway/v660p/veiledninger/slik-gjennomforer-du-et-salg.md). Gjenta for hver del til hele beløpet er betalt.

✅ **Hele regningen er nå betalt.**
{% endstep %}
{% endstepper %}


---

# 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-norway/v660p/veiledninger/slik-deler-du-opp-en-betaling.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.