The Simphony Payment Interface (SPI)

The SPI is the new, resilient version of the OPI. It is part of the Simphony client application and formats the individual messages for the PSP (terminal or middleware) and processes the responses for the client directly. This eliminates the need for the OPI server and avoids traffic over the LAN on POS clients that have a PIN Entry Device (PED) attached.

The following links provide more information on Simphony/SPI:

SPI Architecture: https://docs.oracle.com/cd/F10429_01/doc.182/f10213/c_payments_spi_architecture.htm#SIMCG-SPIArchitecture-DA81B9D8

OPI Architecture: https://docs.oracle.com/cd/F10429_01/doc.182/f10213/c_payments_opi_architecture.htm#SIMCG-OPIArchitecture-D2CB9A39

OPI Information in the Simphony Configuration Guide: https://docs.oracle.com/cd/F10429_01/doc.182/f10213/c_payments_opi.htm#SIMCG-TheOraclePaymentInterfaceOPI-10678CB4

SPI Information in the Simphony Configuration Guide: https://docs.oracle.com/cd/F10429_01/doc.182/f10213/c_payments_spi.htm#SIMCG-TheSimphonyPaymentInterfaceSPI-DA817CDC

Data Flow Process

  1. User initiates payment functionality, such as authorization or finalization in Ops.

  2. SPI establishes a secure outbound connection with a Pin Entry Device (PED) or middleware.

    Appendix D in the Simphony Security Guide provides more information: https://docs.oracle.com/cd/F10429_01/doc.182/f10218.pdf.

  3. SPI submits required transaction data (check information, amount).

  4. PED prompts patron to swipe/dip/tap card, may prompt for tip/PIN.

  5. PED processes payment by submitting CC data and payment request to PSP host.

  6. PSP host responds with approval and returns token data back to PED.

  7. PED/middleware returns response message to SPI through connection established in step 2. Response message includes token, transaction references and print data. Transaction data is stored in check detail.

  8. Communication logs (communication in steps 3 and 7) are stored on each client.

Steps 4-6 are the only area where credit card data is being handled. Steps 4-6 are outside of Simphony and the sole responsibility of the PSP. Encryption of data and communication channels vary by PSP and should be considered when choosing a PSP.

The following figure shows an architecture diagram:


Image file shows an architecture diagram for SPI

The following figure shows a sample response received by SPI:


Image shows an API response received by SPI