> For the complete documentation index, see [llms.txt](https://features.revver.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.revver.tech/features/2.-pos-features/2.3-transaction-checkout.md).

# 2.3 Transaction Checkout

revver POS supports multiple payment methods for completion of a sale. This includes traditional cash payments to the most modern touch/ QR code based payments.

### Cash & Foreign Currency

POS display cash & foreign currency with bank note images which helps the user select the right denomination visually. The change is also auto calculated & rounding is applied when needed.

### Cards

#### Bank Cards

The card entry includes tap, chip entry, swipe. These include VISA, Mastercard, Amex, Postfinance etc.

#### Fuel Cards

Fuel cards can be accepted by scan, magstripe entry based on terminal support. Currently this includes SOCAR card, Tamoil card, DKV, UTA etc.

#### Gift Card

POS supports purchase of articles with gift cards as method of payment.

### Others

#### Vouchers

POS supports acceptance of cashless vouchers \[paper & digital]. This includes acceptance of cumulus UCB's,  station provided vouchers, over payment vouchers etc.

#### Configurable Manual Payment Methods

POS supports accepting payments with manual payment means which are configurable. This could include merchant specific paper vouchers.

### Loyalty

Scanning of loyalty cards, awardingof points is supported by the Revver POS.


---

# 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://features.revver.tech/features/2.-pos-features/2.3-transaction-checkout.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.
