# Mobile Payments

## Revision History

| Date       | Description                                                                  |
| ---------- | ---------------------------------------------------------------------------- |
| 10/21/2015 | Initial Documentation Release                                                |
| 05/25/2016 | Updated format. 2016 Copyright. Updated partner list.                        |
| 02/02/2017 | 2017 Copyright. Updated Reporting information.Updated network configuration. |
| 02/23/2017 | Update Mobile Payment Host Configuration.                                    |
| 05/01/2017 | Updated Reporting information.                                               |
| 07/19/2019 | Updated with Conexxus V2 updates.                                            |
| 01/04/2022 | Added the Mobile Payment (Collected by Host) Report.                         |
| 02/01/2024 | Updated document with branding changes.                                      |

## Overview

### Feature Description

The Mobile Payment feature reference provides information to setup a location to accept Mobile Payments at sites with a Verifone Commander.

This feature enables mobile payment, loyalty, delivery and transaction processing using a consumer's smart phone with a loaded Mobile Payment Application (MPA), a third party FEP vendor and a third party Mobile Payment Processing Application (MPPA) host.

### Hardware Requirements

* Verifone Commander with C18
* Verifone Commander with Topaz
* Verifone Commander with Ruby2
* RubyCi with Topaz
* RubyCi with Ruby2
* Commander 16 with Topaz
* Commander 16 with Ruby2

### Software Requirements

Verifone Commander base 39 and higher.

## Configuring Mobile Payments

### Prerequisites

The following list of requirements must be met by the location prior to Mobile Payment setup:

* The site must setup connectivity to the MPPA using either a VPN or the latest TLS protocol.
* Contact the Mobile Host Provider (MPPA) for site onboarding information.

### Site Onboarding Information

The following data fields should be obtained from the Mobile Application Partner and from the site for identifying the site on the mobile application.

#### Mobile Host Provided

* Adapter (Mobile payment APIs used by site system for communication with MPPA)
* Program Name (Program name as defined by MPPA)
* Authentication Type (Generate Token, Display Token, Scan Token, Enter Token)
* Host IP Address
* Port
* TLS Enabled
* Site Terminal ID
* Merchant ID
* Location ID
* Settlement Employee Number (**optional**)

#### Site Provided

* Phone: (store phone (xxx) xxx-xxxx)
* Welcome Message (may be left blank)

{% hint style="info" %}
The protocol has changed from SSL to TLS for better encryption and security.
{% endhint %}

### Configuring User Roles for Mobile Configuration and Reports

New installations will have default roles configured with all Mobile functions enabled, however, system upgrades will require additional user role setup.

{% hint style="info" %}
Any configuration import after a new install will require manually editing user roles for Mobile Payment function access.
{% endhint %}

{% stepper %}
{% step %}
From the Configuration Client, go to: **Security > Manage Users**.

The User Administration window displays.

![](/files/9cb021b99307a38e546c1746c9930c1edf8c9a79)
{% endstep %}

{% step %}
Select the \[Configure Roles] tab. In the Select Role pane, click to select the `<role>` to configure. Select \[Edit].

<figure><img src="/files/BPb35JEhkslGZcsOoTUE" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Scroll the Functions List and enable the following functions:

* umobilecfg - Update Mobile Configuration
* vmobileasloyaltyreport - View Mobile Above Site Loyalty Report
* vmobilecfg - View Mobile Configuration
* vmobilediagnostics - View Mobile Diagnostics
* vmobilehostlist - View Hosts List
* vmobilereportcategorylist - View Report's Category List
* vmobilereport - View Mobile Report
* vmobilereportlist - View Reports List

<figure><img src="/files/s7GK3GRAVeauJAkjtw1c" alt=""><figcaption></figcaption></figure>

![](/files/6ba873a2f2973099f11d63182b7bbf76542f3f2c)
{% endstep %}

{% step %}
Click \[Done].
{% endstep %}

{% step %}
Select \[Save] to accept, or \[Cancel] to exit without saving changes.
{% endstep %}

{% step %}
Log out and log back into the Configuration Client for changes to take effect.
{% endstep %}
{% endstepper %}

### Configure Mobile Method of Payment (MOP)

{% hint style="info" %}
New installations have a default Method of Payment and Code configured in the system to accept mobile payments.

If however, the system is upgraded, then the MOP and MOP Code must be configured.

If the site imported the mobile configuration using the Import and Export utility, either on a new install or upgrade, the Mobile MOP and Code will need to be configured manually.
{% endhint %}

{% stepper %}
{% step %}
From the Configuration Client, go to: Store Operations > Payment.

![](/files/af775f94f5a21f52ee9d048451fa5e2467874224)

The Payment Management window displays.

![](/files/76790d99cc63801f8b06568a5125687d41b4db2d)
{% endstep %}

{% step %}
From the Payment Management window, select the \[MOP] tab.

