Netverify Mobile Flow
1. From wework app, user inputs in hotstamp. VerificationService#start_verification is hit and a verification attempt is created and set to PENDING. The hostamp is saved.
2. Member goes through Netverify flow.
3. Netverify hits VerificationService#complete_verification once complete and saves response into response field.
  - if the Netverify repsonse is success
    - if not Face Match
      - VerificationService will try to see if the face match is over 70%. if not, VerificationService will fail the attempt with reason "FACE_MATCH_FAILED" and the user, and a faiure mailer will be sent.
    - if not keycard sync (keycard sync will have to generate access levels for the member)
      - VerificationServiceVerificationService will try to sync the keycard over the s2. if not, VerificationService will NOT fail the attempt, but a "keycard failed to sync" mailer will be sent
    - Success mailer is sent to user
  - if the Netverify response is failure
    - if the status is "NO_ID_UPLOADED"
      - this means effectively something went wrong with the id uploading process, not a true verification failure. We do not send a failure mailer but the verification attempt is marked as failed. The user is not marked as failed and their verification status is untouched.
    - if last successful attempt was under an hour ago
      - We don't mark the user as verified failed, but still record the failed verification attempt.
    - Failure mailer is sent to user


Netverify Web Flow
1. From Spacestation, CM inputs in keycard info and hits submit. VerificationService#start_verification is hit and a verification attempt is created and set to PENDING. The keycard info is saved but not activated.
2. CM goes through Netverify flow with member.
3. Netverify hits VerificationService#complete_verification once complete and saves response into response field.
  - if the Netverify repsonse is success
    - if not Face Match
      - VerificationService will try to see if the face match is over 70%. if not, VerificationService will fail the attempt and the user, and a faiure mailer will be sent.
    - if not keycard sync
      - VerificationServiceVerificationService will try to sync the keycard over the s2. if not, VerificationService will NOT fail the attempt, but a "keycard failed to sync" mailer will be sent
    - Success mailer is sent to user
  - if the Netverify response is failure
    - if the status is "NO_ID_UPLOADED"
      - this means effectively something went wrong with the id uploading process, not a true verification failure. We do not send a failure mailer but the verification attempt is marked as failed. The user is not marked as failed and their verification status is untouched.
    - if last successful attempt was under an hour ago
      - We don't mark the user as verified failed, but still record the failed verification attempt.
    - Failure mailer is sent to user