Solve Connect

EFTLink General

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.

Minimum Version

The Solve Connect interface requires a minimum EFTLink version of 20.0.

System Architecture

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.

Fileset

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.

Language

The translation files for this core should not require alteration, but if necessary then this can be 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.

Core Classname

The following should have been set in the EftlinkConfig.properties file by installcore.bat or installcore.sh:

EPSCore0 = manito.eft.solveconnect.SolveConnectCore

Configuration Settings

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.

Key Settings

Table 9-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	`SourceID = DPOS0001`
Store.ID	A 4-digit store identifier which forms part of the reference number assigned to each transaction.	9999	`Store.ID = 1234`
POS.ID	2–digit POS identifier which forms part of the reference number assigned to each transaction.	99	`POS.ID = 25`
PEDConnection	How the PED is connected: Serial/LAN	serial	`LAN`
PEDSerialNumber	Used as an identifier to target PED logon/logoff in a PED Pooling environment. Note: this setting is only applicable if the above key setting "PEDConnection" is set to Serial. When set to LAN the PED IP Address and Port is used as the identifier.	NA	`111-222-333`
AutoPEDLogoff	Determines whether the PED should be logged off after everything transaction. This is a required to be set to True when configuring a PED Pooling environment.	false	`true`

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.

Secondary Configuration Settings

Table 9-2 SolveConnect.properties - Secondary Settings

Setting	Description	Default	Example
ServiceHost	Hostname or IP address of SolveConnect service.	NA	`ServiceHost = IP ADDRESS`
TransactionTimeoutPeriod	Number of seconds to allow a transaction to complete.	180	`TransactionTimeoutPeriod = 180`
CancellationTimeoutperiod	Maximum number of seconds the core will wait for a transaction response following a cancellation.	30	`CancellationTimeoutPeriod = 30`
MaintenanceMenuTimeout	The number of seconds to wait for an option to be selected before dismissing the Maintenance menu.	30	`MaintenanceMenuTimeout = 45`
AuditLoggingEnabled	Enable/Disable logging of transaction results to an audit log.	false	`AuditLoggingEnabled = 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 `SolveConnect.POS.properties` can be left at zero.	Properties	`TransactionReferenceScheme = PowerPOS`
TransactionNumberFromPOS	Whether to use the transaction number from the POS (with suffixes to ensure uniqueness) rather than the default auto-incrementing number.	true	`TransactionNumberFromPOS = true`
ForcePurchaseWithCashback	Force all POS Purchase requests to be converted to Solve Purchase with Cashback requests.	true	`ForcePurchaseWithCashback = true`
PromptForCashbackCharge	Prompt for a cashback charge.	true	`PromptForCashbackCharge = 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	`TransactionReferenceFormat = 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	`EmbeddedPrinting = false`
DCC Keywords	DCC keywords for extracting DCC from status message. There are no defaults.	NA	`DCCAmountKeyword = DCC Amount` `DCCExchangeRateKeyword = Exchange Rate` `DCCMarginKeyword = Margin`
AuthTokenOrigin	Whether to automatic token recognition to establish local/central origin.	false	`AuthTokenOrigin = false`
Token Formats	Token formats to identify local/central token. There are no defaults.		`LocalTokenFormat = 1234567890123456789` `CentralTokenFormat = 123456ABCDEFGHI1234`
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	`CardSwipeTimeoutPeriod = 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	`PEDLogoffDelayTime = 300`
SelectiveMerchantPrint	Determine whether merchant print is selective, that is enable for some conditions, disabled for others.	false	`SelectiveMerchantPrint = false`
MerchantPrint.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: `MerchantPrint.not_present.not_performed = true` Re-enable merchant print for CustomerNotPresent transactions.	NA	`MerchantPrint.not_present.not_performed = true`
SelectiveCustomerPrint	Determine whether customer print is selective. For example, enabled for some conditions disabled for others.	false	`SelectiveCustomerPrint = 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: `CustomerPrint.not_present.not_performed = true`	NA	`CustomerPrint.not_present.not_performed = true`
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	`SignatureCheckReprintOption = true`
ManualAuthMinLength	Minimum input length required for Manual/Voice referral authorization code response.	0	`ManualAuthMinLength = 0`

Fixed Configuration Settings

There are several fixed configuration settings in SolveConnect.properties that are commented in the property file. These are advanced options for development use.

Supported Functions

The following operations are supported by this implementation of the SolveConnect interface.

Table 9-3 SolveConnect - Supported Functions

Function	Description
Logon	Sends a PED Logon request to the Solve Connect client.
Logoff	Sends a PED Logoff request to the Solve Connect client.
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.