Development
End User Account Registration
We have made changes to the end user registration process. This is for end users that are creating an account to log in rather than completing a ‘guest’ registration.
New registration process is as follows;
End user accesses invite link
Email is entered (Email will auto populate from invite)
Access code is sent to email address and entered
End user creates a password
End user selects Authentication method (Authenticator App or SMS)
End user either receives SMS access code – or enters verification code from auth app
Authentication methods
Authenticator App – The user can download / use an authenticator app – scan the QR code and enter the authentication code provided to them in their app.
Each time they log in they will need to enter their email , password and then a code from their authenticator app.
SMS – The user will be sent an access code to the mobile number associated to their profile.
Each time they log in they will need to enter their email, Password and then a code sent via SMS
Existing account registration users
For any existing account registration users that have already created a login – upon their next log in, these users will be prompted to create a password and to then select an authentication method as above.
We have also implemented changes so that all of these users can recover their log in details where required.
Open Banking
Six month history of financial data
We have made changes so that the six months of history shows data for the six months prior to the user authorising the open banking check rather than at the point of viewing the data.
Bugs
Decimals added to number fields
We have resolved an issue where when a user entered a decimal place into a number field the cursor jumped to the start of the input.
API client users not specifying a DOB when running Adress & Mortality check
Where no date of birth is specified within an API request to run an address & mortality check, we were previously defaulting this to 01/01/0001 which was causing a mismatch on the check results. We have now changed this so that no DOB is used within the check and the results reflect this correctly.
Form items displaying in incorrect order
We have resolved an issue where form items were presenting to the end user in a different ordered to that configured in the form.
Sanctions & PEPS Data
We have increased the size of fields within the database to accommodate larger items of data returned to us from our data provider. This is to rectify errors that some end users were facing when completing processes.
Visibility of data
We have improved the visibility of the data when a client is viewing completed forms within a process.
‘Continue on Desktop’ issue
We have rectified an issue where users switch methods of completion between desktop and mobile. Previously the user was not able to continue on desktop successfully.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article