![](/files/fea3c046f278cfa2850a6c7adf526200d32bccdd)
{% endstep %}

{% step %}
Scroll down the `<Select MOP>` pane to an unconfigured position and configure the Mobile MOP parameters.

![](/files/063208c6c16fbb393fbc58c06efaba1d7209b9f2)

| Variable       | Value                                                  |
| -------------- | ------------------------------------------------------ |
| Name           | Enter: MOBILE                                          |
| MOP Code       | Select: 28 - MOBILE                                    |
| Minimum Amount | Indicates the minimum amount accepted <$0.00-9999.99>. |
| Maximum Amount | Indicates the maximum amount accepted <$0.00-9999.99>. |

| Variable             | Value                                                       |
| -------------------- | ----------------------------------------------------------- |
| Limit                | Alerts the cashier to the Mobile MOP limit <$0.00-9999.99>. |
| #Additional Receipts | Indicates how many additional receipts are required <0-3>.  |
| Tender Code          | Generic.                                                    |
| Tender Sub Code      | Generic.                                                    |
| {% endstep %}        |                                                             |

{% step %}
Select to enable additional Options parameters.

![](/files/a923be84ae6942674f497e277db122fda4e718da)

| Variable               | Value                                                                                       |
| ---------------------- | ------------------------------------------------------------------------------------------- |
| Force Safe Drop        | Enables a safe drop message (if the Limit value is not 0.00).                               |
| Tender Amount Required | Requires the clerk to enter an actual (counted) drawer amount before selecting this MOP.    |
| Allow Zero Entry       | Indicates a zero entry is allowed when entering a drawer amount.                            |
| Allow Refund           | Permits a Refund transaction to be tendered.                                                |
| Allow Safe Drop        | Allows a safe drop.                                                                         |
| Force Ticket Print     | Forces a receipt to be printed for transactions that includes this MOP.                     |
| Open Drawer On Sale    | Forces the cash drawer to open when a transaction includes this payment type.               |
| Cashier Report Prompt  | Prompts a cashier to enter the actual (counted) drawer amount when printing cashier report. |

| Variable                   | Value                                                                                                                                               |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Allow Without Sale         | Permits acceptance without purchase. For example, cashing in a winning lottery ticket or permitting a check to be cashed without a purchase.        |
| Allow Change               | Allows the cashier to make change when "amount > amount due" is selected. For example, if a check can be written for more than the purchase amount. |
| Allow Money Order Purchase | Permits a money order sale.                                                                                                                         |
| {% endstep %}              |                                                                                                                                                     |

{% step %}
Select \[Save] to accept, or \[Cancel] to exit without saving changes.

The setup of the Mobile Method of Payment is complete.

![](/files/daa0e33c409891c44a5f18da725bf2fab7ec605a)

{% hint style="info" %}
Log out and back in to all POS terminals after any setting modifications to allow these changes to take effect.
{% endhint %}
{% endstep %}
{% endstepper %}

### Mobile Payment Configuration

From the Configuration Client, go to: Payment Controller > Mobile Payment Configuration.

<figure><img src="/files/QN2gsd7Du11YyXf8xEMS" alt=""><figcaption></figcaption></figure>

The Mobile Payment Configuration window displays.

![](/files/7485c3df22f5108813133cf589a84d14a3f7e278)

The following tabs are available for selection:

* Site Mobile Configuration
* Host Configuration

#### Site Mobile Configuration

{% stepper %}
{% step %}
From the Mobile Configuration form, select the \[Site Mobile Configuration] tab.

![](/files/e9da6d288fefc47d59d99df0fdc6ee84e437d8be)
{% endstep %}

{% step %}
Select \[Accept Mobile Payments] to enable Mobile Payments.

<figure><img src="/files/TxWjl0vNwIxMYjdnMcZb" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Configure the following Site Configuration parameters.

<figure><img src="/files/7FySgHdq2tj0VDDMc4w5" alt=""><figcaption></figcaption></figure>

| Variable        | Value                                        |
| --------------- | -------------------------------------------- |
| Site Name       | The name of the site <20 characters>.        |
| Welcome Message | The site's welcome message <100 characters>. |
| {% endstep %}   |                                              |

{% step %}
Configure the following Miscellaneous Configuration parameters.

<figure><img src="/files/EiO5hCUfeWHZvedjZPvV" alt=""><figcaption></figcaption></figure>

| Variable           | Value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Data Storage Time  | The Data Storage Time for retention <0-30 days>.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| Site Address       | The site street address.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| Latitude/Longitude | The site GPS coordinates.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| Report / Format    | The combination of these fields are used to set the format type for each report from the report drop-down. The values are "Standard" and "Extended Authorization". The default format type would be "Standard" for all reports. In the Chevron distribution, the Mobile Terminal Batch Detail Report will default to Extended Authorization format. Standard: In this format max limit for authorization number is 14 digits and first 14 digits gets printed. Extended Authorization Format: Min limit for authorization number is 1; no upper limit. As of now this feature is applicable only for Mobile Terminal Batch Detail Report. |
| {% endstep %}      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |

