> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/features-and-products-references/gift-cards.md).

# Gift Cards

Gift Cards on the Verifone Commander let a site sell, activate, recharge, and accept prepaid gift cards at the register and at the pump.

## Overview

Gift Cards on the Verifone Commander let a site sell, activate, recharge, and accept prepaid gift cards at the register and at the pump. This Feature Reference describes how the feature works, how to configure it from Configuration Client, and how cashiers use it day to day.

Gift cards are prepaid cards loaded with a specific monetary value and used as an alternative to cash. A customer buys a card, the cashier activates it for the chosen amount, and the card can then be used to pay for purchases, including fuel, until its balance runs out. Cards can be recharged with additional value at any time.

Gift cards come in three forms: closed-loop cards, tied to one retailer or brand family; open-loop cards (such as Visa or Mastercard gift cards), accepted anywhere the card brand is accepted; and digital gift cards delivered by email or app, which can be either type. This Feature Reference covers the closed-loop gift card programs processed through the Commander's electronic payment system.

{% hint style="info" %}
For InComm gift cards, refer to the InComm Feature Reference.
{% endhint %}

### Business Value

* Gifting and convenience: customers buy cards as gifts, and recipients choose what to spend them on -- a proven driver of store visits.
* Promotions and rewards: sites and brands use gift cards in loyalty programs, promotions, and employee rewards.
* Prepaid revenue: the site receives payment when the card is sold; the value is spent in later visits, encouraging return traffic.

### Supported Hardware & Prerequisites

<table><thead><tr><th width="191.7777099609375">Requirement</th><th>Details</th></tr></thead><tbody><tr><td>Site controller</td><td>Verifone Commander Site Controller (base version 50 or higher) or RubyCi, with Topaz or Ruby2 POS</td></tr><tr><td>Payment devices</td><td>Payment PIN pad(s); fuel dispensers with a Dispenser Card Reader (DCR) for pump acceptance</td></tr><tr><td>Gift card program</td><td>An active gift card program with the site's card provider -- the provider supplies the cards and processes activations, recharges, and redemptions through the payment network</td></tr></tbody></table>

### Feature Restrictions

* Refunds are not allowed on gift card tenders. To return money to a customer, process the refund as normal on the register and then recharge the gift card for the refund amount.
* Typical gift card program policies -- confirm the specifics with your card program provider: cards are not redeemable for cash, lottery, money orders, or other gift cards; cards cannot pay house account balances or third-party fleet card balances; gift cards cannot be purchased with other gift cards; lost or stolen cards are generally not replaced.

### Interaction with Other Features

* Loyalty: at sites with a loyalty program, the customer may be prompted for their loyalty number before tendering an activation, recharge, or fuel purchase.
* Split tender: if a purchase exceeds the card's remaining balance, the customer is prompted for an additional form of payment for the difference.
* Receipts: the card's remaining balance prints at the bottom of the receipt after every purchase, activation, or recharge.

### Glossary of Terms

<table><thead><tr><th width="176.22216796875">Term</th><th>Definition</th></tr></thead><tbody><tr><td>CTI</td><td>Card Type Indicator</td></tr><tr><td>DCR</td><td>Dispenser Card Reader</td></tr><tr><td>EOD</td><td>End of Day</td></tr><tr><td>EPS</td><td>Electronic Payment Server</td></tr><tr><td>FEP</td><td>Front End Processor</td></tr><tr><td>GPR</td><td>General Purpose Reloadable card</td></tr><tr><td>MOP</td><td>Method of Payment</td></tr><tr><td>PAN</td><td>Personal Account Number</td></tr><tr><td>PIN</td><td>Personal Identification Number</td></tr><tr><td>PLU</td><td>Price Look Up</td></tr><tr><td>POP</td><td>Point of Purchase (commonly, a PIN pad)</td></tr><tr><td>POS</td><td>Point of Sale</td></tr><tr><td>RTR</td><td>Real Time Recharge</td></tr><tr><td>SAF</td><td>Store and Forward</td></tr><tr><td>TOR</td><td>Time Out Reversal</td></tr><tr><td>UPC</td><td>Universal Product Code</td></tr></tbody></table>


---

# 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.verifone.com/feature-references/features-and-products-references/gift-cards.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.
