Users have the flexibility to register either as a guest when their identification number is unavailable or as a member when it is known. This flexibility enables them to register and explore the application, along with the benefits they are entitled to guest account registration.
Guest account creation
Users can register by providing their first name, last name, a unique email address, and the Date of Birth (DOB).
Note: During account creation, COPPA restrictions validate user’s age eligibility. This is an application-level configuration. Only users who are 13 years old or above are eligible to register.
An In-line error message will be shown to users who are under 13 years old.
Email address verification: Users should verify their unique email address by entering a code sent to their email before proceeding with the registration step.
Existing account found: If the identification number, name, and date of birth entered by the user match an existing account in our system, the system will initiate a secure verification process.
The system will prompt phone number verification via a “Text Me” or “Call Me” option. For privacy reasons, the associated phone number will not be displayed. Instead, a verification code will be sent to the number linked to the matched account.
Upon successful verification, the system will display a pre-filled sign-in form using the email address associated with the verified account. The user can then proceed to sign in.
To prevent duplicate accounts, users are encouraged to sign in using their existing credentials. If the user believes this is incorrect, they may create a new account with a different email address.
Phone number verification: The user enters their phone number for multi-factor authentication (MFA).
Identification number (Conditional step): Users are prompted to provide an identification number (5-18 characters, using only letters, numbers, hyphens) as part of the registration process.
Handling golden record match failures with guest registration path: If the user is unable to verify their demographic details and identification number with the EIMP system, they will have up to three attempts to correct the information. After each failed attempt, the user may choose to retry or select “Skip for now” to proceed with Guest account (unmatched account) registration.
Note: In hybrid flow, entering an identification number is optional. This differentiates it from the matched flow, where the identification number is mandatory.
Guest accounts can upgrade to Member accounts through a step-up process initiated by the application (where the application collects information to identify the associated Identification number and initiates the step up) or during subsequent logins where user provides an Identification number.
Password creation and confirmation: The user should create and confirm their password.
Identity verification step: While registering a user, there is a possibility of a bad actor registering with someone else’s data to commit fraud, which can compromise the platform’s security. To mitigate this risk, the system will call the Threat Metrix platform (TMX) to validate the user's details. TMX analyzes digital behavior and provides real-time insights to detect and prevent fraud, ensuring a seamless experience for digital users.
Note:
Any issues during account creation will not save user details, and the user will be required to start over.
EIMP sync failure handling in decoupled flow
In the decoupled flow, once an account is successfully created, a synchronization process is initiated with the EIMP system to establish a Golden Record. As part of this process, the UUID (unique identifier) generated for the user is shared with EIMP.
If the synchronization with EIMP fails due to a technical issue, the system creates a matched inactive account. The user is then redirected to a message indicating that sign-in is currently unavailable due to a technical issue, with an option to retry or return later.
The system is configured to automatically retry the sync process up to three times. Each time the user attempts to sign in, a background retry is triggered. If any of these retries succeed, the matched inactive account is updated to a matched active account, allowing the user to proceed normally.
Once the system completes all validations, it successfully creates an account.