# Pay at Counter

Run Oracle Simphony on a Windows workstation with a separate Castles payment terminal.

## Overview

Pay at Counter is the standard Simphony POS+ layout for fixed checkout positions. Oracle Simphony runs on a Windows PC. A payment terminal on the same network runs POS+ and captures the card payment.

Communication uses HTTPS on port `8181`. POS+ presents a TLS client certificate, then Simphony validates it using the PXP root certificate you install during setup. TLS with certificate-based authentication is coming soon; in the meantime, Operators must set the workstation connection status to **HTTPS without validation**. See [How it works](/guides/point-of-sale/pos-plus/oracle/how-it-works) for the payment sequence.

## Supported devices

Pay at Counter is certified on these Castles models:

| Device | Supported |
|  --- | --- |
| Castles S1F2 |  |
| Castles S1F4 Pro |  |
| Castles S1P2 |  |


See [Devices](/guides/point-of-sale/pos-plus/devices) for specifications. Acquirer limits apply; see [Acquirers](/guides/point-of-sale/pos-plus/oracle/how-it-works#acquirers).

## Simphony configuration

Configure these values in Oracle EMC so they match Unity:

| 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` |
| TLS trust  | PXP root CA certificate. In the meantime, set the workstation connection status to **https without validation**. |


PXP supplies the `{merchantId}`, `{siteId}`, POS ID, and root CA when you go live. The payment driver Site ID must use the pipe format exactly. For example, `MERCHANT1|SITE01`.

The Workstation Number in Simphony must match the POS ID assigned to that terminal in the Unity Portal.

## 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 payment terminal.

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 is initiated from Simphony.

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.