Sending a verification code to a User Login in Q2 Console User Management
About CSR-initiated verification of an end user
Call Center Initiated End User Verification is a CSR-initiated action in Q2 Console User Management that sends the end user (for example, a customer of the FI) a verification code to their existing digital banking SMS or Email Secure Access Code contact target(s). FIs can use this feature to help determine whether an individual caller over the phone is legitimately the end user they say they are.
Required entitlements
To send a verification code to an end user, you'll need specific rights (permissions) assigned to you in Q2 Console Administration. CSR rights are configured on the Administration > CSR Roles page in Q2 Console.
For information on the required entitlements, see the "User Management" section of the Rights for CSR roles in Q2 Console.
Sending a verification code to an end user
To send a verification code:
- Go to the User Login level of a profile in Q2 Console User Management.
- Select Send verification code.
- Select a delivery target, then select Send verification code to send the code to the end user.
Note: At this time, only SMS text and Email targets are supported for verification code delivery.
- The end user then provides the verification code they received from the designated delivery target. Compare the end user's verification code to the one displayed on the verification code modal window to verify the end user's identity.
- Based on the end user's response, Verify, Reject, or Resend the verification code.
Your selection is logged and can be reviewed in the Verification Codes (Code) section of the Login profile.
Tip: If a verification code is rejected, Q2 recommends that FIs use the CSR Notes feature for record-keeping in accordance with their security protocols. CSR notes can be viewed in both Q2 Console User Management and Q2 Co-Pilot. Q2 recommends FIs maintain their own internal policies and processes regarding rejected verification codes and associated risk policies.