> 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/payments/transactions.md).

# Transactions

Each payment at VR Payment is stored as a transaction in Business Central and matched to the payment link or document.

#### Matching

The app finds the matching link via:

1. Merchant reference (`merchantReference` / `invoiceMerchantReference`), including the prefix on the external ID (`<document no.>-<timestamp>`)
2. Amount matching – independent of link status

On the next sync, existing unmatched transactions are linked retrospectively.

#### Actions on the transaction card

* **Capture payment** – visible for authorised payments
* **Void transaction** – before capture
* **Create refund** / **Show refunds**
* **Post cash receipt** / **Create journal line**
* **Show customer ledger entries**

Capture and void appear depending on transaction status.

#### Status on the document

**Update payment status** on the order or posted invoice reports the status found, or tells you that no transaction has been matched yet.

```mermaid
stateDiagram-v2
    [*] --> Authorized
    Authorized --> Completed: Capture
    Authorized --> Voided: Void
    Completed --> Refund: Refund
```


---

# 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/payments/transactions.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.