Change for personal bank account setup

[narefyev91]

Explanation of Change

Coming from here, we need to add support for manual US personal bank accounts in NewDot. We support both Plaid and manual US personal bank accounts in OldDot. We support Plaid and manual for US business bank accounts in NewDot, but only Plaid for US personal bank accounts in NewDot now. We also need to begin collecting name, address, and phone number associated with the bank account in situations where it's not already on file

Fixed Issues

$ #73693
PROPOSAL:

Tests

• Plaid flow

1. Go to wallet page
2. Click on Add new bank account
3. Pick US country
4. Verify that user sees 2 options to Connect with bank and connect manually
5. Start connect with bank flow - connect bank with plaid
6. Finish plaid flow and pick plaid bank account
7. There 3 additional steps - Legal Name, address and phone - user should not see any of these steps if they already has this information in their account.
8. On the last step - screen to verify changes - each menu item should lead to correct flow and allow to change information
9. When bank is connected - success screen should be shown

• Manual flow

1. Go to wallet page
2. Click on Add new bank account
3. Pick US country
4. Verify that user sees 2 options to Connect with bank and connect manually
5. Start connect with bank flow - connect manually
6. Verify that user sees account number and routing number inputs - fill them and proceed
7. There 3 additional steps - Legal Name, address and phone - user should not see any of these steps if they already has this information in their account.
8. On the last step - screen to verify changes - each menu item should lead to correct flow and allow to change information
9. When bank is connected - success screen should be shown
10. Any changes to user info - should also be updated in user profile

• Verify that no errors appear in the JS console

Offline tests

Bank account is not allowed to be added in offline mode

QA Steps

• Plaid flow

1. Go to wallet page
2. Click on Add new bank account
3. Pick US country
4. Verify that user sees 2 options to Connect with bank and connect manually
5. Start connect with bank flow - connect bank with plaid
6. Finish plaid flow and pick plaid bank account
7. There 3 additional steps - Legal Name, address and phone - user should not see any of these steps if they already has this information in their account.
8. On the last step - screen to verify changes - each menu item should lead to correct flow and allow to change information
9. When bank is connected - success screen should be shown
10. Any changes to user info - should also be updated in user profile

• Manual flow

1. Go to wallet page
2. Click on Add new bank account
3. Pick US country
4. Verify that user sees 2 options to Connect with bank and connect manually
5. Start connect with bank flow - connect manually
6. Verify that user sees account number and routing number inputs - fill them and proceed
7. There 3 additional steps - Legal Name, address and phone - user should not see any of these steps if they already has this information in their account.
8. On the last step - screen to verify changes - each menu item should lead to correct flow and allow to change information
9. When bank is connected - success screen should be shown

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

android-web.mov

iOS: Native

iOS: mWeb Safari

ios-web.mov

MacOS: Chrome / Safari

web.mov

web-manual.mov

MacOS: Desktop

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/ROUTES.ts	12.25% <ø> (ø)
src/SCREENS.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts	75.00% <ø> (ø)
...tionalDepositAccount/substeps/CountrySelection.tsx	0.00% <ø> (ø)
src/types/form/PersonalBankAccountForm.ts	0.00% <ø> (ø)
...c/hooks/usePersonalBankAccountDetailsFormSubmit.ts	0.00% <0.00%> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx	8.28% <0.00%> (-0.02%)	⬇️
src/libs/actions/BankAccounts.ts	2.28% <0.00%> (-0.03%)	⬇️
src/pages/AddPersonalBankAccountPage.tsx	0.00% <0.00%> (ø)
...sitAccount/PersonalInfo/substeps/LegalNameStep.tsx	0.00% <0.00%> (ø)
... and 8 more
... and 10 files with indirect coverage changes

[melvin-bot]

@suneox Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[narefyev91]

I will update videos on monday - just for now only web is added
We still wait some BE changes (like allow to connect bank account manually - not providing bank name and user info should be stored on BE side) - but PR is ready for the first round of reviews from C+

[suneox]

Overall, the change set is consistent with other places, but there is still an issue at the confirmation step: the error message remains stuck at the bottom even after navigating to another step to update the info.

CleanShot.2025-11-26.at.01.01.33.mp4

[github-actions]

🚧 @joekaufmanexpensify has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #75179.

Android 🤖	iOS 🍎
⏩ SKIPPED ⏩	⏩ SKIPPED ⏩
The build for Android was skipped	The build for iOS was skipped

Web 🕸️
https://75179.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[joekaufmanexpensify]

Retested #75179 (comment) and it's fixed now! I no longer see the Update button on the PBA in OldDot after adding it in NewDot, which should mean all the data is stored on the bank account.

[joekaufmanexpensify]

Good from my perspective 👍

[srikarparsi]

Merging without the react compiler check passing because we need to manually use a useMemo because the output of a useMemo is used in a useEffect. Not wrapping address in a useMemo introduces that compile issue.

[melvin-bot]

@srikarparsi looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[srikarparsi]

Note here

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by https://github.com/srikarparsi in version: 9.3.1-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[OSBotify]

🚀 Deployed to production by https://github.com/francoisl in version: 9.3.1-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