Before development starts, settle which Simphony payment interface your integration will use, who supplies the payment service provider (PSP) side, and which parts of the flow you own. Oracle documents two interfaces for Simphony card payments, the Simphony Payment Interface (SPI) and the Oracle Payment Interface (OPI). Versions, access, and prerequisites change, so confirm them against current Oracle documentation and your Oracle contacts.

This article is independent guidance. It does not imply an official partnership with Oracle or compatibility with every Simphony version or configuration.

What Oracle documents

▸ SPI: a component of the Simphony client application that builds messages for the payment side and handles the replies on the workstation. Oracle's page says a PSP supplies the payment side, and that it can be a payment terminal or a middleware layer. See The Simphony Payment Interface (SPI).

▸ OPI: lets Simphony take card payments through PSPs using a single payment driver. Oracle's page says Simphony and OPI do not handle or store cardholder data, the PSP returns a token, and end-of-day settlement can be automated. It also names required OPI version and patch levels, with drivers obtained through Oracle support. See The Oracle Payment Interface (OPI).

Oracle's pages differ between Simphony releases, so read the documentation for the release you actually run.

Questions to resolve first

Area Question Why it matters
Interface SPI, OPI, or another route Oracle supports for this deployment? Sets the driver, configuration, and who builds what
Versions Which Simphony and interface versions run at each property? Behavior and prerequisites vary by version
Access Do you have access to Oracle documentation, drivers, and support? Drivers and patches come through Oracle channels
PSP Which PSP or middleware is contracted, and who owns that relationship? The PSP side sits outside Simphony
Devices Which terminals and handhelds are used, and does the PSP support them? Hardware must match PSP support
Transaction flows Sale, refund, void, pre-authorization, tip adjustment, split checks, offline behavior? Each flow needs design and tests
Tipping Where is the tip entered and when does it post? Tip handling differs by flow
Refunds Who can issue refunds and from which screen? Permissions and audit trail
Settlement Automatic or manual, and who reconciles? Oracle's pages describe configurable settlement
Multi-property How many properties, and how do their configurations differ? Drives rollout effort

Responsibility boundaries

Confirm each owner in writing. This table is a starting point, not a statement of who owns what in your deployment.

Layer Typical owner to confirm
Simphony configuration (drivers, modules, tenders, buttons) The operator or its Simphony service provider
Card processing and PSP services The PSP
Payment terminals and handhelds The PSP or hardware vendor
Integration code or middleware The integrator
Upgrades and ongoing compatibility A named owner for each layer

Pilot and rollout

▸ Pilot at one property first and validate sales, refunds, voids, tips, and settlement.

▸ Compare settlement and reporting against the PSP's records before expanding.

▸ Roll out in waves, with a rollback plan for each.

▸ Plan for ongoing compatibility. Simphony and interface updates can change behavior, so assign someone to review release notes and retest.

Scoping checklist

☐ Interface and version confirmed for every property.

☐ Oracle documentation and driver access confirmed.

☐ PSP and middleware owner named, with contacts.

☐ Terminal and handheld models confirmed with the PSP.

☐ Transaction flows listed, including tipping and refunds.

☐ Settlement and reconciliation owner named.

☐ Pilot property and success criteria chosen.

☐ Support and upgrade owners named per layer.

FAQs

Is this an official Oracle integration?

No. This is independent guidance. Oracle decides what it supports, so confirm with Oracle.

Will it work on every Simphony version?

Do not assume so. Interface behavior and requirements depend on the release and the patch level.

Do we need a PSP?

Oracle's documentation describes card processing as handled by a PSP, so confirm which one your deployment uses.

Who is responsible when a payment fails?

Define it per layer before launch: Simphony configuration, PSP, terminal, and integration code.

Next step

If you can share your Simphony versions, PSP, devices, and property count, we can help scope the integration and flag the questions above. Start at the integration page.

Sources

▸ Oracle: The Simphony Payment Interface (SPI)

▸ Oracle: The Oracle Payment Interface (OPI)