Support for Simphony Payment Interface (SPI)
The Oracle Hospitality Simphony Configuration Guide contains more information about the SPI and its configuration.
The Oracle Hospitality Simphony POS User Guide contains more information about quick chip usage with fast transactions, and about performing a Mail Order Telephone Order (MOTO) transaction using the POS client.
The Oracle Hospitality Simphony Security Guide contains more information about the certificates.
Simphony version 18.2 introduces a resilient and lighter version of the Oracle Payment Interface (OPI), called Simphony Payment Interface (SPI). In the SPI, the business logic and communication layer that in OPI are handled by the OPI server have been moved into the POS client, eliminating the need for the OPI server. If a POS client has a PIN Entry Device (PED) attached, it can process payments independently from the LAN.
Communication Methods
The SPI can be deployed using one of the following connection methods: Terminal mode or Middleware mode. In Terminal mode, the mapping of a POS client to a PED is configured in EMC. In Middleware mode, the payment service provider (PSP) provides a middleware application that handles the mapping of a POS client to a PED and each POS client contacts the middleware application.
Configuration
You configure the SPI driver in the EMC, and deploy it through CAL. You can configure the SPI at the Enterprise, zone, property, and/or revenue center levels in the Payment Drivers module, and you can override the SPI configuration to set client-specific values at the workstation level in the Workstations module. The Payment Drivers module has been enhanced to include the SPI settings.
Current OPI Users
If you are currently using the Oracle Payment Interface (OPI), you will not experience changes as Simphony can run SPI and OPI together at the same property. The OPI and SPI use the same OPIPayment.dll file.
Quick Chip 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 existing logs and PaymentInterfaceLogViewer.exe tool have been enhanced to incorporate the quick chip transaction request and response messages.
Mail Order Telephone Order (MOTO) Feature
The SPI also supports a new feature called Mail Order Telephone Order (MOTO), which is typically used by merchants for call-in, online, or mail orders. MOTO is considered a “card not present” transaction, meaning that the credit card is not available to be swiped or inserted into the PED at the time of the transaction, nor to compare signatures. PEDs typically do not accept manual card data entry, although some may allow the workstation operator to do so when electronic reading of the card fails multiple times. MOTO allows the workstation operator to initiate a transaction using a function key from the payment screen so that the PED lights up and accepts the manual entry immediately (rather than a card swipe or dip). The MOTO feature is available if the PSP supports it.
Parent topic: Features and Updates