



Where we were thrown off is when it threw the OTP error but there were no resources indicating how to deal with the issue. Hi we wouldn't want to be entering in a 2FA code every time anyways. That's why all registrar modules just provide input fields for credentials or alternatively an API token. it would require to always prompt for an OTP code whenever whmcs uses a registrar module to interact to the appropriate API/backend system behind. This isn't something that can be changed on our side or even in whmcs itself. That was one main issue you were reporting. In addition: WHMCS itself only provides the possibility to deal with a user or role user with deactivated 2FA in the registrar modules.
