Learn about the different settings available and their default values.
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.
| Name | Description |
|---|---|
| POS ID | The unique identifier for the point-of-sale device. This is set at device creation and can't be changed later. |
| 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. |
| Communication endpoint | The URL that PXP should communicate with. |
| Device mode | The device mode. This can be Standalone POS, Integrated POS, or Soft POS. |
| 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. |
| 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:
|
| Name | Description | Default value |
|---|---|---|
| Return status packets Coming soon | Return status packets Coming soon | N/A. |
| Language selection Coming soon | Allow customers to choose a display language for the device. | N/A. |
| Gratuity Coming soon | Allow customers to add a gratuity. | N/A. |
| P2PE | Enable point-to-point encryption. | ON |
| Print Merchant Receipt | Print a merchant receipt, in addition to the customer receipt. | ON |
| Certification Mode | Provides additional EMV details when running a certification on behalf of an acquirer. This should not be enabled when live. | OFF |
| Keyed | Allow card payments where card details are manually keyed in. | ON |
| Swiped | Accept card payments with swipe (magnetic strip). | ON |
| Contact Chip (ICC) | Accept card payments with chip. | ON |
| On-Line PIN | Accept card payments with online Personal Identification Number (PIN). | ON |
| Plaintext PIN (Offline) | Accept card payments with a plaintext offline Personal Identification Number (PIN). | ON |
| Paper Signature | Accept card payments with signature. | ON |
| Offline PIN (Encrypted) | Accept card payments with an encrypted offline Personal Identification Number (PIN). | ON |
| No CVM Required | Accept card payments without requiring any card verification. | ON |
| 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. | ON |
| 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. | ON |
| Card Capture Capability | Enables you to physically retain (capture) a customer's card. For example, if you suspect fraudulent activities. | OFF |
| 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. | ON |
| Name | Description |
|---|---|
| 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. |
| Days Until Ftp Upload | The number of days after which PXP will upload a file to FTP. |
| Throttling limit | The maximum number of transaction we can send in one go. |
| Process interval(s) | The interval between processes, in seconds. |