Creating and configuring EFT Property through OPERA Cloud

The OPERA Cloud users with the CCCONF role can access OPERA Cloud and create an EFT property interface for a new property. Once the property is created, activate the OPI Cloud credit card processing parameter for credit card integration, and connect to the OPI Cloud Service. This will launch the OPI Cloud Tenant Configuration portal.

Note:

• If there is an existing EFT interface, it is recommended to delete the old interface and create a new one instead of editing the existing one.

• While creating an EFT property, the IFC8 required fields such as Machine and Version are mandatory, however these are not required for OPI Cloud. When the OPI Cloud Credit Card Processing parameter is active, these fields will be no longer be mandatory and can be left blank.

1. Log in to OPERA Cloud using the URL provided.

2. Enter your User Name and Password in the fields provided.

3. From the Administration menu, go to Interfaces | Property Interfaces. ClickNew to add the configuration for a new EFT interface.

4. Enter the following options:

   1. Property: Enter or select the property from the list. For example, OPICloudProp

   2. Interface Type: Select the interface type as ‘EFT’ from the list.

   3. Product Code: Enter the product ID of the validated system. For example, OPI.

   4. IFC8 Product Code: Will auto-populate based on the Product Code. For example, FIAS_OPI

   5. Name: Enter the display name of the system for identification. For example, EFT Interface.

   6. Cashier ID: Select the cashier id for the interface from the list. For example, 8.

   7. Path ID: Enter the Path ID of the interface. In most cases this is a 1. Only if the vendor is supporting multi-property with one interface, is there a need for more. If setting up a multi-property, the first property must be defined as 1, and all subsequent properties must follow sequentially and with no gaps. For example, 1.

   8. Machine: This field is not applicable as IFC8 is not used.

   9. Timeout: Enter a timeout value in seconds on how long the UI will wait for response on outbound messages (Room key and credit card transaction requests). For example, 240.

   10. Version: This field is not applicable as IFC8 is not used.

       
       
       

5. Click Save to add the configuration for a new EFT interface.

6. Once the EFT property interface details are created, go to Interfaces | Property Interfaces | edit EFT IFC | General Information.

   1. Select the check box to enable the Handle Night Audit / End of Day Commands.

   2. Select the check box to enable the CC Vault Function.

      Note:

      You cannot view theOPI Cloud Credit Card Processing parameter until the EFT property interface details are created and the CC Vault Function check box is enabled in the General Information panel.

   3. Select the check box to enable the Regular Transaction.

   4. The Token Provider URL should be in the format: https://OPIHostIP.example.com

      Note:

      The Token Provider URL is only required to be completed if the customer is using legacy integrations such as OXI or OWS.

   5. The Token Provider Protocol should be set to One Way Handshake which means for OPI only server side certificate is required.

   6. Click Save to save the details.

   7. Go to Interfaces | Property Interfaces | edit EFT IFC | Custom Data panel.

   8. The HTTP_USERNAME and HTTP_PASSWORD should be set at the Token proxy service side that allows communication with the token proxy service URL.

      Note:

      HTTP credentials are only required to be completed if the customer is using legacy integrations such as OXI or OWS

   9. OPERA Cloud uses the VAULT_CERT_CHAIN_CODE for the certificate lookup and should be populated with what was entered during the OPI configuration for OPERA Cloud.

   10. The VAULT_ID should be set to the same value as the auto populated IFC number.

   11. The WALLET_PASSWORD is not used for One Way Handshake.

   12. The VAULT_MAX CC PROCESSED is set to what the Payment Partner can support for the number of rows sent in one Token (GetID/GetCC) request. This is used during the bulk tokenization process and when multiple folio windows exist on OPERA Reservations. 50 is the default used when nothing is set here.

   13. Click Save.

       Note:

       The added credit card details will be displayed on the Payment Instructions panel, or confirmation on adding the card will be displayed only when the EFT interface has data in the Custom Data panel.

   14. Go to Interfaces | Property Interfaces | edit EFT IFC | Translation panel. Click New.

   15. Select theOrigin Code as the DEFAULT code to run an EFT interface.

   16. Enter the Merchant Id . The Merchant ID is mandatory while creating an EFT interface and it should match with the Merchant ID within the OPI Cloud Tenant Configuration. The Merchant Id is a combination of OPERA Chain | Property Code. For example, FIRST | FINPROP.

   17. Click Save.

       
       
       

7. You can activate the OPI Cloud Credit Card Processing parameter once the control is available. See Activating OPI Cloud Service for more information.

   Note:

   You cannot view the Configure link if the OPI Cloud Credit Card Processing parameter is not activated.
8. Once the OPI Cloud Credit Card Processing parameter is active, click Configure under OPI Configuration. This will launch the OPI Cloud Tenant Configuration portal where you can configure the Tenant information and map the Tenant with the PSP endpoints for each Transaction type (Credit/Debit Card or Token Exchange) to perform end-to-end transactions.
   
   
   

   
   
   

• Configuring CHIP AND PIN (EMV)
  
• Configuring OPERA Controls for Settlement at Checkout and Chip and Pin
  
• Activating OPI Cloud Service