{% step %}
Select \[Save] to accept, or \[Cancel] to exit without saving changes.
{% endstep %}
{% endstepper %}

#### Host Configuration

{% stepper %}
{% step %}
From the Mobile Payment Configuration window, select the \[Host Configuration] tab.

<figure><img src="/files/tuOHBTRg9kyNkUYk9BkJ" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click \[Add].

![](/files/c8c4cd3df1c27a32adc90ada322f8f7f5b6a28f6)
{% endstep %}

{% step %}
*Click to select \[Enable Host].*

<figure><img src="/files/LWuLEONw2OqK8DIY9Q0q" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Configure the Host Configuration parameters.

{% hint style="info" %}
*If Scan Token is selected as the Authentication Type, the scanner must be programmed with a prefix “P01”to correctly identify QR Codes.*
{% endhint %}

<figure><img src="/files/lxaHfUgDJbAovu00Jpny" alt=""><figcaption></figcaption></figure>

| Variable     | Value                                                                                                                                                                                                                                                      |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Adapter      | <p>The site Adapter Type:</p><ul><li>FDC Mobile - ConnectorSwitch adapter or outdoor transactions.</li><li>VFIMobile V1 - for Conexxus V1 standards</li><li>VFIMobile V2 - for Conexxus V2 standards</li><li>Local MPPA - for Shell Distribution</li></ul> |
| Program Name | The Program Name                                                                                                                                                                                                                                           |
| Merchant ID  | The Merchant ID number provided by the Mobile Payment Host.                                                                                                                                                                                                |

| Variable                   | Value                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication Type        | <p>The site Authentication Type:</p><ul><li>SCAN\_TOKEN: QR Code generated on the MPA is scanned using the POS scanner.</li><li>ENTER\_TOKEN: Customer or cashier enters token on the PIN pad.</li><li>DISPLAY\_TOKEN: Token for customer to enter is displayed on the PIN pad.</li><li>GENERATE\_TOKEN: Both Display\_Token and Generate\_Token display a token on the PIN pad to be scanned or entered for authenticating the transaction. If a site has different Mobile Payment programs configured with Generate\_Token authentication type for all, the customer is not prompted to select a mobile payment program during the transaction. After selecting mobile MOP, the PIN pad displays a QR Code instead of mobile payment program selection.</li></ul><p>If the Adapter type is 'FDC Mobile', then the field 'Authentication type' is disabled. This adapter allows only outdoor transactions.</p> |
| Site Terminal ID           | <p>ID number for the terminal received from the Mobile Payment Host.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Note: For Conexxus standards, Site\_terminal ID and Location ID are greyed out.</p></div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| Location ID                | <p>The Location ID provided by the Mobile Payment Host; identifies the site during the on boarding process.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Note: For Conexxus standards, Site\_terminal ID and Location ID are greyed out.</p></div>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| Store ID                   | The site Store ID number.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| Settlement Employee Number | The Settlement Employee Number provided by the Mobile Payment Host                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| Settlement Passcode        | The Settlement Passcode.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |

| Variable             | Value                                                                                                 |
| -------------------- | ----------------------------------------------------------------------------------------------------- |
| Phone Number         | The Site Phone Number.                                                                                |
| Send Loyalty Details | Enabling this flag will sends SLA/EPS loyalty program details to MPPA under Mobile Site Data Request. |
| {% endstep %}        |                                                                                                       |

{% step %}
Configure the Network Configuration parameters.

<figure><img src="/files/rC0wQNbvpJSvi6uwZ0WT" alt=""><figcaption></figcaption></figure>

| Variable                   | Value                                                                                                                                                                           |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Address                    | The Host IP or URL. (IPv4 format or http domain name).                                                                                                                          |
| Port                       | The communications port number.                                                                                                                                                 |
| SSL Enabled                | Enables Secure Socket Layer (SSL) for client/ host communications.                                                                                                              |
| Heartbeat Frequency / Unit | The time after which the Commander Site Controller pings the mobile program host to check connection. If the host is offline, the mobile host offline alarm appears on the POS. |
| {% endstep %}              |                                                                                                                                                                                 |

{% step %}
Configure the following Miscellaneous Configuration parameters.

<figure><img src="/files/EbZkFO8r14YOSQqvyU95" alt=""><figcaption></figcaption></figure>

