Configuring the SPI Payment Driver

To add the SPI driver for the first time, or to update an existing property, revenue center, or zone from OPI to using SPI:

  1. Select the Enterprise, property, or revenue center, click Setup, and then click Payment Drivers.

    If multiple properties exist and you are configuring one property or revenue center to use SPI, select the property or revenue center that will use SPI.

  2. Insert a new Payment Driver record named SPI, and then double-click the record to open it.
  3. On the General tab, select 26 - Secure DLL Configuration as the Content Type, click Import from a file, browse to [Drive Letter]:\MICROS\Simphony2\EgatewayService\handlers\OPIPayment.dll, and then click Open.
  4. On the Configuration subtab, enter information in the following fields:

    Table 12-5 Configuration Fields

    Field Description

    Description

    Enter a description for the driver (for example, SPI).

    Display Name

    Enter a display name for the driver (for example, SPI).

    Currency Code

    Enter or verify the existing ISO numeric three-digit currency code for the country. (This value can only be set when SPI Interface = True.)

    Enable Quick Chip

    Set the value to True when using the quick chip feature. (This value can only be set when SPI Interface = True.)

    Ensure that your PSP supports quick chip before you enable this feature. Quick chip lets the guest swipe or dip a credit card at the beginning of a fast transaction while the workstation operator enters the menu items.

    The system must allow fast transactions by enabling option 15 - Allow Fast Transactions in the RVC Parameters module.

    Merchant Number

    Enter the Merchant ID.

    Host Timeout

    Enter the timeout value in seconds. This is the amount of time that the host waits for a response from the PSP. The default timeout value is 180 seconds.

    Pass Phrase

    Leave this field blank for SPI.

    Primary Host

    Enter the URL for the PSP endpoint.

    For example, in Terminal Mode this is http://PEDIPAddress:Port. In Middleware Mode, this is http://MiddlewareIPAddress:Port. If the IP address for each PED is different (network/wireless PEDs in Terminal mode), you need to create workstation devices to enter each POS client’s PED’s IP address individually.

    If the Security Settings use HTTPS, ensure that the Primary Host field shows https. This is based on the Security settings below.

    SPI Interface

    Set the value to True when using the SPI driver.

    This is helpful in preparation for an upgrade or switch from OPI to SPI, when you have a property with many POS clients that each require a certificate. While the property is still operating on OPI and the payment driver remains set to SPI Interface = False, each client SPI device can be created and certificates loaded. As long as the payment driver is not set to SPI, the device record is ignored. When the property is ready to switch to SPI, you simply need to set the SPI Interface to True.

    Validate XML Message Against Schema

    To validate the format of existing messages that are sent to the PSP against the schema, set the value to True. (This value can only be set when SPI Interface = True.)

    Security

    You can load the certificate into the payment driver or the workstation device, depending on the communication method and connection between the POS client and the PED. The certificates are installed on the POS clients as part of the DBSync process.

    • Security Settings: Select the appropriate option:

      • Use Http Only

      • Use Https with No Certificate Validation

      • Use Https with Certificate Validation (one- or two-way authentication)

        • For one-way authentication, the PSP provides the private key for the server certificates, which must be distributed to all POS clients.

        • For two-way authentication, the client certificates with passwords are also issued by the PSP for each Simphony POS client.

    • Load Server Certificate: Click the ellipsis button, select the server certificate, and then click Open.

    • Load Client Certificate: Click the ellipsis button, select the client certificate, enter the password when prompted, and then click Open.

    • Delete Certificates: To delete a certificate, select Do Not Delete, Delete All Certificates, Delete Server Certificate, or Delete Client Certificate. Confirm with Yes or No.

    The Oracle Hospitality Simphony Security Guide contains more information about the certificates.

  5. Click Save.