# Pay at Table

Run Oracle Simphony and POS+ on the same Castles S1F4 Pro device for mobile table service.

## Overview

Pay at Table (All-in-One) combines the Oracle Simphony Android client and PXP POS+ on a single Castles S1F4 Pro. Staff take orders and payments at the table without a separate payment terminal or fixed checkout.

The Oracle SPI client and POS+ share one device. Simphony sends payment requests locally to POS+ using the same SPI adaptor as Pay at Counter. Authorisation runs through Unity to your configured acquirer.

Device requirement
All-in-One is supported on Castles S1F4 Pro only. The Oracle SPI Android client needs additional processing capacity and isn't certified on S1F2 or S1P2.

## Before you start

Confirm you have the following:

- Castles S1F4 Pro with POS+ activated
- Oracle Simphony v19.1 or later (v19.9 recommended)
- A copy of the Oracle Simphony Android client from your venue or Oracle partner
- Unity terminal with the POS+ adaptor type set to Oracle SPI


## Device provisioning

Provision each S1F4 Pro as follows:

1. Provide the Oracle Simphony Android client APK to PXP.
2. PXP signs the client and uploads it to **Castles CASHub** (terminal management).
3. The signed APK is pushed to your S1F4 Pro devices through CASHub.
4. Activate POS+ on each device using [Add and activate a device](/guides/point-of-sale/pos-plus/oracle/setup#add-and-activate-a-device).


All-in-One distribution through CASHub depends on your Oracle and Castles onboarding process. Contact PXP to confirm signing and device push steps for your deployment.

## Simphony configuration

Configure the same Unity values as [Pay at Counter](/guides/point-of-sale/pos-plus/oracle/pay-at-counter):

| Simphony field  | Unity / PXP value |
|  --- | --- |
| Site ID | `{merchantId}|{siteId}` |
| Workstation Number | POS ID from the Unity Portal |
| Connectivity endpoint | `https://{pedId}:8181/api/v1/pos-transactions-oracle` (use the local All-in-One endpoint value from onboarding) |
| TLS trust  | PXP root CA certificate. In the meantime, set the workstation connection status to **HTTPS without validation**. |


### Android workstation (EMC)

Create and enable the Android workstation as follows:

1. In **EMC**, go to **Setup > Workstations** and create the workstation for the device.
2. Note the **Workstation ID** and enter it as the **POS ID** in the Unity Portal.
3. Open the workstation configuration.
4. Go to **Options > Hardware/Cash Drawer**.
5. Enable **Option Bit 68 — Third Party Managed Device**.
6. Save the workstation.


### Service Host

Under the workstation **General** tab, set **Service Host** to the **IP address of the Android device** (not the back-office server).

### Simphony client on device

Finish client setup on the device as follows:

1. Install the signed Simphony Android client on the S1F4 Pro (through CASHub or your deployment process).
2. Connect the client to your Simphony enterprise using credentials from your Oracle partner.
3. Select the workstation entry created for that device.
4. Confirm values match EMC and start Point of Sale.


The Simphony client version must match the version configured in EMC for your property. Mismatched versions prevent the client from loading.

## Transactions

Simphony initiates purchase, refund, and void. See [Supported capabilities](/guides/point-of-sale/pos-plus/oracle/how-it-works#supported-capabilities) for acquirer and device scope.

### Purchase

Purchase is the default payment flow. After the cashier completes the sale in Simphony, the customer presents their card on the S1F4 Pro.

Gratuity and mandatory service charges configured in Simphony are included in the SPI message. See [Gratuity and service charges](/guides/point-of-sale/pos-plus/oracle/gratuity-and-service-charges). If DCC is enabled, the customer may be offered a currency choice on the terminal. See [Dynamic currency conversion](/guides/point-of-sale/pos-plus/dcc).

Run a test purchase during [Setup](/guides/point-of-sale/pos-plus/oracle/setup#step-3-test) before go-live.

### Refund

The cashier initiates a refund in Simphony. POS+ processes it as a standalone refund through Unity.

### Void

The cashier selects void in Simphony for an eligible transaction.

Void support is acquirer-dependent. See [Supported capabilities](/guides/point-of-sale/pos-plus/oracle/how-it-works#supported-capabilities) and confirm void behaviour with your PXP account representative before go-live.

## Network

All-in-One may require connectivity between the Android device and a back-office Simphony host on port `8080`, in addition to local SPI traffic on `8181`. See [Pay at Table network requirements](/guides/point-of-sale/pos-plus/oracle/setup#pay-at-table-all-in-one).