Oracle EFTLink and Xstore compatibility

This video provides an in-depth guide to *EFTLink and Xstore compatibility*, designed for technical professionals who manage, integrate, or support retail payment solutions. 👥 *Who Should Watch?* System administrators, operations staff, database administrators, system analysts, programmers, integrators, and implementation teams. ⚙️ *Key Topics Covered:* 1️⃣ *Compatibility Overview* * EFTLink is backwards compatible with earlier Xstore versions. * Avoid mixing older EFTLink (Client/Server) with newer Xstore releases—always use the latest EFTLink maintenance release. * JRE (Java Runtime Environment) guidance: Xstore and EFTLink Server should ideally run on the same JRE. If using different JRE versions (e.g., Xstore JRE 1.8 with EFTLink v25 JRE 21), TLS1.2 must be enabled on both client and server. * EFTLink client library must be added into Xstore\lib\ext for communication. 2️⃣ *Core Compatibility by Region* * *International Cores*: OPI Retail, PayByLink. * *US Region Cores*: AJB FiPay, Cayan, Tender Retail, Verifone Point US. * *European Region Cores*: Six Payment Services, TLG SolveConnect, Verifone Ocius Sentinel, WorldPay. * Each core includes detailed payment terminal functions (Card Payment, Refund, Stored Value Cards, EWallet, Reconciliation) mapped to Xstore and EFTLink release versions. 3️⃣ *Feature Compatibility by GA Release (v15.0 → v25.0)* * Coverage of major features introduced per release. * Includes: Logon/Logoff, Sales (DCC, Cashback, Customer Not Present, Tokenization, Installments, Invoice Payments, Cell Phone Recharge, PLCC, Pre-Auth), Refunds, Reversals, Stored Value Cards, Custom Forms, and more. 📌 If a function is not listed, it means it does not exist in the Core EPS API or Xstore base.