How to: Configure cards on file at POS

Card-on-file at POS uses the Token Vault provided by the EFT Extension for LS Pay (see Card-on-File Functionality in POS). Both the Legacy Card Payment engine and the EFT Extension Card Payment engine share this same Token Vault, so either engine can create, retrieve, and use stored tokens once it is configured.

This configuration does not ship as demo data. Before card-on-file can be used at any store, you (or a partner/consultant configuration package) must set up the POS Lookups, the POS buttons, and the Token Vault Setup storage mode described below. Without this one-time setup, the Add Card to File and Card on File POS commands cannot find or store tokens, even though the upgrade to a version with the EFT Extension for LS Pay completes without error.

To set up the POS Lookups for token selection

Two POS Lookups are required. Both are based on a POS Data Table connected to the EFT Extension for LS Pay's LSCEFT Token table.

Note: The LSCEFT Token table is owned by the EFT Extension for LS Pay, a separate extension - its object ID cannot be verified from this repository.

#TOKENVAULTSELECTION

In BackOffice, open the POS Lookup List, and create a new Lookup with Lookup ID #TOKENVAULTSELECTION and description Token Selection when using EFT Ext.
In the Data Table ID field, create or select a POS Data Table with ID TOKENVAULT-SELECTION, based on the LSCEFT Token table, with columns for Card Number, Card Issuer, Card Issuer ID, Default Token, and Token.
Set the Selection Mode field to SelectOne.

#TOKENSELECTION

Create a new Lookup with Lookup ID #TOKENSELECTION and description Selection of token for payment.
In the Data Table ID field, create or select a POS Data Table with ID TOKENSELECTION, based on the same LSCEFT Token table, with columns for Card Issuer, Card Issuer ID, Default Token, and Token.
Set the Selection Mode field to SelectOne.
Select the Hide Input Area check box.

Note: For general background on setting up a POS Lookup and its Data Table, see POS Lookup Setup and Data Tables.

To set up the POS buttons

Add a button for each POS command to the relevant POS menu (Card on File is typically pressed after Total, on the payment menu):

Open the POS Menu List for the relevant profile, and go to the Lines FastTab of the menu you want to add the button to.
Add a new line, then click the Assist button to open the POS Button Properties card.
In the Command field, select AddCardToFile. This lets the cashier request a new token from the card provider and store it in the Token Vault.
Add another button on the payment button panel, and in its Command field select CardOnFile, in it's Parameter field select the Tender type to use for the payment (Card for example). This lets the cashier pay with a token already stored in the Token Vault.

Note: For general background on setting up POS menu buttons, see POS Menus.

To configure the Token Vault Setup storage mode

Click the icon, enter Token Vault Setup, and select the relevant link.
Select a storage mode. Select Local to store tokens in the LS Central database - the Cards on File page (see How to: View and manage cards on file for a member) only shows tokens when the Token Vault is configured for local storage.
Save the page.

The Token Vault should store it's data centrally so if the POS is an on-prem POS then the Token Vault configuration on the POS instance should be set as Remote and then the Token Vault configuration on the Head office instance should be set as Local. If the entire system is online i.e. both POS and Head office is using the same LS Central instance (database) then the Token Vault configuration should be configured to be Local. See further information in the online help for the EFT Extension for LS Pay about how to configure the webservices for Remote access.