Go to primary content
Oracle® Retail EFTLink Validated OPI Partners Guide
Release 20.0.1
F44379-05
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

4 Aurus

Operating Areas: USA, Canada, UK, Mexico, Austria, Belgium, Czech Republic, Denmark, Finland, France, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Poland, Portugal, Spain, Sweden, Switzerland, Turkey, China*, and Hong Kong*.

* China and Hong Kong are restricted to EWallet tender options.

Supported Terminals

The following terminals are supported:

Verifone

Ingenico

The following table provides information relating to the compatibility of Xstore, EFTLink and Aurus for payment terminal functionality in the context of OPI transaction types.


Note:

Where there is no version noted for Xstore it implies that the functionality is driven by EFTLink and the OPI Retail Core. Xstore is not required to implement any additional API feature.

Table 4-1 Aurus

Payment Terminal Function Subtype Oracle Payment Interface Retail Transaction Type Xstore Release Version EFTLink OPI Retail Core Release Version Aurus Shield Software

Sign On


-

15.0

-

-

Sign Off


-

15.0

-

-

Card Payment

Payment by Credit

01

15.0

17.0

v2X.XXX

Payment by Debit

01

15.0

17.0

v2X.XXX

Manual Authorization

37, 07

-

17.0

v2X.XXX

Instalments

01

-

19.0

-

eWallet

Cashier initiated with EWallet tender - ScanQR code displayed on shopper's phone (Flow 3).

01

-

19.0

v2X.XXX

Cashback

Cashback prompted on PED, return amount to POS

01

15.0

-

v2X.XXX

Check Payment / Check Verification

Payment by Check

51

17.0

18.0

v2X.XXX

Refund

Refund by Credit

03

15.0

17.0

v2X.XXX

Refund by Debit

03

15.0

17.0

v2X.XXX

Cardless Refund using Token

03

16.0

17.0

v2X.XXX

Reversal

Reversal of last transaction

04

15.0

17.0

v2X.XXX

Reversal of last transaction within batch

08

15.0

17.0

v2X.XXX

DCC (currency conversion)

Foreign exchange tender amount, rate, currency code

Functionality that is driven through the Core plugin by virtue of the <DeviceRequest> / <DeviceResponse> API

01, 03, 07, 20

17.0

18.0

v2X.XXX

Combined EFT/Tax Receipts

Defer customer copy to <CardServiceResponse>


16.0

17.0

-

Customer Display

Sale State Notification

43, 45

15.0

18.0

v2X.XXX

Card Swipe - non PCI Cards

Get card data

50

15.0

18.0

v2X.XXX

IP PED

Support for ethernet/wireless connected PED device

-

NA

17.0

v2X.XXX

Customer Not Present

CVV2 / AVS / partial entry on PED

01

17.0

17.0

v2X.XXX

Electronic Signature Capture

3 byte ASCII (3BA)

01

15.0

18.0

v2X.XXX

Abort

Abort in flight transaction

53

17.0

18.0

v2X.XXX

Stored Value Cards (Gift Cards)

Redeem

30

16.0

18.0

v2X.XXX

Redeem Reversal

31

16.0

18.0

v2X.XXX

Cashback /Unload

32

16.0

18.0

v2X.XXX

Load/Reload

28

16.0

18.0

v2X.XXX

Refund

32

16.0

18.0

v2X.XXX

Cash out (Close)

32

16.0.1

18.0

v2X.XXX

Balance Inquiry

27

16.0

18.0

v2X.XXX

Activate

29

16.0

18.0

v2X.XXX

Activate and Load

29

16.0

18.0

v2X.XXX

Activate Reversal

31

16.0

18.0

v2X.XXX

Reconciliation

Reconciliation with Closure functionality that is typically available via the hardware maintenance menu on the Xstore POS client, that is, uses the <ServiceRequest> / <ServiceResponse> API

10

15.0

17.0

-

Custom Forms

Terminal Display

67

*


18.0

v2X.XXX

Customer Question

60

*


18.0

v2X.XXX

Phone Number Capture

62

*


18.0

v2X.XXX

Email Address Capture

63

*


18.0

v2X.XXX

Signature Capture

61

*


18.0

v2X.XXX

Customer Buttons

65

*


18.0

v2X.XXX

Display QR Code

68

*


18.0

-

Cancel QR Code

69

*


18.0

-


* Denotes that the system integrator would have to implement this functionality in the Xstore custom overlay.