Password encryption is ignored with this site

For some reason, password encryption doesn’t work with this site:

https://www.rentpayment.com/pay/login.html

The password is recorded in plain text. However, if I record a macro with other sites that I have successfully recorded previously the pw is encrypted as expected so I know the extension is working properly.
Is this a bug or are there some sites or scenarios where the encryption doesn’t work?

This website does not use a regular password input text field (<input type="password" ...>), but instead used a standard text field plus some custom CSS:

<input type=‘text’ id=‘password’ name=‘password’ autocomplete=‘off’ class='conceal

Thus UI Vision can not detect that this is a password field and encrypt the recorded (password) string.

Workaround: Record a password input on any other website that has a normal password field, and then copy and paste the password string into this macro. Whenever UI Vision sees a __KANTU_ENCRYPTED__.... string, it knows it has to decrypt it.

Example: - my masterpassword is “123456”.

{
  "Name": "pwd",
  "CreationDate": "2019-11-4",
  "Commands": [
    {
      "Command": "open",
      "Target": "https://www.rentpayment.com/pay/login.html",
      "Value": ""
    },
    {
      "Command": "type",
      "Target": "id=username",
      "Value": "uuuu"
    },
    {
      "Command": "type",
      "Target": "id=password",
      "Value": "__KANTU_ENCRYPTED__f8b53105ebb186d56f90f8545f8d9f1c4677"
    },
    {
      "Command": "type",
      "Target": "name=pu",
      "Value": "on"
    }
  ]
}

After trying the workaround on that site the pw box multiplies the password character length by about 10. UI.Vision recorded the pw correctly using an alternate site. I know XType gets around those wierd input boxes so I switched to XType with the encrypted pw and it failed. Can XType not be used with encrypted pw’s?

We have never tested it with XType, so it could very well be that it does not work with it yet. I moved your post into the “feature suggestion” sub forum, so that we can take care of this with future updates.