| Variable                         | Value                                                                                                                                                                                                                                                                                                                                                               |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Outdoor PreAuthorization Timeout | The DCR Pre-Authorization timeout (in seconds).                                                                                                                                                                                                                                                                                                                     |
| Site Initiated Loyalty           | <p>The Site Initiated Loyalty setting for outdoor transactions:</p><ul><li>Never Allow Site Entered Loyalty - Allow only mobile loyalty.</li><li>Allow Site Entry i.e., Swiped Loyalty Card - Both swiped and mobile loyalties are honored.</li><li>Allow Site Entered Loyalty if no Mobile Loyalty - Allow swiped loyalty if there is no mobile loyalty.</li></ul> |
| {% endstep %}                    |                                                                                                                                                                                                                                                                                                                                                                     |

{% step %}
Select \[Save] to accept, or \[Cancel] to exit without saving changes.
{% endstep %}
{% endstepper %}

### Configure Loyalty Key on DCR for Using Mobile Payment

Following are the steps to configure loyalty for mobile payment if site has a loyalty program(s) enabled.

#### Configure Loyalty Key "REWARDS" on Dispensers with Graphics DCR

If site has already configured "Loyalty" soft key, replace it with "REWARDS" soft key type. This soft key has the functionalities of the "Loyalty" soft key type and also links mobile payment with loyalty. The soft key text can remain as "Loyalty".

On Commander Configuration Client, go to Forecourt > DCR Idle Screen.

Configure a soft key to "REWARDS" soft key type and not LOYALTY\_CARD\_SWIPE or LOYALTY\_MANUAL\_ENTRY. For more information on configuring soft keys, refer to the Verifone Commander User Reference.

<figure><img src="/files/SySfU3sAUV0NJAeWPhZX" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Do a Tools > Refresh Configuration and Forecourt > Initialization > DCR after the configuration changes.
{% endhint %}

#### Configure Loyalty Key on Dispensers with Non-Graphics DCR

On Configuration Client, go to Forecourt > DCR Keys. Select a numeric key which should work as loyalty key when dispenser is idle as shown below. In the example below numeric key 5 is used as loyalty key.

<figure><img src="/files/eZudWDPgNUnKshgn70sW" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Do a Tools > Refresh Configuration and Forecourt > Initialization > DCR after the configuration changes.
{% endhint %}

### Configure Site Address

The Dealer address details are used for displaying site information on the mobile application when a customer does a check-in through the mobile application.

From Configuration Client, go to: Payment Controller > EPS Configuration > EPS Global Configuration.

<figure><img src="/files/O7w57ZSJI4UECYjikkAR" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}
From the EPS Global Configuration window, select the \[EPS] tab.

<figure><img src="/files/xcLmBaRhNvEGrh7tjaUR" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Configure the Dealer parameters.

<figure><img src="/files/hGjZyUMpn6C5NYHxYCyg" alt=""><figcaption></figcaption></figure>

| Variable      | Value         |
| ------------- | ------------- |
| Site Name     | Dealer Name   |
| Address Line1 | Dealer Street |
| City          | Dealer City   |

| Variable      | Value           |
| ------------- | --------------- |
| State         | Dealer State    |
| Postal Code   | Dealer Zip Code |
| {% endstep %} |                 |

{% step %}
Select \[Save] to accept, or \[Cancel] to exit without saving changes.

{% hint style="info" %}
Log out and back in to all POS terminals after any setting modifications to allow these changes to take affect.
{% endhint %}
{% endstep %}
{% endstepper %}

### Local Area Network Configuration

{% stepper %}
{% step %}
From the Configuration Client, go to: Initial Setup > Local Area Network Configuration.

<figure><img src="/files/beM1pIxdVDYRtZ4x62U3" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Configure Device Specific Routes.**

Confirm the Controller is the device selected to configure.
{% endstep %}

{% step %}
Click \[New] in Device Specific Routes.

<figure><img src="/files/rUJVSD0DQ7PPMd5Yzoy9" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select the New Route Config Route Type: Host.

<figure><img src="/files/3AMoxpQfLJ581ryHJ4pT" alt="" width="290"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Enter the Device Specific Host Route Destination address provided by the Mobile Payment Host.

Enter the Gateway address; this will be the site's Payment Gateway address, as associated with the Isolated Payment NIC.

Enter the Netmask = 255.255.255.255.

Click \[Save] in the New Route Configuration dialog box.

<figure><img src="/files/igrwZA6tYt16Rmx08qM1" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
*Click \[Save] on the main form.*

<figure><img src="/files/iBxLsO84ze7NYMbWdekP" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Reboot the Verifone Commander to ensure proper network routing is uses for all devices.
{% endstep %}
{% endstepper %}

### Enabling Mobile Payment to Appear on Day Close Report

The Mobile Payment Report must be enabled to appear on the Daily Close Report print out.

{% stepper %}
{% step %}
From the Configuration Client, go to: Reporting > Report Configuration.

<figure><img src="/files/YrK1vuzHz7E3PpbnTwND" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Make sure 2-DAY is selected from the drop-down box in the Configure Group List section.

