Overview
In Oracle Payment Interface (OPI) Cloud, each payment terminal used for card payments is registered as a credit card terminal, so that the interface can identify the device by its terminal ID and its physical location. This article explains how to add a credit card terminal in OPI Cloud: which details to enter and where to find the terminal ID.
Applies to
| Product | Juno Hospitality Suite |
| Integration | Oracle Payment Interface (OPI) Cloud |
| Version | Oracle Cloud |
| Audience | Property and OPI administrators |
What you'll achieve
After completing these steps, the payment terminal is registered in OPI Cloud for the correct property, with its terminal ID, a label that identifies where it is located, and a device area.
Before you start
- You need access to the Administration menu in OPI Cloud.
- Have the terminal ID ready. This is the number provided by the terminal vendor. It is also shown on the card reader device itself.
- Decide on a label for the terminal that describes its physical location, so you can recognise it later in a list of devices.
- Know which device area the terminal belongs to.
Operational steps
1. Open Credit Card Terminals
- From the Administration menu, go to Administration | Interfaces | Interface Devices | Credit Card Terminals.
- Select New.
2. Enter the terminal details
- Property: enter or select the property.
- Terminal ID: enter the terminal ID number provided by the vendor. You can also find this number on the card reader device. OPI uses this value to populate the WSNum tag in the OPERA/IFC8 messages.
- Terminal Label: enter a label or description that identifies the physical location of the terminal. It helps you recognise the terminal when it appears in a list of devices.
- Device Area: link the device to an area.
- Select Save.
Expected result
The credit card terminal is saved and can be recognised by its Terminal Label in the list of devices.
Need more help?
If the terminal does not appear or does not behave as expected, please contact your integration partner.
Comments
0 comments
Article is closed for comments.