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
 

3 Adyen

Operating Areas: Europe, US, Canada, Brazil, Hong Kong, Singapore, Malaysia, Australia, New Zealand

Supported Terminals

The following terminals are supported:

Verifone

Castles

The following table provides information relating to the compatibility of Xstore, EFTLink and Adyen 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 3-1 Adyen

Payment Terminal Function Subtype Oracle Payment Interface Retail Transaction Type Xstore Release Version EFTLink OPI Retail Core Release Version AdyenVOS Firmware

Sign On


-

15.0

-

-

Sign Off


-

15.0

-

-

Card Payment

Payment by Credit

01

15.0

17.0

1.XX

Payment by Debit

01

15.0

17.0

1.XX

Manual Authorization

37, 07

-

17.0

-

Installments

01


19.0.1

1.XX

Partial Authorization

01


17.0

-

eWallet

Shopper initiated on PED - EWallet button pressed on PED (Flow 1).

01


19.0

1.XX

eWallet

Cashier initiated with EWallet tender - QR code displayed on PED (Flow 2).

01


19.0

1.XX

Cashback

Cashback prompted on PED, return amount to POS

01

15.0

-

-

Check Payment / Check Verification

Payment by Check

51

17.0

18.0

-

Refund

Refund by Credit

03

15.0

17.0

1.XX

Refund by Debit

03

15.0

17.0

1.XX

Cardless Refund using OriginalRRN

03

16.0

17.0

1.XX

Cardless Refund using TransToken

03

16.0

19.0.1

1.XX

Reversal

Reversal of last transaction

04

15.0

17.0

1.XX

Reversal of a transaction within batch+

08

15.0

17.0

1.XX

Reversal of a refund transaction within a batch**

39

15.0

17.0

-

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

1.XX

Customer Display

Sale State Notification

43, 45

15.0

18.0

-

Card Swipe - non PCI Cards

Get card data

50

15.0

18.0

-

Customer Not Present

CVV2 / AVS / partial entry on PED

01

17.0

17.0

1.XX

Electronic Signature Capture

3 byte ASCII (3BA)

01

15.0

18.0

1.XX

Transaction Inquiry

Time out handling

20

-

17.0

1.XX

Abort

Abort in flight transaction

53

17.0

18.0

1.XX

Stored Value Cards (Gift Cards)

Redeem

30

16.0

18.0

1.XX

Redeem Reversal

31

16.0

18.0

1.XX

Cashback /Unload

32

16.0

18.0

1.XX

Load/Reload

28

16.0

18.0

1.XX

Refund

32

16.0

18.0

1.XX

Cash out (Close)

32

16.0.1

18.0

1.XX

Balance Inquiry

27

16.0

18.0

1.XX

Activate

29

16.0

18.0

1.XX

Activate and Load

29

16.0

18.0

1.XX

Activate Reversal

31

16.0

18.0

1.XX

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

-

Card Acquisition

Card Acquisition (Pre-read)

09

-

19.0.1

1.XX

Custom Forms

Terminal Display

67

*


18.0

-

Customer Question

60

*


18.0

1.XX

Phone Number Capture

62

*


18.0

1.XX

Email Address Capture

63

*


18.0

1.XX

Signature Capture

61

*


18.0

1.XX

Customer Buttons

65

*


18.0

1.XX

Display QR Code

68

*


18.0

1.XX

Cancel QR Code

69

*


18.0

1.XX


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

+ Adyen do not currently support receipts for void transactions. This is acceptable as all receipts OPIRetail receive are pre-certified.

** Adyen do not currently support refund reversal transactions due to the nature of their asynchronous platform. Xstore will send the directive to perform a refund reversal. This is a note to warn that this will always fail in the OPI integration with Adyen.