<figure><img src="/files/aZEMC9jrpS41Bafzr3GH" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click Edit in the Configure Group List section.

<figure><img src="/files/Xvs6IBLpuWiJXuRo2LqE" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Scroll down the list and select the Mobile Payment Report option.

<figure><img src="/files/c5VusA98CIBdlbMY4KiR" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click DONE.

<figure><img src="/files/vo7ubiNSSyeQAwGreHRY" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click SAVE.

<figure><img src="/files/1v7Hb09Ek6apW0UR4U1k" alt=""><figcaption></figcaption></figure>

After this configuration, the Mobile Payment Report, will be available as part of the information printed on the Day Close Report.

The report is also available as a selectable option in Report Navigator.
{% endstep %}
{% endstepper %}

## Using Mobile Payments

### Indoor Transactions

#### Pay at POS with Code Displayed on POP

In this use case, the Cashier initiates the payment transaction by requesting a dynamically generated token from the MPPA. The Customer is provided a transaction code to enter into the mobile application, thereby connecting to the transaction.

{% stepper %}
{% step %}
*Customer makes a purchase and tells the cashier that he wants to pay using his mobile app.*
{% endstep %}

{% step %}
The cashier selects "Mobile" MOP on the POS.
{% endstep %}

{% step %}
The Site Controller submits a request to the MPPA host for a transaction code.

{% hint style="info" %}
If multiple mobile hosts are configured at the site, then a host selection prompt appears on the POP device after Mobile MOP is selected.

If multiple mobile hosts are configured at the site, the Authentication Type should be Generate\_Token so that a host selection prompt does not appear on the POP device after Mobile MOP is selected.
{% endhint %}
{% endstep %}

{% step %}
The host responds with a transaction code which is displayed on the POP.

<figure><img src="/files/SZakP02bplzViaFYzjsF" alt="" width="347"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
The customer opens the mobile payment app on their phone, enters or scans the transaction code, which links to the transaction at the POS.
{% endstep %}

{% step %}
After successful code verification, the host authorizes the transaction.
{% endstep %}

{% step %}
On completion of the transaction, receipt details are sent to the MPPA and will be available for the customer to view on the mobile application.

{% hint style="info" %}
Receipt data sent to the MPPA is the same as the receipt being printed from the POS.
{% endhint %}
{% endstep %}
{% endstepper %}

#### Pay at POS with Code Displayed on Phone

In this use case, the Customer initiates the mobile payment transaction request. The MPA initiates the transaction to obtain a dynamically generated pre-authorization token from the MPPA. The token is displayed on the phone and used to complete the transaction at the POS.

{% stepper %}
{% step %}
Customer makes a purchase and tells the cashier that he wants to pay using his mobile app.
{% endstep %}

{% step %}
The cashier selects "Mobile" MOP on the POS.

{% hint style="info" %}
If multiple mobile hosts are configured at the site, then a host selection prompt appears on the POP device after Mobile MOP is selected.

If a site has different Mobile Payment programs configured with Generate\_Token authentication type for all, the customer is not prompted to select a mobile payment program during the transaction. After selecting mobile MOP, the PIN pad displays a QR Code instead of mobile payment program selection.
{% endhint %}

<figure><img src="/files/xcVdG3jZWJnGhAbbJA9f" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
The Customer initiates the mobile payment transaction request, and depending on the system host configuration, the mobile application will display either an alphanumeric string code or a QR code.

<figure><img src="/files/YyMLyFeRtVykbOpa5YHa" alt="" width="359"><figcaption></figcaption></figure>

If the MPA displays a string code, the customer enters the code on the POP.

If the MPA displays a QR code, the cashier scans the QR code.
{% endstep %}

{% step %}
After successful code verification, the host authorizes the transaction.
{% endstep %}

{% step %}
On completion of the transaction, receipt details are sent to the MPPA and will be available for the customer to view on the mobile application.

{% hint style="info" %}
Receipt data sent to the MPPA is the same as the receipt being printed from the POS.
{% endhint %}
{% endstep %}
{% endstepper %}

### Outdoor Transactions

#### Pay at Pump with Code Entry

In this use case, the customer initiates the transaction through the MPA by selecting an available pump at the site. The pump is reserved, and the customer is prompted to enter an authorization code at the DCR. The authorization code will be sent to customer's phone. After fueling, the sales amount is charged to the MPA's registered card.

{% stepper %}
{% step %}
The Customer opens the MPA and selects the PUMP to reserve.
{% endstep %}

{% step %}
An authorization code is sent to the customer's phone.
{% endstep %}

{% step %}
The DCR prompts the customer to enter the authorization code. On successful code validation, the PUMP will be armed.

<figure><img src="/files/CBIOM7DcUDz2YdvWMlkw" alt="" width="272"><figcaption></figcaption></figure>

