YSoft Payment Machine Troubleshooting

This chapter contains most common problems regarding YSoft Payment Machine.

Could not connect to server

1. Check for correct date on YSoft SafeQ Payment System server and also on YSoft Payment Machine.
   • Network communication is encrypted by SSL with certificate verification. Verification will fail if devices has older date then creation time of certificates. There is possibility to reset system date of YSoft Payment Machine in it's service menu.
2. Allow deprecated TLSv1 in YSoft SafeQ Payment System.
   • YSoft Payment Machine requires TLS 1.0 for the communication to server TCP port 4197 - this protocol is disabled by default since Build 72. There are no plans to implement newer TLS protocol support due to YSoft Payment Machine discontinuation.
   • To allow TLS 1.0 edit <yps>\ps-conf\environment-configuration.properties as follows:
     • create a file backup
     • edit file in Notepad or any other text editor
     • add new line with this text at the end of file: spm.deprecated.protocol.support=true
     • save the fileTo allow TLS 1.0 edit <yps>\ps-conf\environment-configuration.properties as follows:
     • restart YSoftPS service

     • successful change produces the following text in payment-system.log after the service restart:

       TEXT

       2023-06-21 16:31:39.312 [main] WARN  c.y.s.SpmCompatibilityServletContextListener - Enabling TLSv1 for Payment Machine support. 

   • Customers who enable TLS 1.0 are advised to configure YSoft Payment Machine to accept only authentication via PIN or CARD (i.e. disable authentication by a domain username and password).

Access denied

When user is not able to access recharging screen on YSoft Payment Machine due to Access denied error, it can be caused by using currency in YSoft SafeQ Payment System which is not supported by YSoft Payment Machine.