> 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-us/payware-connect/settlements.md).

# Settlements

What a Settlement is and how to process one from PAYware Connect and a variety of Verifone terminals.

## What is a Settlement?

A **Settlement** is the final stage of a transaction, where funds actually move from the buyer's bank to the seller's account, completing the purchase after authorization. It involves clearing and transferring money between financial institutions.

This happens in a **Batch** — a group of multiple transactions collected over a defined period (such as 24 hours or a month) and submitted together for final authorization and settlement.

Settlements can be completed on a terminal, or in PAYware Connect's Store Portal (for Merchants) or Corporate Portal (for Resellers).

## Related topics

* [Checking the Pre Settlement Report](/support-us/payware-connect/settlements/checking-the-pre-settlement-report.md) — see unsettled transactions before you settle a batch.
* [Performing a Settlement](/support-us/payware-connect/settlements/performing-a-settlement.md) — settle a batch automatically or manually.

<details>

<summary>Keywords</summary>

Also called: what is a settlement, batch settlement, settle transactions. Search terms: settlement, batch.

</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-us/payware-connect/settlements.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.