{% hint style="info" %}
The pump is authorized only on code validation success. Authorization will fail if maximum retries are exhausted or if the Validation Code Prompt times out.
{% endhint %}
{% endstep %}

{% step %}
The Customer dispenses the fuel. Depending on the MPA, the customer is notified on their phone of the fueling start and stop.
{% endstep %}

{% step %}
On completion, the DCR prints the receipt. The sales amount is transmitted to the MPPA, the customer's card is charged, and a receipt copy is sent to the registered MPA account for transaction history.
{% endstep %}
{% endstepper %}

#### Pay at Pump without Code Entry

In this use case, the customer initiates the transaction through the MPA by selecting an available pump at the site. The pump is reserved and pre-authorized. After fueling, the sales amount is charged to the MPA's registered card.

{% stepper %}
{% step %}
The Customer opens the MPA and selects the PUMP to reserve and authorize.
{% endstep %}

{% step %}
The Customer dispenses the fuel. Depending on the MPA, the customer is notified on their phone of the fueling start and stop.

On completion, the DCR prints the receipt. The sales amount is transmitted to the MPPA, the customer's card is charged, and a receipt copy is sent to the registered MPA account for transaction history.
{% endstep %}
{% endstepper %}

## Reporting

Reports and reporting options are provided by and will vary with the associated Host provider. Sample reports are provided for example purposes only.

Mobile Reports are located on the POS terminal CSR Functions > Network Menu. Select \[Mobile Reports] from the POS Network Menu.

<figure><img src="/files/HurfqFamkUmZ5JLtSGNk" alt=""><figcaption></figcaption></figure>

Select an available Mobile Reports option, then follow the instructions on the Report screen to select from the provided reports.

![](/files/36a07aa91e9c9784dbda3d9527665698bad48a40)

### Mobile Settlement Report

![](/files/96bf393e9fa7eb59d3fa7133c7a4815548e9a176)

#### *Report Details*

**Header**

* HOST: Host name.
* Print Date: Date/Time of report.
* Period: Reporting Period.
* Merchant ID: Configured Merchant ID.
* Terminal ID: Configured Terminal ID.

**Terminal and Host Totals**

* CARD TYPE: Type of card used in the transaction (e.g., VISA, MASTERCARD).
* COUNT: The total number of sales for a card type.
* AMOUNT: The total sale amount for a card type.
* TERMINAL TOTAL: The Terminal Total of all card types.
* HOST TOTAL: The Host total for all card types.
* DIFF: The difference between terminal and host totals.

**Payment Type Totals**

* PAYMENT TYPE: Type of payment (e.g., CREDIT, DEBIT).
* COUNT: The total number of a payment type.
* AMOUNT: The total payment amount for a payment type.

**Exception Transactions**

Transactions that were pre-authorized by the host but later rejected during completion. These transactions need to be manually settled with the host.

* AUTH REF ID: The authorization reference id.
* GLOBAL TRAN ID: The transaction id.
* AMOUNT: The transaction amount.
* RESPCODE: Transaction decline response code.
* DATE/TIME: The transaction date and time.

**Pending Transactions**

Transactions that were pre-authorized by the host but are not yet completed.

* AUTH REF ID: The authorization reference id.
* GLOBAL TRAN ID: The transaction id.
* AMOUNT: The transaction amount.
* DATE/TIME: The transaction date and time.

**Discounted Transactions**

Some transactions are given host discounts based on the card type used in the transaction. These discounts are not reported as part of any POS or EPS reports.

* TRAN\_ID: Unique number given by the host to identify a transaction.
* DISC\_LABEL: Reason/description of the given discount.
* DISC\_AMOUNT: Total discount amount applied on the transaction.
* UNIT\_DISC: PPG discount qualified for the selected grade.
* DISC\_QUANTITY: Quantity of grade fuel dispensed by the customer which qualified for a discount

### Mobile Terminal Batch Detail Report

![](/files/af1d39da59251e58fce97c953e7eec8961b7d11d)

#### Report Details

**Header**

* Print Date: Date/Time of report
* Period: Reporting Period
* Mobile Host: Mobile Payment Host
* Merchant ID: Configured Merchant ID

**Transaction Totals**

* Account #: Masked card number.
* Type: OTHER.
* Auth #: Transaction authorization number.
* TOTAL: Transaction amount total.
* Sales Total: Summary total of all transaction amounts.
* Sales Adjust: Summary total of any adjusted transaction amounts.
* Batch Total: Adjusted sales amount.

### Above Site Loyalty Reports

#### *Terminal Batch Loyalty Summary Report*

Terminal Batch Loyalty Summary Report gives a summary of ASA loyalty discounts applied on Mobile transactions.

<figure><img src="/files/rm6u4wxuiNVB5AknA1bd" alt=""><figcaption></figcaption></figure>

#### Loyalty Discount By Type Report

