# EPS Loyalty
## Revision History
| Date | Description |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 09/25/2015 | Reformatted and revised to include the Verifone Commander. |
| 08/10/2016 | Updated Loyalty Card Configuration to include configuration for GS-128 loyalty cards. |
| 09/15/2016 | Updated Format. |
| 12/14/2016 | Updated PCI private IP addressing requirements. |
| 03/07/2018 | Updated Integrated Partners List link. |
| 06/15/2018 | Updated Loyalty Program Configuration to include new screenshot and configuration for the Enable Card Download from Host flag. |
| 10/08/2019 | Added loyalty network connectivity diagrams, added a phone number entry method configuration, and added notes to the various inside and outside transaction flows for multiple loyalty. |
| 03/21/2023 | Updated the PCATS01 graphic and removed references to Enhanced Zone Router (EZR). |
| 04/05/2024 | Added "Remote Loyalty Enable/Disable" feature. |
| 04/01/2025 | Added "Use Long Text For Indoor Prompts" and cashier option to cancel loyalty prompt. |
| 09/03/2025 | Updated with QR code for Loyalty Program Enrollment Inside |
| 12/24/2025 | Updated with QR code for Loyalty Program Enrollment Outside |
## Overview
### Feature Description
Electronic Payment System (EPS) Loyalty Sales allow the processing and redemption of loyalty transactions, both inside at the Point of Sale (POS) and outside at the Dispenser Card Readers (DCR).
Loyalty transactions are processed through the EPS. EPS Loyalty Sales include:
* Inside Loyalty Sales
* Outside Loyalty Sales
Multiple loyalty programs can be configured and multiple EPS Loyalty Discounts can be applied.
## Requirements
### Hardware Requirements
* Verifone Commander with C18/Topaz/Ruby2
* Verifone RubyCi with C18/Topaz/Ruby2
* Verifone Commander 16 with C18/Topaz/Ruby2
## Loyalty feature updates
### QR code for loyalty program enrollment
From Verifone Commander Release 56.02, QR code display for loyalty program enrollment feature has been implemented for inside transactions.
During a transaction, after it has been determined that a customer is not yet a loyalty customer of one of the available configured loyalty program(s) at the site, a QR code is displayed on the PIN pad that consumers can scan to sign up for Loyalty.
For Verifone Commander Release 56.02, this feature is available only for M400 PIN pads.
From Verifone Commander Release 57.00, QR code for Loyalty sign-up is displayed on DCR displays, DCR receipts, and POS receipts.
## Loyalty connectivity diagram
### MNSP router
The loyalty is processed though the MNSP Edge Router.
## Configuration
### Before you start
Prior to configuring EPS Loyalty, the following information must be acquired:
* Loyalty host IP
* Port for IP communication with the loyalty host
* Custom reconciliation period for reporting
* Custom reconciliation period cut-off time
* Upper and lower limit ISO range for POS configuration
Refer to the Verifone Petroleum and C-Store Integrated Partners webpage for a list of approved Loyalty Partners and their contact information.
### Configuration Client setup
#### **POS Configuration**
1. From the Configuration Client, go to: Payment Controller > POS Configuration.
2. Select the **POS** tab.
3. Configure the Batch, Loyalty, and Misc parameters.
| Value | Description |
| ------------------ | ------------------------------------------------------------------------------------------------------------------ |
| Batch | |
| Batch Close Period |
Determines when the batch is closed.
Period 1: close shift.
Period 2: close daily.
|
| Loyalty | |
| Value | Description |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Loyalty Enabled | Loyalty Enabled is selected and uneditable if any of the Loyalty Programs in **Configuration Client > Payment Controller > EPS Configuration > PCATS Loyalty Configuration** is enabled. Loyalty Enabled is disabled and uneditable if none of the Loyalty Programs in **Configuration Client > Payment Controller > EPS Configuration > PCATS Loyalty Configuration** is enabled. |
| Value | Description |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Multiple Loyalty Discounts in same Transaction | Enables multiple loyalty discounts in the same transaction. |
| Auth on Total |
Enables loyalty messages to be sent to EPS when the \*\*\[Total]\*\*key is pressed.
If the \_Auth On Total\_option is enabled:
–The PCATS Loyalty Discount drops the item price down to $0.
–The system prompts for loyalty and authorizes it before the payment is tendered.
If the \_Auth on Total\_is not enabled:
–When an item is tendered with CASH, the system prompts for loyalty and determines the payment amount. The customer applies discount points for the item, and the sale total drops to $0 with an amount paid.
When \[TOTAL] is selected, the system prompts for loyalty and calculates the payment amount based on the loyalty response zero dollars. It does not require a tendered amount to complete the sale.
|
| Force Cash Receipt | Sets cash receipt to print. |
| EPS PPG precedes POS PPG: | Enables EPS Loyalty Price Per Gallon (PPG) discounts to be stacked before the POP PPG discount. |
| Misc | |
| Message Display Duration | Sets the maximum time (in seconds) an auto-hide message will remain on the screen. |
| Print Customer Copy | Enables printing a customer receipt from the original transaction. |
4. Select **Save** to accept, or **Cancel** to exit without saving.
5. To apply new settings, go to: Configuration Client > Tools > Refresh Configuration.
#### **EPS Global Configuration**
1. From the Configuration Client, go to: Payment Controller > EPS Configuration > EPS Global Configuration.
2. Select the **Loyalty** tab.
**Configure the Loyalty Configuration parameters:**
| Value | Description |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enable Alternate ID | Enables an Alternate ID. |
| Journal Loyalty ID to POS | Enables the Journal Loyalty ID to POS. |
| Use Long Text For Indoor Prompts | Enables the use of long text prompts at the DCR to more clearly provide prompts for newer programs.  |
| Prompt for Loyalty after Payment | Enables the prompt for loyalty after payment. |
| Send reward prompt to Cashier | Enables the cashier to answer the PIN pad prompt from the POS if the customer hands the cash and leaves without responding on the PIN pad. |
| Prompt for rewards only on fuel | Prompts for loyalty rewards only on fuel. |
| Display Host Messages | Enables the cashier to see loyalty messages from the host. |
| Reward Prompt Timeout (In Seconds) | Timeout value (seconds) for the prompt: “Reward customer? \[Yes/No].” |
Select **Save** to accept, or **Cancel** to exit without saving.
To apply new settings, go to: **Configuration Client > Tools > Refresh Configuration**.
#### **Loyalty Program Configuration**
From the Configuration Client, go to: Payment Controller > EPS Configuration > PCATS Loyalty Configuration.
The Loyalty Configuration form displays for the PCATS selected.
{% hint style="info" %}
Edits in PCATS Loyalty Configuration require a one-time password (OTP).
{% endhint %}
**Configure the Network, Communication and Reconciliation Period parameters:**
| Value | Description |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Network | |
| FEP Enabled | Enables the loyalty program. |
| Dealer ID | Sets the Dealer ID provided by the network. |
| Program Name | Sets the Program ID for the loyalty program. |
| Loyalty Offline Receipt Message | Sets the loyalty offline receipt message |
| Enable Barcode Scan | Enables a Barcode Scanning for the related FEP. The flag default is disabled. |
|
Note: This flag must be enabled for Bar Code Scanning on the related FEP.
| |
| Enable Card Download from Host | Enables the Loyalty Card Table Download that allows the Loyalty Host to send down card table entries. The flag default is disabled. |
|
Note: If this flag is disabled at a later date, the loyalty cards that were downloaded from the Host will be removed.
| |
| Display Loyalty FEP Offline to Hybrid Cards | Enables Loyalty FEP Offline Prompt for Hybrid Cards. |
| Prompt for Inside Transactions | Enable for multiple PCATS Loyalty Programs to prompt inside. |
| Prompt for Outside Transactions | Enable for multiple PCATS Loyalty Programs to prompt outside. |
| Communication Options | |
| Mode | Select **\[IP]** as the communication mode. |
| IP Address (IPv4 Format) | Enter **\[IP Address]** of the Loyaly Host. |
|
Note: Contact the Loyalty Host to provide the host IP address and port.
| |
| Port | Enter the Primary Host **\[Port].** |
| Value | Description |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enable TLS | Enables the use of a secure Transport Layer Security (TLS) connection to the loyalty host. When TLS is used, data is encrypted over the communication line. |
| Heartbeat Timer | Sets the interval in seconds between network status checks from the EPS to the Loyalty Host. |
| Reconciliation Period | |
| Custom Reconciliation Period Enabled | Enables the custom reconciliation period for reporting. |
| Custom Reconciliation Period Time | Cut-off time for custom reconciliation periods. |
Select **Save** to accept, or **Cancel** to exit without saving.
To apply new settings, go to: **Configuration Client > Tools > Refresh Configuration**.
#### **Loyalty Card Configuration**
Loyalty cards include both *Mag-Stripe* (swiping) and *Bar Code* (scanning) for encoded account information.
| Value | Description |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Mag-Stripe | Account information is encoded in a magnetic stripe on the back of the loyalty card. |
| Standard Bar Code | Data is encoded in a bar code situated on the product (i.e., a coke can or candy bar wrapper). |
|
Note: The Enable Bar Code Scan flag must be selected for the related FEP to enable bar code scanning. See Loyalty Program Configuration for the related FEP.
| |
| Value | Description |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| GS-128 Bar Codes |
Account information is encoded on \_both\_a magnetic stripe and a bar code on the back of the loyalty card. The loyalty card bar code is also encoded with 8018 in front of the account number.
The GS-128 loyalty card has both a \_mag-stripe\_and a bar code, and must have two entries in the Loyalty Card Configuration:
•once as mag-stripe entry
•once as bar code entry
|
|
Note: The Enable Bar Code Scan flag must be selected for the related FEP to enable barcode scanning. See Loyalty Program Configuration for the related FEP. See the parameter table below for Mag-Stripe, Standard Bar Code and GS-128 Bar Code loyalty card configuration details.
| |
From the Configuration Client, go to: **Payment Controller > EPS Configuration > Loyalty Card Configuration**.
Select the \[Loyalty Card Configuration] tab..
1. Select **\[Add]** to configure a Loyalty Card.
2. Configure the Loyalty Card Information parameters:
| Value | Definition | Mag Stripe | Standard Bar Code | GS-128 Bar Code |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Card Information** | | | | |
| Card Table Index | Index entry in the card table. | Yes | Yes | Yes |
| Card Abbreviation | Sets a two digit abbreviation for the card. | Yes | Yes | Yes |
| Card Name | Name given to identify this entry. | Yes | Yes | Yes |
| Lower ISO | Sets the lower value of the card (bin) range. The entered card number must be greater than or equal to this number to match the table entry. | The first six digits of the card number. | The first six digits of the bar code. | 8018 is a special application ID and is required as the first four digits of the Lower ISO range followed by the first two digits of the bar code. |
| Upper ISO | Sets the upper value of the card (bin) range. The entered card number must be less than or equal to this number to match the table entry. | Same as the lower ISO or ending range value. | Same as the lower ISO or ending range value. | Same as the lower ISO or ending range value. |
| Pan Length | Sets the number of digits to be used with the card. | 16 digits | 12 digits | 22 digits |
| Card Enabled | Enables the loyalty card. | Yes | Yes | Yes |
| Accept Track 1 |
Allows a Track 1 entry.
Note: Either track 1 or 2 needs to be selected.
| Required to accept track 1 data. | No | Not required for the bar code entry. Either track 1 or 2 (or both) for the mag- stripe entry. |
| Accept Track2 |
Allows a Track 2 entry.
Note: Either track 1 or 2 needs to be selected.
| Required to accept track 2 data. | No | Not required for the bar code entry. Either track 1 or 2 (or both) for the mag- stripe entry. |
| Value | Definition | Mag Stripe | Standard Bar Code | GS-128 Bar Code |
| ------------------- | ------------------------------- | ---------- | ----------------- | ------------------------------------------------------------------ |
| Accept Manual Entry | Sets manual entry for this card | Optional | Must be enabled. | Must be enabled for bar code entry. Optional for mag-stripe entry. |
| Hybrid Card | Sets the card as a hybrid card. | Optional | Optional | Optional for both bar code and mag-stripe. |
1. Click \[Edit] to select the supported FEPs. The Supported FEPs pop window displays.
2. Select the FEP(s) that should accept this loyalty card.
{% hint style="info" %}
One loyalty card can be configured to multiple FEPs.
{% endhint %}
3. Click **Done** to save or **Cancel** to exit without saving.
4. Select **Save** or **Cancel** to exit without saving changes.
5. To apply new settings, go to: **Configuration Client > Tools > Refresh Configuration**.
**Loyalty Card Configuration: Example #1**
*GS-128 Loyalty Card -* first entry configured for the **Bar Code** scan based on the sample below:
**Loyalty Card Configuration: Example #2**
GS-128 Loyalty Card - second entry configured for the **Mag-Stripe**swipe based on the sample below:
#### **Loyalty Card Configuration using a 10-Digit Phone Number**
This method configures the site if they are using a 10-digit phone number for loyalty rewards.
From the Configuration Client, go to: **Payment Controller > EPS Configuration > Loyalty Card Configuration**.
Select the **\[Loyalty Card Configuration]** tab.
Select **\[Add]** to configure a Loyalty Card.
Configure the Loyalty Card Information parameters for a 10-digit phone number:
| Value | Definition | 10-Digit Phone Number |
| -------------------- | --------------------------------------------- | --------------------- |
| **Card Information** | | |
| Card Table Index | Index entry in the card table. | Yes |
| Card Abbreviation | Sets a two-digit abbreviation for the card. | Yes |
| Card Name | Name given to identify this entry. | Yes |
| Lower ISO | Sets the lower value of the card (bin) range. | Enter ‘000’. |
| Upper ISO | Sets the upper value of the card (bin) range. | Enter ‘9999’. |
| Value | Definition | 10-Digit Phone Number |
| ------------------- | --------------------------------------------------- | ---------------------------------------- |
| Pan Length | Sets the number of digits to be used with the card. | 10-digits |
| Card Enabled | Enables the loyalty card. | Yes |
| Accept Track1 | Allows a Track 1 entry. | Not required for the phone number entry. |
| Accept Track2 | Allows a Track 2 entry. | Not required for the phone number entry. |
| Accept Manual Entry | Sets manual entry for this card | Must be enabled for phone number entry. |
| Hybrid Card | Sets the card as a hybrid card. | Not required for the phone number entry. |
1. Click **\[Edit]** to select the supported FEPs. The Supported FEPs pop window displays.
2. Select the FEP(s) that should accept this loyalty card.
{% hint style="info" %}
One loyalty card can be configured to multiple FEPs.
{% endhint %}
3. Click **Done** to save or **Cancel** to exit without saving.
4. Select **Save** or **Cancel** to exit without saving changes.
5. To apply new settings, go to: Configuration Client > Tools > Refresh Configuration.
## Using EPS loyalty
Loyalty sales allow the processing and redemption of loyalty transactions both inside, at the POS, and outside at the DCRs.
### EPS loyalty attributes
* Sites can enable both POP Discount and loyalty, but a customer can receive only one discount per transaction.
* After the loyalty card is swiped, VOID LINE and ERROR CORR cannot be used. Use VOID TICKET instead.
* If the network denies the request, a denial message displays. The transaction continues as usual.
* The POS updates loyalty report totals after each transaction.
### Loyalty sales functions
#### Inside EPS loyalty sales
* Inside Price Per Gallon Loyalty Sale (Pre-Pay)
* Inside Ticket-Level Loyalty Sale (Post-Pay)
* Loyalty Outside Pay Inside
* Merchandise Only Inside Loyalty Sale
#### Outside EPS loyalty sale
* Outside Price Per Gallon Loyalty Sale
* Outside Ticket-Level Loyalty Sale
#### **Inside EPS Loyalty Sales**
The customer or host may authorize a loyalty discount during an inside loyalty sales transaction. The customer can be given discounts as well as be prompted to accept a discount depending on the host settings.
**Inside Price Per Gallon (PPG) Loyalty Sale (Pre-Pay) Example**
The customer went inside the store, swiped their loyalty card, and prepaid for the purchase.
The dispenser was preset for the purchase amount at the discounted PPG. Fuel was dispensed for the prepaid value of fuel at the discounted PPG.
{% hint style="info" %}
The customer can authorize a discount during an inside loyalty sale if the loyalty host provides an optional discount prompt.
{% endhint %}
**Pre-Pay Steps**
{% hint style="info" %}
If Multiple Loyalty is configured, the customer may be prompted for additional cards. They can swipe the next card, select a program, or press **I’m Done**.
{% endhint %}
1. Enter the **amount**.
2. Select the **method of payment**.
3. Swipe/scan the loyalty card (or manually enter the loyalty account number).
4. Select the **fuel product**.
5. Tender and complete the sale.
6. The receipt prints showing the pre-pay amount and fueling point.
**Inside Ticket-Level Loyalty Sale (Post-Pay) Example**
The customer pulled up to a fueling position outside and pressed **Pay Inside** at the DCR. After fueling completed, the customer went inside and swiped their loyalty card, then paid.
Since this transaction began outside and was completed inside, the loyalty card was not swiped prior to fueling, and no PPG discount was given. However, the host did issue a transaction level EPS Loyalty Discount for the sale.
{% hint style="info" %}
*The information printed on their receipt may vary depending on the loyalty program in place.*
{% endhint %}
**Post-Pay Steps**
{% hint style="info" %}
If Multiple Loyalty is configured, the customer may be prompted for additional cards. They can swipe the next card, select a program, or press **I’m Done**.
{% endhint %}
1. Enter the sales item(s).
2. Press **Total**.
3. Swipe/scan the loyalty/payment card, or manually enter the card account number.
4. If the Auth on Total Key is enabled, the information is sent to the network and the discount is applied to adjust the ticket balance.
5. If the Auth on Total Key is not enabled, the discount is not applied until after the MOP is selected.
6. Tender and complete the sale.
7. The receipt prints displaying the loyalty discount amount applied to the ticket and any other messages from the Loyalty Host.
**Loyalty Outside Pay Inside Example**
The customer swiped the loyalty card at the DCR and received a PPG discount. The customer then selected to pay inside.
**Pay Inside Steps**
{% hint style="info" %}
If Multiple Loyalty is configured, the customer may be prompted for additional cards. They can swipe the next card, select a program, or press **I’m Done**.
{% endhint %}
1. Enter the sales item(s).
2. Press **Total**.
3. If the Auth on Total Key is enabled, the information is sent to the network and the discount is applied to adjust the ticket balance.
4. If the Auth on Total Key is not enabled, the discount is not applied until after the MOP is selected.
5. Tender and complete the sale.
6. The receipt prints displaying the loyalty discount amount applied to the ticket and any other messages from the Loyalty Host.
**Merchandise Only Inside Loyalty Sale Example**
The customer went inside and purchased several items. The customer swiped the loyalty card and received the appropriate line item or ticket level discount from the host.
{% hint style="info" %}
If Multiple Loyalty is configured, the customer may be prompted for additional cards. They can swipe the next card, select a program, or press **I’m Done**.
{% endhint %}
1. Enter the sales item(s).
2. Press **Total**.
3. If the Auth on Total Key is enabled, the information is sent to the network and the discount is applied to adjust the ticket balance.
4. If the Auth on Total Key is not enabled, the discount is not applied until after the MOP is selected.
5. Tender and complete the sale.
6. The receipt prints displaying the loyalty discount amount applied to the ticket and any other messages from the Loyalty Host.
**Outside EPS Loyalty Sales**
The customer can authorize a loyalty discount during an outside loyalty sale. If needed, loyalty account numbers can be entered manually at the DCR by selecting the **Loyalty** softkey.
**Outside Price Per Gallon Loyalty Sale Example**
The customer pulled to a fueling position outside, swiped their loyalty card, chose to use an available PPG discount and pay outside at the DCR. The dispenser adjusted the PPG to the discounted amount. Fuel was dispensed and paid for at the discounted PPG.
{% hint style="info" %}
*The information printed on their receipt may vary depending on the loyalty program in place.*
{% endhint %}
{% hint style="info" %}
If Multiple Loyalty is configured, the customer may be prompted for additional cards. They can swipe the next card, select a program, or press **I’m Done**.
{% endhint %}
1. The customer swipes the loyalty card at the DCR.
2. The loyalty network asks the customer if they want the discount.
3. The loyalty transaction is sent to the loyalty network.
4. The loyalty network replies with a text message from the host and a price per gallon discount off the purchase.
5. The customer swipes the payment card.
6. The receipt prints showing the discounted PPG amount and any host message.
**Outside Ticket-Level Loyalty Sale Example**
The customer pulled up to a fueling position and pressed **Pay Outside** at the DCR. After fueling completed, the customer swiped their loyalty card and then completed payment.
{% hint style="info" %}
*The information printed on their receipt may vary depending on the loyalty program in place.*
{% endhint %}
{% hint style="info" %}
If Multiple Loyalty is configured, the customer may be prompted for additional cards. They can swipe the next card, select a program, or press **I’m Done**.
{% endhint %}
1. The customer swipes the loyalty card at the DCR.
2. The loyalty transaction is sent to the loyalty network.
3. The loyalty network replies with a host message and a ticket-level discount.
4. The customer swipes the payment card.
5. The receipt prints displaying the ticket-level discount.
#### Cashier Option to Cancel Out of Loyalty Prompt
From Verifone Commander Release 56.01, added **YES**and **NO**keys to the Loyalty Auth prompt. Pressing the NO prompt will abort the PIN pad prompt.
This feature is focused on addressing the issue of cashier control over the PIN pad when a site is in customer-facing mode. This solves scenarios where customers walk in, inform the cashier of their pump number, drop money on the counter, and leave. These customers are unaware of any necessary actions on the PIN pad. Cashiers need to reach over to cancel loyalty prompts or even walk around to the PIN pad. This inconvenience causes a significant challenge and lacks intuitiveness.
## Reporting
### EPS Reports from the POS Terminal
To access EPS Reports from the POS Terminal, go to: **CSR Func > Network Menu**.
{% hint style="warning" %}
Some reports contain sensitive information. Set POS security levels to limit report access.
{% endhint %}
Select the Report Types from the POS Network Menu:
#### EPS Network and Secure Reports
The EPS Network Reports are specific to a particular host network and can vary across customer implementations.
**EPS Loyalty Reports**
Below are samples of the EPS Loyalty Reports.
Based on the parameter file settings, the account number may be masked.
{% hint style="warning" %}
*Because of the sensitive nature of the data included in Loyalty Detail Reports, it is critical that proper security levels be set for report access.*
{% endhint %}
**Terminal Batch Loyalty Detail Report**
The Terminal Batch Loyalty Detail Report is requested by terminal batch number.
**Report Details:**
**TITLE: Terminal Batch Loyalty Detail Report**
• DLR #: Dealer identification number.
• PRINTED: Date and time the report printed.
– MM/DD/YY: Date in month, date year format.
–HH:MM:SS: Time in hour, minutes, and seconds.
• WORKSTATION ID: Workstation identification number.
• TERMINAL BATCH: Terminal batch number.
• LOYALTY HOST: Loyalty host name.
–ACCOUNT NO: Account number.
–TOTAL: Total transaction amount.
–DISCOUNT: Transaction discount applied to the transaction.
• SUMMARY DISCOUNTS FOR ALL
LOYALTY HOSTS: Displays the summary of discounts applied for all loyalty hosts in a batch transaction.
–TICKET TOTAL: Total amount in a batch transaction.
–DISCOUNT TOTAL: Total discount in a batch transaction.
**Loyalty Discounts by Type Report**
The Loyalty Discounts by Type Report contains a summary, and grand totals for all PPG, transaction-level, and item-level discounts given during the selected terminal batch period.
**Report Details:**
**TITLE: Loyalty Discounts By Type Report**
• DLR #: Dealer identification number.
• PRINTED: Date and time the report printed.
–MM/DD/YY: Date in month, date year format.
–HH:MM:SS: Time in hour, minutes, and seconds.
• TERMINAL BATCH: Terminal batch number.
• PPU DISC: PPU Discount in a transaction.
• TICKET DISC: Total discount in a transaction.
• ITEM DISC: Discount by item.
• TOTAL $: Total amount in dollars.
**Loyalty PPU Totals by Grade Report**
The Loyalty PPU Totals by Grade Report provides the total of network loyalty discounts taken by fuel grade through the EPS. The report is requested by terminal batch number.
The total number of discounted fuel transactions are included in the report.
For fuel sales with loyalty, the report will contain a list of fuel product codes sold, along with the total volume by product code and the total dollar amount of discounts by product code.
**Report Details:**
**TITLE: Loyalty PPU Totals By Grade Report**
• DLR #: Dealer identification number.
• PRINTED: Date and time the report printed
–MM/DD/YY: date in month, date year format.
–HH:MM:SS: Time in hour, minutes, and seconds.
• TERMINAL BATCH: Terminal batch number.
• GRADE: Type of fuel grade.
• COUNT: Count.
• VOLUME: Total volume of fuel dispensed.
• DISCOUNT $: Discount in dollars.
**Loyalty PPU Transaction Detail Report**
The Loyalty PPU Transaction Detail Report contains information about the entire fuel sale with a Loyalty PPU discount. This report is sorted on transaction date and time and is requested by Terminal Batch Number.
For each sale, the report contains the date and time, fueling position, grade, original price as reported by POS, PPU discount amount, volume, total dollar amount of the discount, total amount of the fuel sale, and the loyalty card number.
**Report Details:**
**TITLE: Loyalty PPU Transaction Detail Report**
• DLR #: Dealer identification number.
• PRINTED: Report print date and time.
–MM/DD/YY: Date in month, date year format.
–HH:MM:SS: Time in hour, minutes, and seconds.
• TERMINAL BATCH: Terminal batch number.
**Heading**
–DATE: Transaction date.
–TIME: Transaction time.
–MEMBER ID: Loyalty card number.
–PUMP#: Pump number.
–GRADE: Fuel grade.
–STREET-PRICE: Original fuel price.
–FUELED PRICE: Discount fuel price.
–PPU DISC: PPU discount.
–VOLUME: Volume of fuel dispensed.
–TOTAL DISC: Total discounts applied.
–TOTAL SALE: Total transaction amount.
• TRANSACTIONS APPROVED BY FIRST LOYALTY HOST: List of individual transactions for the first loyalty host; data for each transaction.
• TOTAL VOLUME: Total volume of fuel sales for all transactions approved by this loyalty host in this terminal batch.
• TOTAL DISCOUNT: Total ticket discount for all transactions approved by this loyalty host in this terminal batch.
• TOTAL SALE AMOUNT: Total sale amount for all transactions approved by this loyalty host in this terminal batch.
**Loyalty Transactions Approved by Hosts (Terminal Batch Period) Report**
The Loyalty Transactions Approved by Host Report prints all loyalty transactions within a given terminal batch. To account for sites with multiple loyalty hosts, transactions are organized by the approving host
If a transaction is approved by multiple loyalty hosts, it will be included in each host’s list of transactions.
**Report Details:**
**TITLE: Loyalty Transactions Approved by Loyalty Hosts**
• DLR #: Dealer identification number.
• PRINTED: Date and time the report was printed.
– MM/DD/YY: Date in month, date year format.
– HH:MM:SS: Time in hour, minutes, and seconds.
• TERMINAL BATCH: Terminal batch number.
**Headings:**
–STAN: System traced audit number (Transaction ID), a unique key for a transaction.
–DATE/TIME: Date and time of transaction.
–LOYACT#: Last four digits of loyalty. account
–FUEL: Cost of fuel products purchased.
–VOLUME: Volume of fuel products purchased. Includes all fuel-specific discounts.
–NONFUEL: Includes any non-fuel transaction item, such as tax.
–TKT DISC: Total ticket level discount on transaction. Does not include line item or price per gallon discounts.
–SALEAMT: Total transaction as reported to user. Contains only ticket level discounts applied to this transaction.
–TRACE NUMBER: Sequence number assigned by loyalty host. If the sequence number is greater than 40 characters long, only the last 40 will be returned.
• FIRST LOYALTY HOST NAME: Program name of the loyalty host which displays the receipt.
• FIRST LOYALTY HOST DEALER NUMBER: Dealer ID for this site as reported to the First loyalty host.
•TRANSACTIONS APPROVED BY FIRST LOYALTY HOST: List of individual transactions for the first loyalty host; data for each transaction.
• TOTAL FUEL SALES: Total cost of fuel sales for all transactions approved by this loyalty host in this terminal batch.
• TOTAL FUEL VOLUME: Total volume of fuel sales for all transactions approved by this loyalty host in this terminal batch.
• TOTAL NONFUEL SALES: Total cost of non-fuel sales for all transactions approved by this loyalty host in this terminal batch.
• TOTAL TICKET DISCOUNT: Total ticket discount for all transactions approved by this loyalty host in this terminal batch.
• TOTAL SALE AMOUNT: Total sale amount for all transactions approved by this loyalty host in this terminal batch.
• Lines #13 - 20: Are the same as lines 5-12, but for a second possible loyalty host.
–As noted above, if a transaction is approved by more than one loyalty host, it will appear in this report for all hosts that approved it.
–The only difference between each of these entries is the sequence number provided by the loyalty host.
**Loyalty Transactions Approved by Host (Configured Period) Report**
The Loyalty Transactions Approved by Host Report prints all approved transactions within the reconciliation window. The report prints one host’s transactions at a time because in a multiple-loyalty environment, each loyalty host can be configured with its own reconciliation period.
Reporting one host at a time resolves any conflicts resulting from multiple reconciliation periods. The reconciliation period is not related to the terminal batch period, and is configured on a per-host basis.
When this report is generated, the POS will prompt the user for the host name to run the report on, and an index. This index refers to the period for which the report should be generated. Zero will represent the most recent period, one the period before that, and so on.
This report only details a single host; that host’s program name and dealer number will appear at the top of the report. The fields for ticket-level discount and sequence number will be added to each transaction, as well as appropriate headings.
The data contained in this report is similar to the Loyalty Transactions Approved by Hosts (Terminal Batch Period) Report. However, this report only contains data for a single loyalty host’s reconciliation period. The user will be prompted to select which host, and which reconciliation period index, prior to printing the report.
{% hint style="info" %}
*The total ticket discount amount in this report includes ticket level discounts from all sources, not just the selected loyalty host.*
{% endhint %}
**Report Details:**
**TITLE: Loyalty Transactions Approved by Host**
• DLR #: Dealer identification number.
• PRINTED: Date and time the report was printed.
–MM/DD/YY: Date in month, date year format.
–HH:MM:SS: Time in hour, minutes, and seconds.
• FIRST LOYALTY HOST NAME: Program name of the loyalty host which displays the receipt.
• FIRST LOYALTY HOST DEALER NUMBER: Dealer ID for this site as reported to the first loyalty host.
• RECONCILIATION PERIOD: Reconciliation period start/end date.
**Headings**
–STAN: System traced audit number (Transaction ID).
–DATE/TIME: Date and time of transaction.
–LOYACT#: Last four digits of loyalty account.
–FUEL: Cost of fuel products purchased.
–VOLUME: Includes all fuel-specific discounts and the volume of fuel products purchased.
–NONFUEL: Includes any non-fuel transaction item, such as tax.
–TKT DISC: Total ticket level discount on transaction. Does not include line item or price per gallon discounts.
–SALEAMT: Total transaction as reported to user. Contains only ticket level discounts applied to this transaction.
–TRACE NUMBER: Sequence number assigned by loyalty host. If the sequence number is greater than 40 characters long, only the last 40 will be returned.
•TRANSACTIONS APPROVED BY FIRST LOYALTY HOST: List of individual transactions for the first loyalty host; data for each transaction.
• TOTAL FUEL SALES: Total cost of fuel sales for all transactions approved by this loyalty host in this terminal batch.
• TOTAL FUEL VOLUME: Total volume of fuel sales for all transactions approved by this loyalty host in this terminal batch.
• TOTAL NONFUEL SALES: Total cost of non-fuel sales for all transactions approved by this loyalty host in this terminal batch.
• TOTAL TICKET DISCOUNT: Total ticket discount for all transactions approved by this loyalty host in this terminal batch.
• TOTAL SALE AMOUNT: Total sale amount for all transactions approved by this loyalty host in this terminal batch.
**Loyalty Discounts/Redemptions Report**
The Loyalty Discounts and Redemptions Report contains transactions with a ticket level discount granted by a loyalty host that falls within the selected reconciliation period.
This report will be changed to be printed on a per-host basis. The host program name and dealer number will be added to the report header. In addition, the sequence number assigned by the loyalty host will be added to each transaction entry.
**Report Details:**
• TITLE: Loyalty Discounts/ Redemptions.
• DLR #: Dealer identification number.
• PRINTED: Date and time the report was printed.
–MM/DD/YY: Date in month, date year format.
–HH:MM:SS: Time in hour, minutes, and seconds.
• FIRST LOYALTY HOST NAME:
Program name of the loyalty host which displays the receipt.
• FIRST LOYALTY HOST DEALER
NUMBER: Dealer ID for this site as reported to the First loyalty host.
• RECONCILIATION PERIOD: Reconciliation period start /end date.
**HEADINGS:**
– STAN: System traced audit number (Transaction ID), a unique key for a transaction.
–DATE/TIME: Date and time of the transaction.
–DISC: Ticket-level discount on transaction from this loyalty host.
–LOYACT#: Last four digits of loyalty account.
–TRACE NUMBER: Sequence number for this transaction assigned by the selected loyalty host.
• TRANSACTIONS APPROVED BY FIRST LOYALTY HOST: List of individual transactions for the first loyalty host; data for each transaction.
• TOTAL DISCOUNT: Total discount for all transactions in this reconciliation period.
## Glossary
The following terms and definitions will assist the reader with understanding the content of the Feature Reference.
| Term | Definition |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Bar Code | Data is encoded in a bar code situated on the product (for example, a candy wrapper). |
| DCR | Dispenser Card Reader. |
| EPS | Electronic Payment System. |
| FEP | Front End Processor. |
| GS-128 Loyalty Card | Account information is encoded on both a magnetic stripe and a bar code. The bar code is encoded with **8018** in front of the account number. GS-128 requires two Loyalty Card Configuration entries: one mag-stripe entry and one bar code entry. |
| IFSF | International Forecourt Standards Forum. |
| Loyalty Transaction | Any transaction approved by a loyalty host, including earn transactions and discount redemptions. |
| Mag-Stripe | Magnetic stripe on the back of the loyalty card encoded with account information. |
| MOP | Method of Payment. |
| PCATS | Petroleum Convenience Alliance for Technology Standards. |
| POP | Point of Purchase. |
| POS System | Includes POS terminals, site controller, and the EPS. |
| PPG | Price Per Gallon. |
| PPU | Price Per Unit. |
---
# Agent Instructions: 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:
```
GET https://docs.verifone.com/feature-references/feature-references/eps-loyalty.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.