1 Introduction

After installing EFTLink (instructions can be found in the Oracle Retail EFTLink Framework Installation and Configuration Guide), you will need to configure the specific core with the required settings to allow the POS to communicate with the selected EFT system.

Note:

Also refer to the Oracle Retail EFTLink Security Guide for core specific actions to ensure secure configuration.

This guide consists of separate chapters for each available core; go to the pertinent section for each core to be installed. The following cores are supported:

• Adyen

• AJB FIPay

• Cayan

• Oracle Payment Interface (OPI)

• Pay by Link (PBL)

• PayPal

• Six Pay

• Solve Connect

• Tender Retail

• Verifone Ocius Sentinel

• Verifone Point (US)

• WorldPay

Miscellaneous Data Disclaimer

EFTLink along with some selected Cores, has the ability for additional data to be sent and received in a field called <MiscellaneousData>.

This can be used by System Implementers (SIs) and Payment Service Providers (PSPs) to pass additional data in the messages between Xstore and the Payment Providers, using custom code.

Typically, this is used to add directives which we can trigger different payment workflows. However, it can also be used to capture additional payment data for downstream processing for the Retailer's to use for reconciliation or financial purposes.

Under no circumstances should any PCI or potentially sensitive PII data be placed in this field. Oracle will not be responsible for any issues caused by integration changes made by SIs, Retailers and Payment Providers, that enable sensitive data to be added into this field.