Loyalty Discount by Type Report gives details about PPG, Ticket, Line items loyalty discounts given by MPPA.

![](/files/760b5e6eb42e84adf8d962238ce9b35f8093acf3)

#### Loyalty Grade Totals Report

Loyalty Grade Totals Report gives details about all ASA PPG discounts given by all configured mobile host programs.

![](/files/00c4e1e403c08c983a66f9f0067612664a49ca1a)

#### Loyalty Discount Detail Report

Loyalty Discount Detail Report gives you detail about all ASA discounts given by all configured mobile host programs.

![](/files/9e292c6b5b39706ca7c52df825b1db696b5de402)

### Above Site Mobile Report

#### Mobile Payment (Collected by Host) Report

*The Mobile Payment (Collected by Host) Report gives details about all ASA Mobile Payments based on card type collected by the Host. This report is printed from the CSR Functions > Reporting > Flash Reports Menu.*

<figure><img src="/files/XS3XNi10uhKzl3CzYMcG" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/qexJ2hzORZFFRt2nD11O" alt="" width="254"><figcaption></figcaption></figure>

## Troubleshooting

### Site Doesn't Display on Mobile Payment Application

{% stepper %}
{% step %}
Verify that site has Mobile Host connectivity.

* Ping the host from: POS Main Menu > Maintenance > Ping Test (site level)
* Ping the host from Verifone Commander as the VASC-level user MAINT using: Ping `<Mobile Host IP Address>`.
  {% endstep %}

{% step %}
If the site has connectivity, but does not appear on the mobile application, verify connectivity to the Mobile Host.

* Check the logs (/var/log/messages) to verify a site update request from Verifone Commander to the Mobile Host was successful
* If needed, contact mobile host provider.
  {% endstep %}

{% step %}
Confirm the Mobile Host Provide onboarding details were configured properly.
{% endstep %}
{% endstepper %}

### Site Settlement Failed

{% stepper %}
{% step %}
Verify that the settlement details (e.g., settlement employee number and settlement password) were entered in Mobile Host Configuration.

The settlement details must be the same as what was received from the Mobile Host Provider during the site onboarding process for Mobile Payment.
{% endstep %}

{% step %}
Contact the mobile host provider if the entered configuration details are correct.

{% hint style="info" %}
These attributes are specific to FDC Mobile and are not used by the VFIMobile adapter.
{% endhint %}
{% endstep %}
{% endstepper %}

### Pump Reserved but Authorization Failed

* The pump reservations are released after 3 minutes.

### Car Wash PLUs Not Displaying on Mobile Payment Application

{% stepper %}
{% step %}
From the Configuration Client, go to: Devices > Car Wash.

<figure><img src="/files/gt1PFFYD91nysGPKGICs" alt=""><figcaption></figcaption></figure>

The Car Wash Configuration window displays.

![](/files/5332cffe19885ebf61dd1da3d7eade6ebb5b9804)
{% endstep %}

{% step %}
Verify that all Car Wash PLUs are configured and enabled for Outdoor.
{% endstep %}
{% endstepper %}

### Pump Can't Authorize Mobile Payment Application

{% stepper %}
{% step %}
From the Configuration Client, go to: Store Operations > Payment.

<figure><img src="/files/MX1HCvPJOBOt2gjsK6B6" alt=""><figcaption></figcaption></figure>

The Payment Management window displays.

![](/files/32380aed0025a090e2e0f1d442ee647400acadcf)
{% endstep %}

{% step %}
Verify that the Mobile MOP is configured.
{% endstep %}
{% endstepper %}

### Disabling the Mobile Host

{% stepper %}
{% step %}
From the Configuration Client, go to: Payment Controller > Mobile Payment Configuration.

<figure><img src="/files/4tTTaWIq3J2t3eJjkFwN" alt=""><figcaption></figcaption></figure>

The Mobile Payment Configuration window displays.

<figure><img src="/files/jhjTxZvDiBHJbx7dwGKr" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select the \[Host Configuration] tab.
{% endstep %}

{% step %}
Deselect \[Enable Host].
{% endstep %}

{% step %}
Select \[Save] to accept, or \[Cancel] to exit without saving changes.

{% hint style="info" %}
After disabling the host, the POS displays an alarm "Host Disable in Progress." Verifone Commander will not accept new transactions until the Host Disabled alarm is cleared, once the settlement with MPPA completes.
{% endhint %}
{% endstep %}

{% step %}
To apply new settings, go to: Configuration Client > Tools > Refresh Configuration.

![](/files/dd6aa34524dba0e7726af83630e84d4c6b10e6cc)

{% hint style="info" %}
Log out and back in to all POS terminals after any setting modifications to allow these changes to take affect.
{% endhint %}
{% endstep %}
{% endstepper %}

## Appendix A - Terms

