> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/vr-payment-gateway/vr-payment-gateway_en_us/refunds-and-payouts/payouts-and-tokens.md).

# Payouts and payment tokens

#### Payouts / bank matching

The **VR Payment Payouts** page shows bank movements reported by VR Payment with gross, net, and fee amounts. Mark a line as **matched in BC** once it appears on the bank statement.

The FactBox shows totals. Open payouts also appear as a dashboard tile.

{% hint style="info" %}
The cash receipt per invoice posts against the clearing account. Match the VR Payment payout here or on the bank statement – do not post it again as a customer payment.
{% endhint %}

#### Payment tokens

**VR Payment Tokens** lists payment methods stored at VR Payment (one-click). The app matches tokens to the customer automatically (external customer ID or email) and can delete tokens.

The job queue keeps the list current.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/vr-payment-gateway/vr-payment-gateway_en_us/refunds-and-payouts/payouts-and-tokens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.