PGC PAX v2.15.11

There is a possibility that this build will assign a new UUID (Terminal ID) to your device. If this happens the POS system or originating software will need to be updated with the devices new UUID 9Terminal ID). Instructions to find the UUID (Terminal ID) in the applications are available on the Developer Center here: (Step 21) PAX A-Series Deployment Instructions

Resolved an issue where sending a different Merchant Account Code in the PayGuadrian Cloud API payload than what was programmed in BroadPOS BridgePay would change the BroadPOS BridgePay programming to the different Merchant Account Code in error.
Resolved an issue where "Pairing Successful" would display when an invalid pairing code was entered during device pairing.
Enhanced the auto-start prompts when initially loading the PayGuardian application on a device running Android 10 or above. Users are now taken to an option to enable the app over other apps. Simply toggle this on and hit the back button. Users are taken to the PayGuardian home screen and are ready to process. The new steps can be found here: Downloading the Terminal - Step #16 K-L PAX A-Series Deployment Instructions
Resolved an issue were pairing would succeed but the device would not connect to the cloud service.