> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/abc-ignite/abc-ignite-engagement-app/rewards-page/reward-voucher.md).

# Reward voucher

After a member redeems points for a reward in the ABC Ignite Engagement app, they can view the resulting **Perkville voucher** on this page. The voucher confirms the Perkville redemption and contains the instructions for claiming the reward. Members may need to show it to staff at the front desk or follow another fulfillment process configured by the business.

{% hint style="info" %}
**Redeeming in the app is not the same as fulfilling a reward in ABC Ignite.** The standard ABC Ignite integration does **not** automatically apply a credit, service, discount, or coupon in ABC when a member redeems Perkville points. Follow the instructions on each voucher and any business-specific fulfillment process. A voucher being issued does not mean the reward has already been provided.
{% endhint %}

For general voucher types, statuses, and how staff handle redemptions, see [Vouchers](https://docs.perkville.com/features/vouchers.md) and [Understanding voucher redemptions and mistaken redemptions](https://docs.perkville.com/faqs/redemptions/understanding-voucher-redemptions-and-how-to-handle-mistaken-redemptions.md). General Perkville reward options do not establish that ABC Ignite itself fulfills those rewards.

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FwnMJKdBnF2ELWgEg5c6s%2FABC%20mobile%20app%20Perkville%20reward%20voucher%20page.png?alt=media&amp;token=f77a5fad-7772-4c6d-959d-8339ffeb2ca3" alt="" width="285"><figcaption></figcaption></figure>


---

# 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.perkville.com/integrations/integration-reference/abc-ignite/abc-ignite-engagement-app/rewards-page/reward-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.
