1 Oracle Retail EFTLink

This document highlights the major changes for Release 26.0.0 of Oracle Retail EFTLink.

Overview

Oracle Retail EFTLink provides the payment foundation for Xstore Point of Service and is a middleware product that enables Oracle to remove Xstore Point of Service from the costly and frequently changing Payment Application Data Security Standard (PA-DSS).

As retailers continue to investigate the most cost effective ways in which they can become compliant with PCI standards, EFTLink provides a tested and mature approach that is already deployed in over ten countries. The solution has been adopted as the strategic approach for Xstore Point of Service and enables the rapid support of payment solutions in new markets by working with payment providers who are local and/or offer an extensive international network.

EFTLink uses an industry-standard interface to the point of service and then translates the messages to the relevant format provided by the payment provider, enabling the POS to be outside of the payment scope.

Functional Enhancements

The following is a list of functional enhancements made to EFTLink since the last release.

  • Support forXstore/EFTLink communication in a new WebSocket mode (the existing TCP socket mode is fully supported). WebSocket mode is only supported in certain situations, most notably with Xstore release 26.0 in combination with the OPIRetail and/or PayByLink cores.

OPI Retail

  • The OPI Retail core allows certain transaction requests to be routed to an OPI partners cloud implementation. This will be useful for transactions that do not necessarily require a local terminal, such as Pay By Link transactions.
  • The OPI Retail core now supports an enhanced custom form providing OPI partners with more flexibility and configuration for the forms displayed on the terminal/PED.
  • The OPI Retail core has the capability to automatically request the custom form from a third-party Customer feedback API endpoint during a payment flow.
  • The OPI Retail core has added tags and identifiers to support EBT transaction flows, new E-wallet types, and enhanced entry mode mapping.
  • The OPI Retail core has changes that improve validation, and proactively addresses invalid data returned from OPI partners.
  • The OPI Retail core now uses JAXB when working with OPI request and response messages. Custom extensions of the OPI Retail core may require small modifications as a consequence of this. Please refer to the OPI Core Extensibility Guide.

Related Documents

For more information, see the following documents in the Oracle Retail EFTLink 26.0.0 documentation set:

  • Oracle Retail EFTLink Core Configuration Guide

  • Oracle Retail EFTLink Framework Advanced Features Guide

  • Oracle Retail EFTLink Framework Installation and Configuration Guide

  • Oracle Retail EFTLink Security Guide

  • Oracle Retail EFTLink Rest API Guide

  • Oracle Retail EFTLink Xstore Compatibility Guide

  • Oracle Retail EFTLink Validated Partners Guide

  • Oracle Retail EFTLink Validated OPI Partners Guide