| Term           | Definition                                                                                                                                                                                                                                                                                                          |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API            | Application Programming Interface.                                                                                                                                                                                                                                                                                  |
| ASA            | Above Site Authorization - above site authorization is the scenario when MPPA talks to the PFEP to obtain an authorization outside of the Site System. The POS does not engage the EPS or PFEP for payment. The mobile authorization request is an unsolicited message from MPPA to the site system Mobile Service. |
| DCR            | Dispenser Card Reader.                                                                                                                                                                                                                                                                                              |
| EPS            | Electronic Payments System - a hardware/software application that processes payments thru a payment host or series of payment hosts.                                                                                                                                                                                |
| FCC            | Forecourt Controller - the controller that handles pump processing at the site.                                                                                                                                                                                                                                     |
| FEP            | Front End Processor - software process that resides on the EPS. The FEP is the front-end process for a particular host.                                                                                                                                                                                             |
| OPT            | Outdoor Payment Terminal - a device installed at a retail petroleum site to enable payment outdoors without direct intervention from a site operator.                                                                                                                                                               |
| POP            | Point of Payment.                                                                                                                                                                                                                                                                                                   |
| POS            | Point of Sale.                                                                                                                                                                                                                                                                                                      |
| PPG            | Price Per Gallon.                                                                                                                                                                                                                                                                                                   |
| PFEP           | Payment Front End Processor - the application or institution that the Site or MPPA uses for the processing of payments.                                                                                                                                                                                             |
| MD             | Mobile Device - the mobile device (e.g., smart phone) used by the customer to interface with the Mobile Payments Processing Application (host).                                                                                                                                                                     |
| Mobile Service | Mobile Service - a software program at the Site that facilitates the communication between the MPPA, the Site's System, the POS, and in some cases the PFEP.                                                                                                                                                        |

| Term | Definition                                                                                                                                                                                                                                                                                                                                                                                                                        |
| ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| MPA  | Mobile Payments Application - a software application downloaded by a customer to a mobile device to facilitate mobile payment transactions.                                                                                                                                                                                                                                                                                       |
| MPPA | Mobile Payments Processing Application - the application/host that facilitates the communication between the MPA on the mobile device, Site System, and at times the PFEP for purposes of mobile payments.                                                                                                                                                                                                                        |
| SLA  | Site Level Authorization - is the scenario when MPPA provide necessary details (Payment instrument) to site system so Mobile Service makes a card/payment request to EPS with those details to get authorization. EPS component will communicate with PFEP processor for authorization. MPPA does not engage PFEP for this use case. Authorization request is an unsolicited message from MPPA to the site system Mobile Service. |
| SSL  | Secure Socket Layer - is a standard security technology for establishing an encrypted link between a server and a client.                                                                                                                                                                                                                                                                                                         |
| UMTI | Unique Mobile Transaction Identifier - serves as a transaction identifier. It is expected that the UMTI will remain the same for all the messages exchanged for a single transaction.                                                                                                                                                                                                                                             |
| VPN  | Virtual Private Network.                                                                                                                                                                                                                                                                                                                                                                                                          |

## Appendix B - Partner Links

### FIS

[www.FISglobal.com](http://www.fisglobal.com/)

#### Contact Information

601 Riverside Avenue, Jacksonville, FL 32204\
904-438-6000\
E-Mail: <moreinfo@fisglobal.com>

### Gas Buddy

[www.GasBuddy.com](http://www.gasbuddy.com/)

#### Mailing Address

60 Canal St, Boston, MA 02109

**GasBuddy Mobile App**

[www.gasbuddy.com/App](http://www.gasbuddy.com/App)

### MShift, Inc.

[www.MShift.com](http://www.mshift.com/)

#### Contact Information

39899 Balentine Drive, Suite 235, Newark, CA 94560\
510-933-5901\
E-Mail: <info@mshift.com>

### Paydient

[www.Paydient.com](http://www.paydient.com/)

#### Contact Information

275 Grove St, Auburndale, MA 02466\
617-219-4200\
E-Mail: <info@paydiant.com>

### P97 Networks, Inc.

[www.P97.com](http://www.p97.com/)

#### Contact Information

10333 Richmond Avenue #250, Houston, TX 77042\
713-588-4200 (8:00 AM - 5:00 PM CST, Monday-Friday)\
E-mail: <support@p97.com>

#### Documentation

PetroZone Functions Supported by Mobile API: <http://p97.com/dox/PZE-UC006.pdf\\>
PetroZone Installation Reference for Mobile API: <http://p97.com/dox/DEL-INREF016.pdf>

### ZipLine

[www.ZipLine.biz](http://www.zipline.biz/)

#### Contact Information

4171 West Hillsboro Boulevard, Suite 5, Coconut Creek, FL 33073 954-449-9540\
E-mail: <Info@zipline.biz>


---

# 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/mobile-payments.md?ask=<question>
```

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.