Configure, Run, and Test PayServer

server:
  -
    protocol: P3                    # P3 protocol
    transport: WEBSOCKET            # over WebSocket connection
    port: 8080                      # port number
  -
    protocol: P3                    # P3 protocol
    transport: FRAMED_TCP           # over framed TCP connection
    port: 8081                      # port number

devices:
  # sample configuration for a mock device which can be used for testing
  -
    name: Mock Device               # human readable device name
    identifier: mockDevice          # unique identifier (will be generated randomly if omitted)
    type: MOCK                      # device type
    comlink: MOCK                   # connection type

 
# sample configuration for a Miura reader connected via USB
  -
    name: USB Miura                 # human readable device name
    identifier: usbMiura            # unique identifier (will be generated randomly if omitted)
    type: MIURA                     # device type
    comlink: USB                    # connection type
    port: COM3                      # virtual port name
    keep_alive: true                # the device will be kept connected between transactions (false by default)
    idle_text: ["custom text", "with multiple", "lines", "      centered"]        # custom text that appears when the reader is in idle state

  

information:                        # optional extra information
  location: 3rd Room                # human readable name of the server location

settings:
  locale: en                     # locale to be used independent from the system one
  transactions:
#    enable_signature_actions: true  # specifies if transaction process will send out signature actions

Set the optional
settings.transactions.enable_signature_actions
to true, if you want to capture the shopper's signature digitally and not on the physical receipt. After enabling this option, the signature action messages will be sent out during transaction processing and you need to implement the accompanying signature capture logic in your POS. For more information about signature actions, see P3 Usage and Message Flows and PayClient Integration.
Set the optional
devices[].keep_alive
to true, if you want PayServer to stay connected to that particular device after you execute a transaction on it. This will increase the transaction speed but also prevent the device from entering standby mode. Beware that the device will be connected until you disconnect from PayServer or until you use another device for a transaction.
Set the optional
devices[].idle_text
to any custom idle text that should be shown while the device is in keep-alive state (i.e., no transaction is done, but the connection to the device is kept alive). Provide max 4 lines with 20 characters each and prefix the text with spaces to center it.

Download and run the PayClient Tester App.
Fill in the host. Copy and paste your
merchantIdentifier
and
merchantSecretKey
.
Click the
Connect
and
Start Transaction
buttons. When you start the transaction, the Tester client executes it on the first device from the list of devices. To make sure your device is selected, configure the server for only one device at first.