Please enable JavaScript.

Coggle requires JavaScript to display documents.

KYC Risk Areas (Data correctness and corruption (The response has mixed…

- - - - Check with a query in the DB if the users' data is right (the exact time the check is triggered, their KYC status at the moment, etc.)
      - Check in the request if the data is sent correctly to the provider
  - - - Write a query in the db to check past cases and compare the users' data to the one provided in CMS and Capita's platform
  - - - The user should get an error in this case, before sending the document
      - If the user doesn't get an error and gets verified afterwards it's an Onfido bug
  - - - query to see if the db is updated and if the send data is valid
      - check in CMS whether the age and address are approved
  - - - Check the users that were going through the verification and their data at the time of the crash with a query in the DB.
      - Check in the Onfido platform the number of checks sent
  - - - Check in logz.io if there's a reason for the lack of response
      - Check in the user's profile if his verification status has been correctly updated
      - Check if the user's information is being updated in CMS and the DB
  - - - Check in the DB if there were a lot of affected users
      - Check if the loss data is able to be restored (if the users can sent their information again)
  - - - Check with a query in the DB if there are users which have missing data
      - Check if the checks are received by Onfido
  - - - Check if correct data is recorded in the DB
      - If the user gets verified but the data which the user sent is wrong, it's an Onfido bug
      - Check in the Onfido platform the address which was sent
  - - - Find the request and response in logz.io
      - try entering invalid postcode a few different ways (with spaces, more characters, etc)
      - Check if the problems comes from a specific device/browser
  - - - Create a few accounts and check the data in cms and the database
      - query in the db
  - - - Check in the DB the users' data
      - Try checking a few times by going through the same flow on different devices and browsers
      - Check the request and response at the moment of entering and sending the DOB
  - - - Check Onfido response
      - check for a crash of onfido
      - check db status
  - - - Check the connection at the time
      - Check via CMS and mix panel if the information about the user is generated
      - Check in logz.io if the response and request are correct
  - - - Check if the db is updated
      - Check what happens if the internet connection is lost
      - Check if there's an onfido crash
  - - - Create a few accounts and compare the verifications statuses in the db and the website
      - Check if the correct request is sent to the kyc provider
  - - - Check if the db is updated
      - Check if the status in Onfido is updated
  - - - Check if the internet connection was lost
      - to be tested if the old data can be updated with invalid one
      - query to check if the user's data is updated
      - to be tested on a couple of users if the old data is updated
      - CMS, Onfido and DB check
- - - - query to see if the new user is updated in the db
  - - - Check CMS, Onfido platform and DB if the verification status is updated
  - - - Check if the request, which was sent to Onfido was correct and if an error appeared at the time.
      - Check if the response Onfido sent was correct.
  - - - Check if the user can proceed with the verification after the response fails and if that's possible, check if the user's kyc status is updated in the db
      - Check if the problem was related to a specific device and browser
  - - - Check if there is an update in the the DB for the KYC status and it is correct
      - Check if only one check is recorded in the Onfido platform after trying to send a request again)
      - Check if the request is sent again, the correct response comes from Onfido.
  - - - Check if there are any such cases with a query in the DB
      - Check in the DB, CMS and the Onfido platform when the user sent his documents.
  - - - Query to check if the address is verified and when it was verified
      - CMS check if the address is verified
      - DB query to check if the user's address is presented in the database
  - - - Automation process to check a number of users are being watchlist check
      - Functional spot check testing to validate via the DB query for users who had Identity checks but don't have watchlist checks
    - - select id, verifiedKycAge,verifiedKycAddress,verifiedKycAgeTime,verifiedKycWatchlist,verifiedKycWatchlistTime from users where verifiedKycWatchlist = 0 and verifiedKycWatchlistTime is null and verifiedKycAge = 1 and verifiedKycAddress = 1 order by verifiedKycAgeTime desc
  - - - uery to see if the user's profile is updated in the db
      - Check if there was loss of internet connection
      - Check if onfido is updated
- - - - Check if the provider sends an adequate response
      - Check if the request is sent to the provider
      - Check if the user gets an error and if the request should be send again
  - - - Go through the KYC flow a few times. Go to Onfido/Capita platform to check if the check is triggered.
      - Check in http://logz.io/the network tab in Chrome if the providers send the correct response.
      - Check with a query in the DB if the check is recorded and the user's data updated
  - - - Enter invalid First Name/Last Name/Address/DOB which makes the user under 18 and check if the BE returns a correct response
      - Check in CMS, DB and the provider's platform if the user gets verified with the entered incorrect data
  - - - Testing activities
        
        Does onfido alarms the lack of documentation and does it stops the process and makes the users's verification pending or impossible to continue
        
        Test via http://logz.io and the dev tools whether the error is handled
        
        Check whether the db continues work properly
        
        Test if a couple of users with unreadable documentation block the registration flow of the whole app/website
    - - Testing Activities
        
        Check wheter the rest of the information is updated in the db
  - - - check whether the access is restricted
      - check if an error is send in logz.io
      - does onfido detect the data is different. Check whether onfido, db or via web tools an error is send
  - - - db and onfido check if the error is detected
      - dev tools to check the response when the document is sent
- - - - Check if the user's data is updated in the DB using query
      - Check on different environments, browsers and devices
      - Check if the documents are sent to Onfido in the Onfido platform
  - - - Check in Heroku if the provider is changed in the correct environment
      - Try changing the provider in Heroku again and check if the behaviour is correct.
      - Check the provider to which the request for the express check was sent to.
  - - - Query to see the time of age verification
      - CMS age status check
      - Query to see the status of the age verification in the db
  - - - Check if a problem with the verification status or the user's data occurs from this kind of behaviour.
      - Check the checks sent to the Onfido platform
  - - - query to see if the data for the new user updates the db
      - Check on different browsers
  - - - Try entering Invalid postcode
      - Try entering DoB which makes the user underage
      - Try entering Names with invalid characters
- - - - Try uploading from different browsers (Safari, Chrome, Firefox)
      - Check uploading from different devices(Android, iOS, macOS, Linux, Windows)
      - Check the devices and browsers the users are using in Mixpanel
  - - - Test on different devices to check of the problem comes from the specific device
      - Look up in Mixpanel/Firebase/DB what devices and browsers are the users using, and what is their devices' os.
  - - - Check in this case if a correct error appears to the user
      - Check the behaviour on different browsers and devices
  - - - Test on different browsers
      - Look up in Mixpanel/Firebase/DB what devices and browsers are the users using, and what is their devices' os.
      - Test on different devices to check of the problem comes from the specific device
      - May be a memory issue on the older devices especially
  - - - Check the different browsers and devices used in Mixpanel
- - - - Check the response from Onfido when the request is sent.
      - Check in the Onfido platform if the check was sent
      - Check if there's a way to alert the user when he'll be able to upload his documents
      - Check in the Onfido platform if there's a maintenance scheduled
      - Check if the user's data is updated in the DB and CMS
  - - - Check if the user is able to send a request again
      - Change the provider to Onfido while capita is fixed and see if the user has another chance at submitting his data
  - - - Check in this case if the user gets a second chance to upload his documents. Is the data recorded twice in the DB and in the provider's platform?
      - Check in the DB if the user's data is updated
      - Check the browser the user was using
      - Check the response which was returned at the time
      - Check the device the user was using
      - Check if the problem comes from a specific action by going through the same flow a few times
      - Check if the problem comes from a specific device or browser
  - - - Automated check for users without pictures but passed the upload documents process.
      - Check in Onfido platform for users, who passed the process of submitting documents, but there are no documents
  - - - Check the response from Onfido
      - check if the provider is onfido, not capita (query to check the users's provder)
      - Check the selected provider in Heroku
- - - - Check if Onfido is updated
      - Check in the db with a query for the user's status and then check his account in the website
- - - - Check in Mixpanel Live View if the events are recorded in the corresponding environment