| Oracle® Retail EFTLink Core Configuration Guide Release 18.0 F12262-04 |
|
 Previous |
 Next |
This document covers EFTLink Integration with Tender Retail Payment Systems. It should be read in conjunction with the Oracle Retail EFTLink Framework Installation and Configuration Guide.
This document assumes static EFTLink configuration. When deploying with a POS that supports dynamic configuration, all property settings referred to below should be set on the POS, and not directly into local property files.
EFTLink connects to the Tender Retail application that is installed on the same PC as the POS, using a proprietary socket protocol. The Tender Retail application must be started.
|
Note: This document does not cover the install of the Tender Retail software. |
The following files are used in the EFTLink folder:
cores/tenderretail/epstenderretail.jar
tenderretail.properties (optional, if not present defaults apply)
Lang<CC>_<Core>.properties – Language translation file, for further information see Language.
The translation files for this core should not require alteration, but if necessary then this can accomplished by amending the relevant Lang<CC>_<Core>.properties within the base eftlink folder.
The language used will follow the language set in the EFTLink framework; see the Oracle Retail EFTLink Framework Installation and Configuration Guide, EFTLink General Information, Translation section.
EftlinkConfig.properties
DisplayLanguage = EN
Supported country codes are: CN, DE, EN, ES, FR, IT, JP, NL, PT, RU and SV.
The following should have been set in the EftlinkConfig.properties file by installcore.bat or installcore.sh
EPSCore0=manito.eft.tenderretail.TenderRetailCore
The full set of configuration properties is defined and commented in tenderretail.properties.
Settings that may be different for all POS.
Table 9-1 Tender Retail - Key Settings
| Setting | Description | Example |
|---|---|---|
|
tenderRetail.terminalID |
The bank supplied ID number specific to the station processing the transaction as configured in the Tender Retail Merchant Connect Multi Credit/Debit server. Only one terminal is supported. |
|
These settings are normally correct at their default values, but can be overridden if necessary.
Table 9-2 Tender Retail - Secondary Settings
| Setting | Description | Default | Example |
|---|---|---|---|
|
mcm.host.folder |
The path to the folder where the Tender Retail's software is installed. |
\MerchantConnectMulti |
|
|
mcm.host.port |
The socket port for making payment requests. |
3858 |
|
|
mcm.host.name |
The file location of where the MCM software is installed. |
localhost |
|
|
check.mcm.server.on.startup |
Defines whether the Tender Retail MCM server should be contacted initially when starting the EFT adapter. |
true |
|
|
terminal.cap.cardtype |
Determines whether the terminal can figure out the card type used (credit/debit). This setting only applies when using Legacy Message Requests. |
false |
|
|
communications.type |
Sets the communications type. |
ip |
|
|
connection.timeout.1 |
This parameter configures the time until when the Tender Retail software is expected to respond to a request. This includes the time needed to swipe the card at the PIN Pad terminal (if required) and to contact the financial institution. |
120000 |
|
|
connection.timeout.2 |
This parameter determines the interval in which the Tender Retail software is expected to continue delivering data once it began to deliver something. |
2000 |
|
|
timeout.saf |
This parameter determines the time the Tender Retail software has to empty its store and forward queue. Note: If there is a communication problem with the eft transaction processor or there are lots of transactions in the queue it may take quite a while to process the queue. |
600000 |
|
|
do.positive.ack |
Determines whether the responses are acknowledged. The value specifies the interval in which the Tender Retail MCM server expects the acknowledgements. |
5000 |
|
|
currency.code |
Used in conjunction with SVS Gift card to set the currency code. |
840 |
|
|
currency.symbol |
Line display currency symbol. |
$ |
|
|
Use.tokens |
Determines whether the mcm server is set to use tokens. # this setting must match the MCM server. |
true |
|
|
combine.receipts |
Turn on/off POS combine receipt. |
false |
|
|
combine.receipts.suppress.lines |
When combine.receipt is true, sets which line number to suppress. |
NA |
|
|
combine.receipts.suppress.strings |
When combine.receipt is true, sets which line to suppress when strings are matched. |
NA |
|
|
exclude.combine.receipts.Strings |
Sets what line to suppress when strings are matched. |
NA |
|
|
Void.header.n [where n is >0] |
Specify a number of header lines to include on void receipts (maximum of 3 supported lines). |
None |
|
|
Void.footer.n [where n is >0] |
Specify a number of footer lines to include on void receipts. |
None |
|
|
Electronic.signature |
Enable the extracting of electronic signature from the device for display/approval on the POS. |
false |
Electronic.signature=true |
The terminal has some administration/maintenance functions. These are normally invoked from a dedicated EFT Maintenance button, but if this is not available, they could be accessed by an engineer using the EFTLink built-in test harness.
EFTLink uses DeviceProxy messages to display input prompts on the POS to manage these functions.
Below is a list of supported functionalities of the interface to Tender Retail.
Table 9-4 Tender Retail - Supported Functions
| Function | Description |
|---|---|
|
Sale State Notifications |
Sends line items through to the device so the customer display can be updated in line with the POS. |
|
Payment |
Sends payment request to Tender Retail's MCM software. The MCM software will return a response message with formatted receipt strings for customer and/or merchant receipts. In an event of referral or communication failure where authorization cannot be obtained online then a prompt for authorization code will appear; authorization code must be obtained via telephone. Appropriate receipts will be printed at the end of transaction. |
|
Reversal |
Sends reversal requests to Tender Retail's MCM software. The MCM software will reverse a transaction specified by the transaction number, found on the receipt, which must be captured by the POS and passed on to EFTLink. |
|
Refund |
Sends refund requests to Tender Retail's MCM software. The MCM software will refund a transaction with specified amount. |
|
Tokenized Refund |
Sends refund requests to Tender Retail's MCM software. The MCM software will refund a transaction with specified token id. |
|
SVC Redeem |
Sends a gift or merchandise credit card payment request to the terminal. If there are not enough funds available, only the funds available will be deducted. The POS client will have to settle the transaction with another tender in this scenario. |
|
SVC Redeem reversal |
Sends a gift or merchandise credit card payment reversal request to the terminal. |
|
SVC Activate |
Sends a gift or merchandise credit card Issuance request to Tender Retail's MCM software. |
|
SVC Activate reversal |
Sends a gift or merchandise credit card activation request to Tender Retail's MCM software. |
|
SVC Add Value |
Sends a gift or merchandise credit card add value request to Tender Retail's MCM software. The card must be first activated before using this function. |
|
SVC Add reversal |
Sends a gift or merchandise credit card payment request to Tender Retail's MCM software. Optionally a void will be activated in the core to avoid presenting the card for the reversal. |
|
SVC Balance Enquiry |
Sends a gift or merchandise credit card balance enquiry request to Tender Retail's MCM software. |
|
SVC Unload (Cash Out) |
Sends a gift or merchandise credit card cash out request to the Tender Retail's MCM software. All funds are deducted from the account and the cash back amount is returned to the POS. The account is not deactivated as part of this process. |
