Post Installation Steps

By default, in Windows, the 'OPI Server' service runs under the Local system account user. To allow the EFTLink service to create dynamic key store files, a user with administrative privileges may be required. To configure this in the services panel, right click on the OPI Server service. Select the Properties and then select the Log on tab. Select This account and input the user's credentials and select OK.

  • AJB FiPay: The AJBComm.jar component needs to be copied to C:\eftlink\cores\FIPay or /opt/eftlink/cores/FIPay for Linux. Refer to the FileSet section of the AJB core in the Oracle Retail EFTLink Core Configuration Guide located on OHC for more details.

  • Cayan: The merchant credentials which are supplied by Cayan team are needed to be setup. This can be done in Xstore's back office through the EFTLink Admin functions. Refer to the Account Information Entry section of the Cayan core in the Oracle Retail EFTLink Core Configuration Guide located on OHC for more details.

  • VerifoneUS: The PED needs to be paired with EFTLink prior to use. This can be done through Xstore's back office in the EFTLink Admin functions. Refer to the Administration Functions section of PointUS core in the Oracle Retail EFTLink Core Configuration Guide located on OHC for more details.

  • Starting from release 24, as mentioned in the Oracle Retail EFTLink Core Configuration Guide, the OPIRetail, Cayan, and PayByLink cores enforce the use of a dedicated truststore. Please pay particular attention to the follow section: Securing Communication to EPS Devices by Importing Trusted Certificates.