> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/selling/payments/payment-methods/credit-voucher.md).

# Credit Voucher

Give a customer credit to spend later instead of money back.

## What is this?

A credit voucher is store credit you hand out instead of paying a customer back. The till creates it when you settle a return with this method, and the customer spends it on a later purchase. At the till it is called **Store credit**.

Unlike a gift card, a voucher is never bought. It exists only because you issued one.

## How does it work?

**Issuing.** On a return, choose the method. There is nothing to type in — Flow Retail creates a voucher for the amount owed and puts its number and valid-to date on the receipt.

**Redeeming.** On a sale, choose the method and fill in **Store credit number**. The till looks it up, shows the balance, and fills the amount with whichever is smaller — the balance or what is left to pay. A voucher that has expired, is no longer active, or does not cover the amount entered is refused.

{% hint style="info" %}
Vouchers and gift cards share that system, but they are kept apart. A credit voucher cannot be spent as a gift card, and a gift card cannot be spent as a credit voucher — even after store credit is switched off, because the vouchers already out there still exist.
{% endhint %}

## How do we get started?

Credit vouchers run on the Flow Gift Card system, so that extension has to be active before the payment method is offered at all.

On top of that, vouchers need their own account. Add store credit to each store on the store's **Extensions** tab and fill in **Store Credit Merchant ID**, **Store Credit Merchant Token** and **Store Credit Brand ID**. The brand is what separates vouchers from gift cards.

Then add the payment method under **Admin → Settings → Payment Methods**, and set it <kbd>Active</kbd> on every store that should issue or accept vouchers.

*Last updated 17.09.2026*


---

# 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.flowretail.com/docs/day-to-day-operations/selling/payments/payment-methods/credit-voucher.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.