In this section, we showcase visuals and the primary user interactions with the Add funding Element. See [Add funding: Implementation](doc:add-funding-element-implementation) for implementation details, including pre-conditions, custom events, and error handling. ## Core behavior and requirements With the Add funding Element, BILL has a set of requirements for the expected behavior.

Behavior & requirements	Description
User role	The organization user must have the `ADMINISTRATOR` user role to manage all the bank accounts in the organization. A card account is available only to the user that added the card account.
Add a bank account with Plaid	The user adds a bank account instantly with Plaid. The account is automatically verified and is ready for use.
Add a bank account with manual setup	When the user adds a bank account with manual setup, BILL sends a test payment to the added account. The user must verify the added bank account by entering the test payment amount. If the test payment verification fails, the account is archived and removed from the list of funding payment methods for the user.
Add a card account	The user adds a card account by manually entering the card details.
User verification	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 `NOMINATED`on their bank account status to complete user verification. If user verification is required, the user is prompted to complete the verification process in the Add funding Element. User verification is also available with the User verification Element, Manage funding Element, Schedule payment Element, and Onboarding Element. Without verification, the user cannot use a funding payment method for payments.

## Plan your user experience In this section, we outline key considerations for planning a seamless user experience when integrating with the Add funding Element into your application. Ensure that you address each point thoughtfully to realize the full value of the Element capabilities in your existing experience. Add funding Element overview

### Assumptions When the user is using the Add funding Element, BILL assumes that the organization onboarding is complete with the Onboarding Element. ### Entry points There are a set of workflows where the Add funding Element can be integrated. * When the user is attempting to pay a bill * When the list of funding payment methods is empty * In your application's settings page or payment management section ### Map the user flow Map the complete user flow from identifying the need to add a funding payment method to successfully completing the process of making a payment. Add a payment method flow

### Maintain context Ensure that your users understand that they are adding a funding payment method for their BILL organization account. In addition, your users must understand how this relates to their ability to pay bills with your integrated experience. ### Bank account with manual setup experience When the user adds a bank account with manual setup, they enter their account number and routing number with the Element. BILL sends a test payment to the account to confirm whether the account details are accurate. BILL takes up to 2 business days to send the test payment. The user must verify the added bank account by entering the test payment amount. **NOTE:** _In the Stage environment, the test deposit amount is always $0.50._ Consider how you can make it easy for the user to enter the test payment amount with CTAs that direct the user to the Manage funding Element. * 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 ### User verification 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 `NOMINATED`on their bank account status to complete user verification. If user verification is required, the user is prompted to complete the verification process in the Add funding Element. User verification is also available with the User verification Element, Manage funding Element, Schedule payment Element, and Onboarding Element. Without verification, the user cannot use a funding payment method for payments. Consider how you can make it easy for the user to complete the verification flow with CTAs that direct the user to the Manage funding Element. * 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. ## Related Elements BILL Elements are connected and understanding this connection and hierarchy enables you to understand the user experience better.

Connection	Description
Child	[MFA Element](doc:mfa-element): MFA is required for the user to add a funding payment method. When the signed-in user session is not MFA-trusted, the user is required to complete the MFA setup. [User verification Element](doc:user-verification-element): The user may be required to complete one-time BILL risk verification before the user can use a funding payment method for payments.