User verification: User experience
In this section, we showcase visuals and the primary user interactions with the User verification Element.
See User verification: Implementation for implementation details, including pre-conditions, custom events, and error handling.
Core behavior and requirements
With the User verification Element, BILL has a set of requirements for the expected behavior.
Behavior & requirements | Description |
|---|---|
Without user verification, the user may not have access to features | Before the user can use a funding payment method, the user may be required to undergo BILL risk verification. Users that are flagged by the BILL risk model are set as If user verification is required, the user is prompted to complete the verification process in the User verification Element. User verification is also available with the Add funding Element, Manage funding Element, Schedule payment Element, and Onboarding Element. Without verification, the user cannot use a funding payment method for payments. |
Funding payment method user status values |
User verification is available with the Onboarding, Add funding, Manage funding, Schedule payment, and User verification Elements. |
Plan your user experience
In this section, we outline key considerations for planning a seamless user experience when integrating with the User verification Element into your application. Ensure that you address each point thoughtfully to realize the full value of the Element capabilities in your existing experience.
Element overview
Assumptions
When the user is using the User verification Element, BILL makes a set of assumptions.
Assumptions |
|---|
The user has added at least one verified funding payment method. OR The user has been given permission to use at least one funding payment method by another user. |
BILL has assigned the NOMINATED funding payment method user status. |
The user has not completed user verification earlier for using or managing the funding payment method. |
Entry points
There are a set of workflows where the User verification Element can be integrated.
- In your application's notification center
- When user sign-in is complete
- When the user is attempting to pay a bill and no verified funding payment method is available
- In your application's settings page or payment management section. BILL prompts the user to complete verification in the Manage funding Element.
Element entry points
Map the user flow
Map the complete user flow from identifying the need to add a funding payment method (or being given permission to use at least one funding payment method) to successfully completing BILL risk verification to successfully completing the process of making a payment.
User verification flow
Maintain context
Ensure that your users understand that they must successfully complete BILL risk verification and must be verified before they can use the nominated funding payment methods in their BILL organization account. In addition, your users must understand how this relates to their ability to pay bills with your integrated experience.
Related Elements
BILL Elements are connected and understanding this connection and hierarchy enables you to understand the user experience better.
Connection | Description |
|---|---|
Parent | Onboarding Element: The user can complete BILL KYC/KYB checks for the organization, set up MFA, add funding payment methods for paying vendors and bills, and complete user verification (if required). Add funding Element: The user can add funding payment methods in the organization. Manage funding Element: The user can add additional funding payment methods and manage existing funding method details in the organization. |
Updated 1 day ago
Now that you understand the user experience, the next step is to integrate the User verification element. Continue to the Implementation section to learn about pre-conditions, custom events, and error handling.