# About device settings

Learn about the different settings available and their default values.

## Overview

A device's settings are configured in the Unity Portal when you first set up a new POS. They're then automatically downloaded to the device when it first connects.

You can update a device's settings in the Portal at any time and the modified settings will automatically be updated on the device.

Oracle Simphony uses TLS certificate authentication for SPI payment flows. Set *POS+ adaptor type* to **Oracle SPI**. Other Unity Portal device settings (e.g., example host URLs or status packet options) may still appear in the Portal; confirm with PXP which settings apply to your Simphony deployment. TLS with certificate-based authentication is coming soon; in the meantime, Operators must set the workstation connection status to **HTTPS without validation**.

When you add a device for Oracle Simphony, set *POS+ adaptor type* to **Oracle SPI** and note the **POS ID** for Simphony EMC. See [Add and activate a device](/guides/point-of-sale/pos-plus/oracle/setup#add-and-activate-a-device).

## General settings

### POS settings

| Name | Description |
|  --- | --- |
| Status | The current status of the POS device. Must be  before go-live. |
| POS ID | The unique identifier for the point-of-sale device. This is set at device creation and can't be changed later. For Oracle Simphony, this must match the Simphony **Workstation Number**. |
| POS+ adaptor type | How the terminal receives payment requests. Set to **Oracle SPI** for Oracle Simphony integrations. |
| Device model | The device model. |
| Serial number | The serial number of the device. |
| Communication protocol | The communication protocol used to transfer data to and from the device. This can be `TCP` or `HTTP`. Confirm with PXP whether this applies to your Simphony deployment. |
| Communication endpoint | The URL that PXP should communicate with. For Simphony SPI, Simphony connects to the terminal using the connectivity endpoint configured in EMC. Confirm with PXP whether this Portal field applies to your deployment. |
| Commercial model | The commercial model. This can be `One-time fee`, `Recurring fee`, or `One-time & Recurring fee`. |


### Host URLs

Host URLs appear for POS devices in the Unity Portal. Confirm with PXP which host URL fields apply to Oracle Simphony SPI deployments.

| Name | Description |
|  --- | --- |
| Instore notification URL | The URL that PXP sends device logs to. |
| Store & forward URL | The URL that PXP sends transactions to for processing, if store and forward is enabled. |
| Transaction URL | The URL that PXP sends transactions to. |
| Reporting URL | The URL that PXP sends reports to. |
| Status Packet URL | The URL that PXP sends status updates to. |


### Logging settings

| Name | Description |
|  --- | --- |
| Verbose logging | Whether verbose logging is enabled for this device. |
| Maximum log size (MB) | The maximum size that a log can reach, in megabytes. Once this size is reached, the old log will be discarded and a new log will be created. |
| Log file clean up days | The number of days after which PXP will delete the log data. |
| Device log level | The device log level. This can be one of:`None`: no information is logged.`Information`: all activity is logged.`Exception`: only errors or exceptions that caused issues with a transaction are logged.`Health`  |


## Feature settings

### General

| Name | Description | Default value  |
|  --- | --- | --- |
| Return status packets | Receive status updates about the customer's payment journey. |  |
| Language selection  | Allow customers to choose a display language for the device. |  |
| Gratuity | Allow customers to add a gratuity on the terminal. For Oracle Simphony, tip amounts are typically selected in Simphony and passed in the SPI message. Confirm with PXP whether device-based gratuity should also be enabled for your deployment. [Learn more](/guides/point-of-sale/pos-plus/oracle/gratuity-and-service-charges). |  |
| Service charge | Enable service charges on the terminal. For Oracle Simphony, mandatory service charges are typically passed from Simphony in the SPI message. [Learn more](/guides/point-of-sale/pos-plus/oracle/gratuity-and-service-charges). |  |
| P2PE | Enable point-to-point encryption. |  |
| Accessibility mode | Enable accessibility mode. |  |
| Currency | The default currency. Must match the currency used in Simphony. | `GBP` |
| On-device limit | The on-device limit. | `100.00` |
| Contactless limit | The contactless payment limit. | `50.00` |
| Floor limit | The floor limit. | `0.00` |
| CVM limit | The CVM limit. | `50.00` |
| Refund limit | The refund limit. For Oracle Simphony, refunds are initiated from Simphony. See [Pay at Counter](/guides/point-of-sale/pos-plus/oracle/pay-at-counter#refund) or [Pay at Table](/guides/point-of-sale/pos-plus/oracle/pay-at-table#refund). |  |


### Receipt settings

| Name | Description | Default value  |
|  --- | --- | --- |
| Print Merchant Receipt | Print a merchant receipt, in addition to the customer receipt. |  |
| Certification Mode | Provides additional EMV details when running a certification on behalf of an acquirer. **This should not be enabled when live.** |  |


### DCC settings

Enable DCC when routed through AIB or Elavon. See [Dynamic currency conversion](/guides/point-of-sale/pos-plus/dcc).

| Name | Description | Default value  |
|  --- | --- | --- |
| Enabled | Enable Dynamic Currency Conversion for this device. When enabled, eligible transactions automatically present currency choice options to international customers. |  |
| DCC on Pre-auths | Allow DCC to be offered on estimated authorisations. Oracle Simphony SPI supports Purchase, Refund, and Void only. Confirm with PXP whether this setting applies to your deployment. |  |
| DCC on Capture | Allow DCC to be offered on captures. Oracle Simphony SPI supports Purchase, Refund, and Void only. Confirm with PXP whether this setting applies to your deployment. |  |


### Terminal capabilities

| Name | Description | Default value  |
|  --- | --- | --- |
| Keyed | Allow card payments where card details are manually keyed in. |  |
| MOTO | Allow Mail Order/Telephone Order payments. |  |
| Swiped | Accept card payments with swipe (magnetic strip). |  |
| Contact Chip (ICC) | Accept card payments with chip. |  |
| On-Line PIN | Accept card payments with online Personal Identification Number (PIN). |  |
| Plaintext PIN (Offline) | Accept card payments with a plaintext offline Personal Identification Number (PIN). |  |
| Paper Signature | Accept card payments with signature. |  |
| Offline PIN (Encrypted) | Accept card payments with an encrypted offline Personal Identification Number (PIN). |  |
| No CVM Required | Accept card payments without requiring any card verification. |  |
| Static Data Authentication (SDA) | Enable Static Data Authentication (SDA). This is a basic security mechanism used in EMV chip cards where the card contains a digital signature created by the issuing bank that remains constant (static) for the life of the card. |  |
| Dynamic Data Authentication (DDA) | Enable Dynamic Data Authentication (DDA). This is a security mechanism used in EMV chip card transactions where the payment terminal verifies the authenticity of the card by performing a real-time cryptographic challenge-response authentication. During this process, the chip card generates a unique digital signature using its private key for each transaction, and the terminal validates this signature using the card's public key certificate. This makes it extremely difficult for fraudsters to clone or counterfeit cards, since each transaction requires a new and unique cryptographic proof of authenticity. |  |
| Card Capture Capability | Enables you to physically retain (capture) a customer's card. For example, if you suspect fraudulent activities. |  |
| Combined DDA/AC Generation (CDA) | Enable combined Dynamic Data Authentication (DDA) and Application Cryptogram (AC) generation. DDA verifies the authenticity of the chip card by validating its digital signature, while AC generation creates a unique cryptogram for each transaction to ensure its security and prevent replay attacks. This combined process enhances transaction security by verifying both the card's legitimacy and the transaction's integrity in one step. |  |


## Store and Forward settings

Store and Forward settings appear for POS devices in the Unity Portal. Confirm with PXP whether Store and Forward applies to your Oracle Simphony SPI deployment.

| Name | Description | Default value  |
|  --- | --- | --- |
| Store and Forward | Enable Store and Forward for this device. |  |
| Transaction amount threshold | The threshold amount up to which to store a transaction for offline processing. Transactions with an amount above this threshold won't be stored. | `0` |
| Days Until Ftp Upload | The number of days after which PXP will upload a file to FTP. | `7` |
| Throttling limit | The maximum number of transaction we can send in one go. | `0` |
| Process interval(s) | The interval between processes, in seconds. | `0` |


## Updating settings

1. In the Unity Portal, go to **Merchant setup > Sites** and open the **POS service**.
2. Select the device and change settings under **General settings** or **Feature settings**.
3. Click **Save** to confirm. The device picks up changes on its next connection.


After changing values that Simphony depends on (e.g., the POS ID), update Simphony EMC to match. The POS ID itself can't be renamed once created.