# Troubleshooting

Resolve common Oracle Simphony POS+ integration issues.

## Overview

Use this page when Simphony can't reach POS+, payments fail at the terminal, or configuration values don't match between Unity Portal and Simphony EMC.

## Before you start

Confirm the basics:

- Castles terminal state is  in the Unity Portal.
- The POS+ adaptor type is Oracle SPI.
- The Simphony version is v19.1 or later (v19.9 recommended).
- [Network requirements](/guides/point-of-sale/pos-plus/oracle/setup#network-requirements) are met for your integration path.


## Configuration mismatches

| Symptom | Likely cause | Action |
|  --- | --- | --- |
| Simphony can't connect to POS+ | Wrong connectivity endpoint | Verify `https://{pedId}:8181/api/v1/pos-transactions-oracle` matches the PED endpoint supplied for your deployment. |
| Payment driver rejects the site | Site ID | Use `{merchantId}|{siteId}` with a pipe separator. For example, `MERCHANT1|SITE01`. |
| Workstation not recognised | POS ID mismatch | The Workstation Number in Simphony EMC must exactly match the POS ID in the Unity Portal. |
| Wrong site or merchant routed | Site ID longer than 15 characters | Shorten the Unity site ID before go-live. |


See [Unity to Simphony mapping](/guides/point-of-sale/pos-plus/oracle/setup#unity-to-simphony-mapping) and [Add and activate a device](/guides/point-of-sale/pos-plus/oracle/setup#add-and-activate-a-device).

## TLS and certificate issues 

TLS with certificate-based authentication is coming soon. Download the PXP root CA from the Unity Portal and configure it in Oracle Simphony to enable TLS when this becomes available. In the meantime, operators must set the workstation connection status to **HTTPS without validation**.

| Symptom | Likely cause | Action |
|  --- | --- | --- |
| TLS or certificate error from Simphony | Root CA not installed | Install the PXP root CA from the Unity Portal on the Simphony workstation or Android device. See [Root CA certificate](/guides/point-of-sale/pos-plus/oracle/setup#root-ca-certificate). |
| Connection worked, then failed after weeks | Client certificate renewal issue | Restart the POS+ app on the terminal; confirm the device is  and online. POS+ renews certificates automatically. |
| Trust errors after environment change | Wrong root CA for environment | Confirm that the staging or production root CA matches the Unity environment. |


POS+ presents the client certificate and Simphony validates it. You don't manage terminal certificates manually under normal operation.

## Network and connectivity

| Symptom | Likely cause | Action |
|  --- | --- | --- |
| Simphony timeout reaching PED | Port `8181` blocked | Allow inbound HTTPS on `8181` from the Simphony workstation to the Castles terminal. |
| Pay at Counter — PED unreachable | Different subnets or firewall | Confirm the Windows PC and PED can ping each other on the local network. |
| Pay at Table — Client can't sync | Port `8080` blocked | Allow bidirectional `8080` between the Android device and the back-office Simphony host, if used. |
| Pay at Table — Local SPI failure | Wrong local endpoint | Confirm the connectivity endpoint matches the All-in-One value supplied during onboarding (`https://{pedId}:8181/api/v1/pos-transactions-oracle`). |


See [Network requirements](/guides/point-of-sale/pos-plus/oracle/setup#network-requirements).

## Device and terminal issues

| Symptom | Likely cause | Action |
|  --- | --- | --- |
| POS+ app not accepting payments | Device not activated | Complete [Add and activate a device](/guides/point-of-sale/pos-plus/oracle/setup#add-and-activate-a-device). The state must be . |
| Settings not applied | Device offline at activation | Connect the terminal to the internet and reopen POS+ so the device downloads Portal settings. |
| Wrong payment flow | Wrong adaptor type | Set *POS+ adaptor type* to **Oracle SPI**. |


## Pay at Table-specific issues

| Symptom | Likely cause | Action |
|  --- | --- | --- |
| Simphony Android client fails to load | Version mismatch with EMC | Android client version must match the version configured in EMC for the property. |
| Workstation not listed on device | EMC workstation not created | Create the workstation in EMC, enable **Option Bit 68 — Third Party Managed Device**, and match **POS ID** in Unity. |
| Service Host errors | Wrong Service Host IP | Set **Service Host** to the **Android device IP**, not the back-office server. See [Pay at Table](/guides/point-of-sale/pos-plus/oracle/pay-at-table#service-host). |


## Transaction and acquirer issues

| Symptom | Likely cause | Action |
|  --- | --- | --- |
| Void not available | Acquirer limitation | Confirm void eligibility for your acquirer in [Supported capabilities](/guides/point-of-sale/pos-plus/oracle/how-it-works#supported-capabilities). See [Pay at Counter](/guides/point-of-sale/pos-plus/oracle/pay-at-counter#void) or [Pay at Table](/guides/point-of-sale/pos-plus/oracle/pay-at-table#void). |
| DCC not offered | Acquirer or device setting | Confirm DCC eligibility in [Acquirers](/guides/point-of-sale/pos-plus/oracle/how-it-works#acquirers) and enable DCC in Unity. See [Dynamic currency conversion](/guides/point-of-sale/pos-plus/dcc). |
| Card scheme declined | Acquirer routing | Confirm scheme support in [Card schemes](/guides/point-of-sale/pos-plus/oracle/how-it-works#card-schemes). |