This document covers EFTLink Integration with TLG (The Logic Group) 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 directly to the SolveConnect software usually installed on the same PC as the POS, using a proprietary socket protocol.
Note: This document does not cover the installation of SolveConnect software. |
In addition to standard EFTLink files the following are used:
Core/SolveConnect/SolveConnect.jar
– Core interface to TLG's SolveConnect software.
SolveConnect.POS.properties
SolveConnect.properties
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.solveconnect.SolveConnectCore
There are two configuration files - SolveConnectPOS.properties and SolveConnect.properties. These are copied from cores/SolveConnect to the base eftlink folder by installcore.bat or installcore.sh.
SolveConnectPOS.properties carries only the POS specific identifiers, SolveConnect.properties carries everything else, and can usually be deployed on a retailer's estate without other changes.
Table 8-1 SolveConnectPOS.properties - Key Settings
Setting | Description | Default | Example |
---|---|---|---|
SourceID |
The POS specific identifier, allocated by retailer, to be unique across the retailer's estate. |
NA |
|
Store.ID |
A 4-digit store identifier which forms part of the reference number assigned to each transaction. |
9999 |
|
POS.ID |
2 digit POS identifier which forms part of the reference number assigned to each transaction. |
99 |
|
Note: Together, the Store.ID and POS.ID settings can be used to create a transaction reference that will be unique across all sites in a group. |
Table 8-2 SolveConnect.properties - Secondary Settings
Setting | Description | Default | Example |
---|---|---|---|
ServiceHost |
Hostname or IP address of SolveConnect service. |
NA |
|
TransactionTimeoutPeriod |
Number of seconds to allow a transaction to complete. |
180 |
|
CancellationTimeoutperiod |
Maximum number of seconds the core will wait for a transaction response following a cancellation. |
30 |
|
MaintenanceMenuTimeout |
The number of seconds to wait for an option to be selected before dismissing the Maintenance menu. |
30 |
|
AuditLoggingEnabled |
Enable/Disable logging of transaction results to an audit log. |
false |
|
TransactionReferenceScheme |
The format and source of Store and Till-ID values. Recognized values are Properties and PowerPOS. If set to PowerPOS, the POS.ID value will be automatically extracted from the POS system name at run time, so the setting in |
Properties |
|
TransactionNumberFromPOS |
Whether to use the transaction number from the POS (with suffixes to ensure uniqueness) rather than the default auto-incrementing number. |
true |
|
ForcePurchaseWithCashback |
Force all POS Purchase requests to be converted to Solve Purchase with Cashback requests. |
true |
|
PromptForCashbackCharge |
Prompt for a cashback charge. |
true |
|
TransactionReferenceFormat |
Format for the transaction reference to be passed to SolveConnect. Built from the store id (S), POS ID (P) and POS Transaction number (T). |
SSSSPPTTTTTT |
|
EmbeddedPrinting |
Whether customer printout is to be buffered and included in the POS authorization response such that it can be embedded in the POS receipt. |
false |
|
DCC Keywords |
DCC keywords for extracting DCC from status message. There are no defaults. |
NA |
|
AuthTokenOrigin |
Whether to automatic token recognition to establish local/central origin. |
false |
|
Token Formats |
Token formats to identify local/central token. There are no defaults. |
|
|
CardSwipeTimeoutPeriod |
Number of seconds to allow for a standalone card read/swipe to complete. This will need to be extended, for example, to 9999 if an open/background card read operation is required. |
30 |
|
PEDLogoffDelayTime |
Delay time between POS logoff and PED logoff, to allow for operator changeover without PED disconnection. Applies to networked PEDs only. Time in seconds. Set to 0 to disable PED logoff. |
300 |
|
SelectiveMerchantPrint |
Determine whether merchant print is selective, that is enable for some conditions, disabled for others. |
false |
|
MercantPrint.not_present.not_performed |
In selective mode, all merchant print is disabled by default, but can be selectively re-enabled based on a combination of the transaction attributes returned by SolveConnect. Note: This is the opposite way round to selective customer print. The attributes used are: TRANSACTION:customer present, not_present, internet CARDHOLDER_RESULT:verification pin, signature, pin_and_signature, on_device, not_performed, failed, unknown These attributes are formed into a dot-separated property name (for example, MerchantPrint.present.pin) that can be set to "true" to re-enable merchant print for that attribute combination. Note: merchant print requiring signature will always be printed, it cannot be disabled. For example, to re-enable merchant print for CustomerNotPresent transactions:
Re-enable merchant print for CustomerNotPresent transactions. |
NA |
|
SelectiveCustomerPrint |
Determine whether customer print is selective. For example, enabled for some conditions disabled for others. |
false |
|
CustomerPrint.not_present.not_performed |
In selective mode, customer print is enabled by default, but it can be selectively disabled based on a combination of the transaction attributes returned by SolveConnect. Note: This is the opposite way round to selective merchant print. The attributes used are: TRANSACTION:customer present, not_present, internet CARDHOLDER_RESULT:verification pin, signature, pin_and_signature, on_device, not_performed, failed, unknown These attributes are formed into a dot-separated property name (for example, CustomerPrint.present.pin) that can be set to "false" to disable customer print for that attribute combination. For example. to disable customer print for CustomerNotPresent transactions:
|
NA |
|
SignatureCheckReprintOption |
Determine whether to include a "reprint" option when prompting operator for signature verification. Caution - if set true, the display request will be sent as a menu selection rather than a yes/no and this will affect the way it is presented to the operator. |
false |
|
ManualAuthMinLength |
Minimum input length required for Manual/Voice referral authorization code response. |
0 |
|
The following operations are supported by this implementation of the SolveConnect interface.
Table 8-3 SolveConnect - Supported Functions
Function | Description |
---|---|
Payment |
Sends payment request to the terminal. Terminal will return a response message with formatted receipt strings for customer and/or merchant receipts. In an event of referral where authorization cannot be obtained online then a prompt for authorization code will appear; authorization code must be obtained via telephone and entered here. If successful, appropriate receipts will be printed at the end of transaction. |
Reversal |
Sends reversal request to the terminal. This 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 request to the terminal. This will refund a transaction with specified amount. |
GiftCard |
Sends gift card payment request to the terminal. Specified amount will be deducted from the gift card. Administration options to add balance and check balance is also supported. |
Receipt Reprint |
Reprint merchant/customer receipt. |