Payment

Configuration

• Enable Payment
  If you want to setup a payment cascade, tick this box.
• General Settings
  
• SoftLimit (Bytes) The SoftLimit tells the Accounting Instance when to ask a connected JAP for a signed cost confirmation. Everytime the number of bytes in this field has been transferred between the mix and the JAP, the JAP must send this cost confirmation.
• HardLimit (Bytes) The HardLimit is the number of bytes that may be transmitted without receiving a cost confirmation from the JAP. When the HardLimit is reached, the mix will cut the connection to the JAP. HardLimit should be much greater than SoftLimit. (Typical values are 1500000 for HardLimit and 250000 for SoftLimit.)
• SettleInterval (seconds) The settle interval tells the Accounting Instance how often to contact the Payment Instance to settle cost confirmations. The longer this interval, the less the communication effort and the less the accuracy of the displayed balance in the JAP. (You should set a value between 30 and 120 seconds here.)
• PostgreSQL database for accounting
  For accounting to function properly, your mix will need access to a PostgreSQL database. Enter the correct data for the database here.
• JPI Certificate
  In order to be able to communicate with the Payment Instance, you will have to import its public certificate in this panel. If you do not have the certificate, ask the Payment Instance operator about it.
• JPI (Java Payment Instance)
  Enter the hostname, port and id of the Payment Instance you want to use for settling your cost confirmations.