| Oracle® Retail EFTLink Validated OPI Partners Guide Release 19.0.1 F30037-04 |
|
 Previous |
Operating Areas: United States, Canada
Supported Terminals
The following terminals are supported:
Verifone MX915
Verifone MX925
Ingenico (all attended Tetra models)
Ingenico (all attended Telium Models)
The following table provides information relating to the compatibility of Xstore, EFTLink and Shift4 Payments, LLC 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 6-1 Shift4 Payments, LLC
| Payment Terminal Function | Subtype | Oracle Payment Interface Retail Transaction Type | Xstore Release Version | EFTLink OPI Retail Core Release Version | Shift4 Payments LLCUniversal Transaction Gateway (UTG) |
|---|---|---|---|---|---|
|
Sign On |
- |
15.0 |
- |
- |
|
|
Sign Off |
- |
15.0 |
- |
- |
|
|
Card Payment |
Payment by Credit |
01 |
15.0 |
17.0 |
5.0.0.3024 |
|
Payment by Debit |
01 |
15.0 |
17.0 |
5.0.0.3024 |
|
|
Manual Authorization |
37, 07 |
- |
17.0 |
5.0.0.3024 |
|
|
Instalments |
01 |
19.0 |
- |
||
|
Partial Authorization |
01 |
17.0 |
5.0.0.3024 |
||
|
Cashback |
Cashback prompted on PED, return amount to POS |
01 |
15.0 |
- |
- |
|
Transaction Inquiry |
Timeout Handling** |
20 |
- |
17.0 |
5.0.0.3024 |
|
Check Payment / Check Verification |
Payment by Check |
51 |
17.0 |
18.0 |
- |
|
Refund |
Refund by Credit |
03 |
15.0 |
17.0 |
5.0.0.3024 |
|
Refund by Debit |
03 |
15.0 |
17.0 |
5.0.0.3024 |
|
|
Cardless Refund using Token |
03 |
16.0 |
17.0 |
5.0.0.3024 |
|
|
Reversal |
Reversal of last transaction |
04 |
15.0 |
17.0 |
- |
|
Reversal of transaction within batch |
08 |
15.0 |
17.0 |
5.0.0.3024 |
|
|
Reversal of refund transaction within batch |
39 |
15.0 |
17.0 |
5.0.0.3024 |
|
|
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 |
- |
|
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 |
5.0.0.3024 |
|
Electronic Signature Capture |
3 byte ASCII (3BA) |
01 |
15.0 |
18.0 |
- |
|
Abort |
Abort in flight transaction |
53 |
17.0 |
18.0 |
- |
|
Stored Value Cards (Gift Cards) |
Redeem |
30 |
16.0 |
18.0 |
- |
|
Redeem Reversal |
31 |
16.0 |
18.0 |
- |
|
|
Cashback /Unload |
32 |
16.0 |
18.0 |
- |
|
|
Load/Reload |
28 |
16.0 |
18.0 |
- |
|
|
Refund |
32 |
16.0 |
18.0 |
- |
|
|
Cash out (Close) |
32 |
16.0.1 |
18.0 |
- |
|
|
Balance Inquiry |
27 |
16.0 |
18.0 |
- |
|
|
Activate |
29 |
16.0 |
18.0 |
- |
|
|
Activate and Load |
29 |
16.0 |
18.0 |
- |
|
|
Activate Reversal |
31 |
16.0 |
18.0 |
- |
|
|
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 |
- |
|
Customer Question |
60 |
* |
18.0 |
- |
|
|
Phone Number Capture |
62 |
* |
18.0 |
- |
|
|
Email Address Capture |
63 |
* |
18.0 |
- |
|
|
Signature Capture |
61 |
* |
18.0 |
- |
|
|
Customer Buttons |
65 |
* |
18.0 |
- |
|
|
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.
** Time out handling - The UTG time out setting will always be set to a value less than the OPIRetail setting which means OPIRetail will always get a response from the UTG. Therefore in production UTG will return one of the following response codes to OPIRetail:
90 - Cutoff In Progress
91 - Host or Switch Unavailable, Card Issuer Signed Off, Card Issuer Timed Out, Card Issuer Unavailable
92 - Unable to Route Transaction
The standard behavior for UTG would be to expect a transaction inquiry [Type 20] message but OPI Retail will treat these response codes as a decline in line with the OPI Specification. It has been agreed with Oracle Retail and Shift4 Payments LLC that Shift4 Payments LLC will be responsible for voiding the transaction in this scenario. This means the UTG will send a void for the payment. Shift4 Payments LLC provided evidence to support that this void is executed. This was enough to convince Oracle Retail that it would not be possible to see a double charge scenario for those decline reason codes.
