Configuration Parameters
This section is designed for developers and integrators, intended to provide details on the configuration and the list of parameters, to integrate POS systems and Verifone Engage devices to SCA 4.0 / Engage platform.
The purpose of Configuration Parameters section is to define the general parameters from PropertiesData.xml file, configuration menu, EMV parameters, those are necessary for the configuration of the payment device and the application to perform the functionalities.
Setup Details
SCA application setup requires the following packages to be downloaded and installed in the device. In case of a new device,
- Download ADK package
- Download SCA full package
- Download SCA configuration package
The above mentioned packages can be downloaded from VHQ location or by using NetLoader.
In case of updating only SCA application, instead of the full ADK package, the ADK Upgrader need to install.
The component in the package includes PME, CAM, NAFG Library, VLF and the ADK.
Defining Terminologies for Configuration
| Terminologies | Definitions |
|---|---|
| CREDIT CONVERSION | Credit conversion is an option, where the processors will convert the signature request to a PIN less debit request depending on certain criteria in the transaction request. |
For EMV Configuration
| Terminologies | Definitions |
|---|---|
| CREDIT PREFERRED | Credit+Debit+Smart Routing. [Dual cards with US common will select US common and send it as PINLESS. Security limit will be set to very high for US Common debit]. |
| CREDIT ONLY | NO pure Debit AIDs, NO keys on the device, US Common will go as PINLESS and security limit will be 999999. |
The following sections describe the details of all the configurations supported by Verifone SCA.
SCA Application Parameters
Parameters are stored locally in config.usr1 on Engage devices (press 1-5-9 and enter system password). Config.usr1 looks in TranslateConfig.xml file and updates properties.db accordingly. Therefore, when one uses a variable in a DLD or from VeriCentre, the name used will be in TranslateConfig.xml, whereas if one updates a setting directly via the Configuration menu it would be in properties.db.
Note
Designation of STANDALONE or STANDALONE ONLY indicates parameter supported only in the standalone environment.
PropertiesData.xml File
The PropertiesData.xml file contains all parameters necessary to configure the payment device (with the exception of the EMV INI configuration files).
The TranslateConfig.xml file contains a subset of the parameters contained in PropertiesData.xml. If users desire access through system mode, VeriCentre, or direct download (.dld) to the parameters in PropertiesData.xml, then the parameters must be included in TranslateConfig.xml; otherwise, users will need to change/update values directly in PropertiesData.xml.
When downloaded to the device, the propertiesData.xml file is put into SQLite database (properties.db), this contains:
- Host
- Merchant
- Devices
- Interfaces
- Currencies
- DCC Parameters
- Application Parameters
- OptFlags
- Deployment
- Card
- UDT
- Authorization
- Shift
- Store and Forward
- Surcharge
- Barcode
General Parameters
This section describes all the parameters from TranslateConfig.xml files with values and default values, those are common across all solutions.
- AppConfig Parameters
- Application Parameters
- Authorization Parameters
- Barcode Parameters
- Bluetooth Parameters
- Commerce Platform Parameters
- Currencies Parameters
- DCC Parameters
- Deployment Parameters
- Device/PINPad Parameters
- Hosts Parameters
- Interfaces Parameters
- Merchant Parameters
- OptFlags Parameters
- Other Parameters
- Card Range Table (PMEBIN.db) Parameters
- Settlement Parameters
- Shift Parameters
- Store and Forward Parameters
- Surcharge Parameters
- Transaction Logging
- UDT Parameters
- VHQ Parameters
- WebSocket Parameters
- APM CP Application Parameters
Host Specific Parameters
This section describes the parameters with values and default values, those are specific to the solutions.
