> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/features-and-products-references/incomm/configuring-incomm.md).
# Configuring InComm
Configuring the InComm feature encompasses:
* Enabling or disabling InComm transaction processing.
* Setting departments and PLUs for selling InComm products.
* Enabling or disabling each transaction type.
* Determining if validation is required for each transaction type.
* Specifying the Ticket Security Level for each transaction type.
* Creating PLUs and departments as part of the initial configuration.
### InComm Departments
Before you begin the actual InComm configuration, you must set up departments for each transaction type. This configuration includes:
* A unique product code with a corresponding transaction type assigned to each department.
* The Product Codes to be used for each transaction type.
* These departments can then be linked to networks using the new Electronic Payment Server (EPS) Prepaid Configuration applet.
See the table below for a list of departments and product codes.
Department Name
Product Code
Pin Activate Prepaid Card
560
Enable Device Or Handset Unlock
562
Third Party Prepaid Card Activate
564
Third Party Prepaid Card Reload
565
Financial Prepaid Card Activate
566
Proprietary Prepaid Card Activate
568
Proprietary Prepaid Card Reload
569
General Purpose Activate
570
General Purpose Reloadable
571
Real Time Recharge
572
Wireless Real Time Recharge
573
* There could be multiple departments for the same transaction type.
* Each department can be assigned a fee.
* PLUs representing swipe reload products need to be linked to Swipe Reload department.
* If a fee is specified for Swipe Reload department, the fee is applied to all the swipe reload transactions.
* There is also an option to specify fee for a PLU. If a fee is specified for a PLU, it takes precedence over the department fee.
* To setup a general purpose reloadable card that prompts the customer to swipe the card on PIN pad after completing payment, do the following:
* Create a new department and assign the general purpose reloadable card product code.
* Create an Open PLU assigned to the gift card department for prompting recharge amount.
* For easy access create a softkey for the Department and the PLU.
### InComm Card Types, Transaction Types, and Product Codes
| Card Type | Transaction Type | Department and Product Code |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | --------------------------------------- |
| Fast Card | Card Activation | General Purpose Activate (570) |
| Fast Card | Wireless Recharge | Wireless Recharge (573) |
| Fast Card | Card Deactivation | General Purpose Activate (570) |
| Fast PIN | Fast PIN Sale | PIN Activate Prepaid Card (560) |
| Fast PIN | Fast PIN Return | PIN Activate Prepaid Card (560) |
| Third Party Gift Cards | Card Activation | Third Party Prepaid Card Activate (564) |
| Third Party Gift Cards | Card Deactivation | Third Party Prepaid Card Activate (564) |
| Closed Loop Gift Cards | Card Activation | Proprietary Prepaid Card Activate (568) |
| Closed Loop Gift Cards | Card Deactivation | Proprietary Prepaid Card Activate (568) |
| Closed Loop Gift Cards | Recharge | Proprietary Prepaid Card Reload (569) |
| Financial Gift Cards | Card Activation | Financial Prepaid Card Activate (566) |
| Financial Gift Cards | Card Deactivation | Financial Prepaid Card Activate (566) |
| General Purpose Reloadable Cards | Card Activation | General Purpose Activate (570) |
| General Purpose Reloadable Cards | Card Deactivation | General Purpose Activate (570) |
| General Purpose Reloadable Cards | Swipe Reload | General Purpose Reloadable (571) |
| Real Time Recharge | Real Time Recharge | Real Time Recharge (572) |
| Product Authorization | Enable Device | Enable Device / Handset Unlock (562) |
| Product Authorization | Disable Device | Enable Device / Handset Unlock (562) |
|
Balance Inquiry, Redemption, Card Redemption lock, Card Redemption Unlock, and Store credit transactions are excluded as these are not linked to product codes. These transactions (tender transactions) are supported for InComm Closed Loop cards only.
| | |
### Configuring Departments
{% stepper %}
{% step %}
**Configuration Client**
In Configuration Client, go to **Store Operations > Merchandise**. The Merchandise Configuration window appears.
{% endstep %}
{% step %}
**Departments**
Select the **\[Departments]** tab. The Department form appears.
{% endstep %}
{% step %}
**Add or Delete**
Select **\[Add]** to set up an InComm Department or **Delete** to delete an existing department.
{% endstep %}
{% step %}
**Configure the Department**
Configure the Department parameters as listed in the table below.
| Value | Description |
| ------------ | -------------------------------------------------------------- |
| Department | |
| Number | Sets the new department number. |
| Name | Describes the department. |
| Min. Amount | Sets the minimum allowable dollar amount for a line item sale. |
| Max. Amount | Sets the maximum allowable dollar amount for a line item sale. |
| Product Code | Set by the network. Categorizes the products sold. |
| Value | Description |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
|
If a PLU and a department have different codes, the product code assigned to the PLU overrides but only if the product code in the PLU File ≠ 0.
| |
| Category | Sets the category if categories are used in this department. |
|
Categories are set up in Store Operations > Merchandise > Category.
| |
| Fuel Tax Exemption | Sets the fuel tax exemption that applies in this department. |
|
The parameter does not appear unless a fuel tax exemption record has been set up in Forecourt > Fuel Tax Exemption. It apples to fuel departments only.
| |
| Fees | Set to automatically apply a fee to the sales in this department. |
| ID Check | Sets the appropriate ID Check in this department. |
| Taxes | Sets the tax is to be imposed in this department. |
|
Taxes are set up in Store Operations > Payment > Tax Rates.
| |
| Blue Laws | Set to restrict the sales of an item in this department on designated days. |
|
Blue Laws are set up in Store Operations > Restrictions > Blue Laws.
| |
Some of the items in this table require setup in pop-up windows, as listed below.
* Click **\[Edit]** to open the Fees pop-up window; select the associated fee(s).
* Click **\[Edit]** to open the ID Check pop-up window; select the associated ID(s).
* Click **\[Edit]** to open the Taxes pop-up window; select the associated taxes.
* Click **\[Edit]** to open the Blue Laws pop-up window; select the associated law.
{% endstep %}
{% step %}
**Configure InComm Department**
Configure the InComm Department Options.
| Value | Description |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Options | |
| Allow Food Stamps | Determines whether food stamps will be allowed for a sale made to this department. |
| Allow Fractional Quantity | Permits the product to be sold in fractional quantities as needed in this department. |
|
If this parameter is selected, all quantities entered in department sales for this department are read as decimals. For example, if the quantity is 1 3/4 lbs of turkey, key \[1] \[7] \[5]. If this parameter is not selected, all quantities entered are read as whole numbers.
| |
| Fuel Department | Defines the department as a fuel department. |
|
If the Fuel Department option is selected, then do not select “Mark as Negative.”
| |
| Allow Special Discount | Permits items in this department may have a special discount applied to them. |
|
If this parameter is selected, then Special Discount MOP should be set up in Store Operations > Payment > MOP with Special Discount MOP Code.
| |
| Negative Department | Permits transaction amounts to be subtracted from receipt and report totals. |
| Money Order Department | Defines the department as a money order department. |
|
If this parameter is selected, then do not select “Mark as Negative.”
| |
| {% endstep %} | |
{% step %}
**Save or Cancel**
Select **\[Save]** to accept, or **\[Cancel]** to exit without saving changes.
{% endstep %}
{% endstepper %}
### Configuring PLUs
PLUs represent a sellable item. Multiple PLUs can then be linked to a department.
{% stepper %}
{% step %}
**Configuration Client**
From the Configuration Client, go to: **Store Operations > PLUs**.
The Price Look Up Manager window appears.
{% endstep %}
{% step %}
**Add**
Click \[**Add**] to set up a new PLU, or **\[Delete]** to delete an existing PLU.
{% endstep %}
{% step %}
**Configure the Price**
Configure the Price Look Up Manager parameters in the pop-up window.
| Value | Description |
| ------------ | ---------------------------------------------------------- |
| PLU Manager | |
| PLU | Sets the Price Look Up number or scan barcode for the PLU. |
| Description | Department description. |
| Price | Sets the PLU unit cost. |
| Sell Unit | Sets the PLU sell unit. |
| Department | Assigns the Prepaid Department. |
| Product Code | Assigns the unique product code. |
| Fees | Set this parameter to apply fees automatically. |
| ID Check | Select this parameter if the item requires an ID check. |
| Taxes | Sets the taxes to be imposed. |
| Blue Laws | Set to restrict the sales of an item on designated days. |
* Click **\[Edit]** to open the Fees pop-up window; select the associated fee(s).
* Click **\[Edit]** to open the ID Check pop-up window; select the associated ID(s).
* Click **\[Edit]** to open the Taxes pop-up window; select the associated taxes.
* Click **\[Edit]** to open the Blue Laws pop-up window; select the associated law.
{% endstep %}
{% step %}
**PLU Properties**
Configure the PLU Properties.
| Value | Description |
| ---------- | ----------------------------------- |
| Properties | |
| Open | Permits the PLU to be an open item. |
| Returnable | Allows the product to be returned. |
| Value | Description |
| ---------------- | ------------------------------------------------------------------ |
| Special Discount | Permits special discounts for the PLU. |
| Fractional Qty | Permits the product to be sold in fractional quantities as needed. |
| Not Sold | Prohibits the product from being sold. |
| Food Stamp | Permits food stamps to be used to purchase this PLU. |
| Promo | Permits the product to be included in a promo. |
| {% endstep %} | |
{% step %}
**PLU Taxable Rebate**
Configure the PLU Taxable Rebate parameters.
| Value | Description |
| -------------- | ---------------------------------------- |
| Taxable Rebate | |
| Rebate Amount | Sets the rebate amount for the PLU. |
| Taxes | Sets the taxes to be imposed on the PLU. |
| {% endstep %} | |
{% step %}
**Save or Cancel**
Select **\[Save]** to accept, or **\[Cancel]** to exit without saving changes.
{% endstep %}
{% endstepper %}
### Enabling InComm
From the Configuration Client, go to: **Payment Controller > EPS Prepaid Configuration**.
#### Configuring Prepaid Network
Configure the Prepaid Network parameters as shown in the table below.
| Value | Description |
| --------------- | ---------------------------- |
| Prepaid Network | |
| Network Name | Select \[InComm]. |
| Enabled | Enables the Prepaid Network. |
#### Configuring Prepaid Departments
{% stepper %}
{% step %}
**Prepaid Department**
In the Prepaid Department section, select **\[Add]**.
{% endstep %}
{% step %}
**Configure**
Configure the Prepaid Department parameters as described in the table below.
| Value | Description |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Prepaid Departments | |
| Department | Sets the Prepaid Department to configure. |
| Enabled | Enables the selected Prepaid Department. |
| Pre-Validate | Specifies whether an InComm Pre-Authorization Request needs to be sent to the host when selling items from the selected prepaid department. |
|
The Pre-Authorization Request is used to verify whether the actual transaction can be successfully completed before the payment is tendered.
| |
| Reprint Security Level | Sets the security levels for reprinting the receipt at the POS. |
| Delete | Allows an existing prepaid network to be deleted. |
| {% endstep %} | |
{% step %}
**Prepaid Network Messages**
Configure PrePaid Nerwork Messages
| Value | Description |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Prepaid Network Messages | |
| Show Guideline | Enables Guideline Message prompt. Instructs cashier to follow guidelines when selling items from a prepaid department. |
| Show Purchase | Enables Purchase Message prompt. Appears after Guideline Message prompt. Reminds cashier to only disclose PIN for a prepaid item with customer present. |
| Show Cancel | Enables Cancel Prompt. Appears after cashier selects NO on Purchase Message prompt screen. Informs cashier prepaid item cannot be sold and is removed from the ticket. |
| {% endstep %} | |
{% step %}
{% endstep %}
{% endstepper %}
### Configuring Prepaid Network Messages
Three types of message prompts are displayed to the cashier during prepaid card activation / recharge process:
* **Guideline message prompt**: Guideline Prompt when enabled, prompts the cashier when a prepaid card activation item (ProdCode: 560 to 575) is added to the ticket. This message instructs the cashier to follow guidelines to avoid fraud. The default message for the guideline prompt is “Please ensure you are following AML fraud guidelines by not selling more than $1900.00 in cards to one customer - The limit is $999.00 in the state of Arizona.”
* **Purchase message prompt:** Purchase Prompt when enabled, prompts the cashier if PIN Activation item (ProdCode = 560) is added to the ticket. The purchase prompt appears after the Guideline Message Prompt if Guideline Prompt is enabled. The purchase prompt instructs the cashier not to take PINs for prepaid cards over the phone. The Purchase prompt has **YES** and **NO** buttons. If the cashier responds **YES**, then PIN Activation item can be added to the ticket. If the cashier responds **NO**, then PIN Activation item is not allowed for sale and the item is removed from the ticket with an error message. The default message for purchase prompt is “Is this purchase being made by someone on site?”
* **Cancel message prompt:** When the cashier responds with a **NO** to the Purchase Prompt, the PIN Activation item is removed from the ticket and Cancel Prompt message (if enabled) is shown to the cashier. This prompt is to inform the cashier that the item cannot be sold and is being removed. The default message for the Cancel Prompt is “PIN numbers are never to be given to anyone over the phone - NO EXCEPTIONS!”
You can use the text boxes (shown below) to edit the default text if you wish.
{% stepper %}
{% step %}
**Checkboxes**
Use the checkboxes above each message field to enable that message. (You can edit the text to suit your particular circumstances.)
{% endstep %}
{% step %}
**Save or Cancel**
Select **\[Save]** to accept, or **\[Cancel]** to exit without saving changes.
{% endstep %}
{% endstepper %}
### Configuring InComm FEP and Cards
To configure the InComm as the EPS network, in Configuration Client, go to: **Payment Controller > EPS Configuration > InComm Configuration**, as shown below.
The InComm Configuration window appears.
FEP configuration applies to all InComm products, so you must enable it on the main tab, then proceed to the FEP Card tab, as shown below.
#### FEP Tab
To configure the FEP settings:
{% stepper %}
{% step %}
**FEP Tab**
Select the **\[FEP]** tab.
{% endstep %}
{% step %}
**Network Parameters**
Configure the Network parameters using your Terminal and Dealer IDs. (InComm provides these IDs.) See the InComm Reference Table in this document for more information.
Value
Description
Network
FEP Enabled
Enables to FEP.
Terminal ID
Terminal ID. This field is usually set as 5 digit store number + 3 digit lane number. In the Verifone Commander system, the Terminal ID is a single value per site. It is required that the Terminal ID be unique across all the sites. Recommendation: set this configuration value to the 5 digit site ID (zero padded) and lane number 000. For example, store number 141 would be set as “00141000”(“00141” = 5 digit store ID, “000” = 3 digit lane number). An InComm integration project resource will provide the format. Refer to “Incomm Reference Table” on page 4 for more information.
Dealer ID
Merchant Retailer ID (assigned by InComm). Set this to the value directed by InComm. Refer to “Incomm Reference Table” on page 4 for more information.
{% endstep %}
{% step %}
**Communication Options**
Configure the Communication Options parameters.
Value
Description
Communication Options
Mode
Select the [IP] mode.
IP Address
Enter the InComm Host <IP Address>.
Port
Enter the Primary Host <Port>.
Secondary IP Address
Host Secondary IP Address if applicable.
Secondary IP Port
Secondary Host Port if applicable.
{% endstep %}
{% step %}
**FEP Parameters**
Configure the FEP parameters, as shown below.
| Value | Description |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| FEP | |
| Store ID | Sets the Store ID. Store ID (5 digit store number (zero padded) + merchant/retailer name, such as 00141SUPERTSHOP) This value’s format may vary. An InComm integration project resource will provide the format. Refer to “Incomm Reference Table” on page 4 for more information. |
| Print Gift Receipt | Determines if a gift receipt prints. |
| {% endstep %} | |
{% step %}
**Fallback**
Configure Fallback parameters as shown below.
| Value | Description |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| Fallback | |
| Enable Fallback Approvals | Enables Fallback Processing. |
|
Fallback involves a stand-in approval of activations in the event of network connectivity failure with the InComm host. After connectivity is established, the stored transactions are sent to the host when a response is received or a Daily Close is performed. Timeout reversal will be always supported.
| |
| Maximum Transactions | Sets the Fallback Transaction Limit. |
| Maximum Amount | Sets the Fallback Dollar Limit. |
| Retry Interval in Seconds | Sets the SAF Retry Interval. |
| Retry Limit | Sets the SAF Retry Limit. Zero means retry indefinitely. |
| {% endstep %} | |
{% step %}
**Save or Cancel**
Select **\[Save]** to accept, or **\[Cancel]** to exit without saving changes.
{% endstep %}
{% endstepper %}
#### FEP Card Tab
{% stepper %}
{% step %}
**FEP Card**
In the InComm Configuration window, click on the **\[FEP Card]** tab.
{% endstep %}
{% step %}
**Add or Delete**
Select **\[Add]** to configure the FEP Card, or **\[Delete]** to remove an existing card.
{% endstep %}
{% step %}
**Configure Card**
Configure the card Information parameters as listed in the table below.
| Value | Description |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
| Card Information | |
| Card Abbreviation | Two digit abbreviation for the given card. |
| Card Name | Name given to identify this entry. |
| Lower ISO | Sets the low value of the card range. |
|
The entered card number must be greater than or equal to this number to match the table entry.
| |
| Value | Description |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Upper ISO | Sets the high value of the card range. |
|
The entered card number must be less than or equal to this number to match the table entry.
| |
| Pan Length | This entry must match the total number of digits embossed on the card. |
| Send Track I | If two Send Track fields are set to 1, and the FEP accepts more than one track, then both will be sent. 0 = Don’t send Track 1 to the Host, or manually entered account. 1 = Primary track to send to the host. 2 = Secondary track to send to the host. |
| Send Track II | If two Send Track fields are set to 1, and the FEP accepts more than one track then both will be sent. When both flags are non-zero, Send Track 2 has priority over Send Track 1, if Track 2 data exists. 0 = Don’t send Track 1 to the Host, or manually entered account. 1 = Primary track to send to the host. 2 = Secondary track to send to the host. |
| Card Enabled | Enables the selected proprietary card. |
| Refund Allowed | Permits refunds. |
| Value | Description |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Card Limits | |
| DCR Auth Amount | Populate this field with the Authorization amount you want to use. This will allow you get an authorization for greater than $1. |
| {% endstep %} | |
{% step %}
**Save or Cancel**
Select **\[Save]** to accept, or **\[Cancel]** to exit without saving changes.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.verifone.com/feature-references/features-and-products-references/incomm/configuring-incomm.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.