How to Configure Cash and Card Payments
Description
This guide explains how to set up the Payment methods (tender types) to be used at the POS, and how to set the various rules to be applied for handling payments and refunds. It also covers setting up the POS to connect to the Enactor payment service to handle card payments (Configuration of the Payment service itself is out of scope for this guide).
The intent of the guide is to provide basic guidance on configuration including required and the most common options. Please refer to the full solution documentation for a detailed explanation of all available settings.
Configuration
Tenders
The Tender configuration is maintained using the Tender Maintenance function described following.
Accessing Tenders
Access Tenders using the Tenders option, obtained via the selection sequence shown at right, starting from the Main Menu:
The Tenders option invokes the Tenders Maintenance select page as shown below. The Select page lists currently-configured Tenders and enables the User to Add, View, Edit, Copy or Delete Tenders.
New Tender
In the Tender Maintenance select page select the Create a new Tender Option, which presents an initial page to capture a Region, Tender Type and Tender ID. Enter values and select the Create option.
Cash
To configure the cash tender, either select the pre-existing cash tender for your region or create a new tender with a tender type of “Cash”.
On the General tab, provide a description for the tender type and select the appropriate currency. Make sure the “Open Drawer” option is selected so that the cash drawer will open when the tender is selected. Alternatively, “Open Drawer at End” will wait until the transaction is complete before opening the drawer.
The settings on the Restrictions 1 tab allows you to control how the tender can be used. Select the “Debits Allowed” option which permits the tender to be used to pay for a transaction. The “Debit Tendering Restrictions” option allows you to prevent over or under-tendering a transaction using the tender. These restrictions would not be required for a cash tender so “None” is the normal selection. “Debit Limit” allows the specification of a maximum amount of the tender that can be selected in a single transaction if desired.
Selecting the “Credits Allowed” option permits the tender to be used in refunds/returns. In a refund scenario, a customer would never be given more cash than due with the expectation of the store receiving change from the customer so the “Credit Tendering Restrictions” should be set to “Amount less than or equal balance”. A maximum amount of cash that can be refunded in a single transaction can be specified by using “Credit Limit”.
The “Prompt With Amount Due” option will cause the balance due for the transaction to be offered as the default amount for the tender.
On the Restrictions 2 tab, you will specify the appropriate return tenders. Typically, when configuring a cash tender, alternative refund tenders will also be designated in the event that a large return may exceed the cash on hand.
A separate guide covering Cash Management has been published. Cash management settings at the tender level are covered in the separate Cash Management guide.
A drawer limit can be set on the Cash Tender tab if desired
To enable basic Cash tender functionality, no settings changes are necessary under Discount Restrictions, Overlap Tenders, User Limits, Change, Surcharge or Attributes. Information regarding these additional options can be found in the full Enactor documentation.
Card
To configure the card tender, either select a pre-existing card tender for your region or create a new tender.
On the General tab, provide a description for the tender type and select the appropriate currency.
On the Restrictions 1 tab, the following options should be selected: Debits Allowed, Credits Allowed and Prompt With Amount Due. Credit Tendering Restrictions should be set for “Amount less than or equal balance”. Limits can be established for Debits and Credits if desired.
On the Restrictions 2 tab, you will specify the appropriate return tenders. Typically, when configuring a card tender, alternative refund tenders will also be designated in the event that a card is no longer valid at the time of return.
A separate guide covering Cash Management has been published. Cash management settings at the tender level are covered in the separate Cash Management guide.
A cashback tender can be set on the Card Tender tab if supported. The “Card Tender Return” option allows you to specify if a return can be done to any card or only a card used in the original transaction.
To enable basic Card tender functionality, no settings changes are necessary under Discount Restrictions, Overlap Tenders, User Limits, Change, Surcharge or Attributes. Information regarding these additional options can be found in the full Enactor documentation.
Card types
Enactor Retail provides facility for processing Cards of various TYPE that may be issued and managed by external providers. These Cards are recognised and validated based on IIN Range configuration and their processing, specific to each TYPE, is configurable based on Card Type associated with the IIN Range.
Creating Card Types
Card Types are defined using the Card Types option, obtained via
the selection sequence shown at right starting from the Main Menu:
The Card Types option invokes the Card Type Maintenance Page as shown below. Select the Create a new Card Type option.
In the initial page specify the Card Type ID. A Region and Type are selectable from dropdown lists of configured Regions and built-in Types, respectively. Select Create.
On the General tab, enter a description for the card type and select the tender type from the drop-down like the Card tender type created in the previous section. If the acquirer information has already been setup, you can also select the appropriate acquirer at this time.
On the Payments tab select the card scheme that aligns with the card type being configured. A maximum transaction value can be entered in the “Transaction Ceiling” field if desired. Select the “Enable Refund” option if the card type can accept a refund. If cashback is supported, select the “Enable Cashback” option and specify a maximum amount in the “Cashback Ceiling” field.
The Actions tab allows configuration of how non-conforming transactions can be completed. Each exception can be configured to always accept or reject or require being connected to the host.
The Authorisation tab defines the business policy and acquirer requirements for handling the particular card type. Any changes made on this tab will be specific to retailer and acquirer requirements. A complete explanation of these fields can be found in the full Enactor documentation.
The Onine PIN tab provides the settings to specify the PIN handling requirements for the card type. This includes PIN type (none, Online PIN or Online PIN + Signature), PIN length and PIN bypass (Signature Fallback).
The AVS Tab specify the processing requirements in relation to the Address Verification System (AVS) Security provisions for the Card Type applied by the PED during Payment Processing. The values for these options will be driven specifically by the retailer’s business rules and the acquirer’s processing requirements. These options specify when the card security code needs to be used and when a customer address needs to be collected as part of card processing.
Tabs ICC1 and ICC2 contain settings that are specific to EMV processing. These attributes will be specified by the issuer and acquirer and will be covered in more detail as part of the payment processing setup guide.
IIN ranges
Once a card type has been defined, IIN ranges will need to be established so that the card type can be identified.
Creating IIN Ranges
IIN Ranges are defined using the IIN Ranges option, obtained via
the selection sequence shown at right starting from the Main Menu:
The IIN Ranges option invokes the IIN Range Maintenance Page as shown below. Select the Create a new IIN Range option.
In the initial page specify the Range Start and Range End value defining the IIN Range, which permits specification of the limits using up to 15 Digits, and the Minimum and Maximum PAN Length, which accommodates a range of 0-99, then select Create.
The General tab controls the principal identification and usage features of the IIN Range. This includes the card and issuer description for easy identification. Also specify the Digit Group Lengths, Country and Currency.
The Track Data tab specifies where specific data can be found on the MSR. This arrangement of this data has become much more standardized over the years. Unless a different scheme has been provided by the card issuer, please use the values depicted below for PAN Attributes, Expiry Date Attributes and Service Code Attributes:
An IIN range can be defined for many different kind of cards including payment, cheque guarantee, loyalty, employee, gift card and others. The type of card is specified on the Applicable Cards tab. A regular payment card would be marked as “Payment Card” but a combination debit card (i.e. Visa-Debit) may be marked as both a “Payment Card” and a “Cheque Card” as in the example below. The “Online Update” options allows online updates of loyalty accounts and is selected by default.
Tender Menu
The creation and setup of the POS menu structure is covered in a separate guide. This guide will focus only on the creation and setup of a Tender menu within an existing menu structure.
Accessing Menus
Access Menus using the Menus option, obtained via the selection sequence shown at right, starting from the Main Menu:
The Menus option invokes the Menus Maintenance select page as shown below. The Select page lists currently-configured Menus and enables the User to Add, View, Edit, Copy or Delete Menus. To create a new Tender menu select “Create New Menu”.
In the Menu Maintenance select page select the Create a new Menu Option, which presents an initial page to capture a Menu Set, Role, Menu Group, Locale and Menu ID, all of which serve to uniquely identify a Menu. Enter values and select the Create option.
For a new Tender menu, the “Menu Set” would be POS. Select the “Role” of the user that will have access to the menu which would typically be Sales Assistant for a standard Tender menu. Select the “Menu Group” that the Tender menu will be added to.
Begin creating the menu by clicking the “Add…” button and then selecting “Add a new Button”.
Then, create the button for a Cash tender. On the General tab, under “Event” select “Cash Tender”. The “Button Label” is what will be visible to the cashier on the menu. It should be changed to simply read “Cash”. On the Data tab, add an item with the name (without the quotes) “enactor.mfc.TenderId”, a Java Type of “string” and the Value should be the Tender ID of the cash tender created previously (“CASH_UK” in our example). Be sure to click “Add” after the values have been entered.
To create the button for Card tender, repeat the process above but select “Card Tender” for the Event on the General tab and specify the correct Tender ID on the Data tab (“CARD” in our example above).
