feat: Show page to link existing account when attempting to pay

[MrMuzyk]

Explanation of Change

• Updated routing in order to show page to link existing bank account in RHP without redirecting user to workflows
• Show page to link existing bank account when user tries to pay expense on workspace that doesnt have connected bank account but has existing accounts that could be connected

Fixed Issues

$ #65912

PROPOSAL:

Tests

Same as QA steps

• Verify that no errors appear in the JS console

Offline tests

QA Steps

Scenario A:

Precondition:

• User has a workspace connected to business bank account.

1. Create brand new workspace that has the uses the same currency as business bank account connected to different workspace on this account
2. Create an expense for new workspace
3. Try to pay for this expense by clicking on Pay -> Pay with business account
4. Page showing already existing linked accounts should be displayed

Scenario B:

Precondition:

• User has a workspace connected to business bank account.
• User has added a personal bank account.

1. Create a new USD workspace.
2. Go to workspace chat.
3. Create an expense in workspace chat.
4. Click Submit and Approve.
5. Click Pay button.
6. Click Pay with business account.
7. Personal bank account should not appear in the list.

Scenario C:

1. Sign in to ND with a new account, validate the account
2. Create a workspace
3. Submit an expense in the workspace chat and approve it
4. Click the "Pay" button, then "Mark as paid"
5. Expense gets marked as paid correctly

Scenario D:

Precondition:

• User has a workspace connected to business bank account.

1. Create a new USD workspace.
2. Go to workspace chat.
3. Create an expense in workspace chat.
4. Click Submit and Approve.
5. Click Pay button.
6. Click Pay with business account.
7. → Existing connected bank account list opens.
8. Close the RHP.
9. Go to Reports > Expenses.
10. Click Pay button.
11. Click Pay with business account.
12. Page showing already existing linked accounts should be displayed

Scenario E:

1. Create a worskspace
2. Go to the workspace > Workflows > Add bank account
3. Complete the flow adding a Wells Fargo bank account
4. Go to Workspaces. Create a new workspace with USD currency (same currency as the first workspace)
5. Go to the new workspace chat > Create a manual expense > Submit > Approve > Pay > Pay with business bank account
6. The bank account added in the first workspace should be displayed as an option to connect existing bank account

Scenario F:

1. Create a new workspace on an account with an existing bank account.
2. Submit an expense and try to pay it.
3. Begin adding a new bank account.
4. Back out of the flow before completing.
5. Go to workflows page, notice you see partially setup account linked to the workspace (this is correct)
6. Go back to report, notice you don't see split pay button (this is correct).
7. Tap pay.
8. Tap pay with business account.
9. You should be prompted to continue with partially setup account, because it's linked to the workspace at this point.

Scenario G:

1. Login to an account with a partially setup bank account.
2. Create a new workspace.
3. Submit an expense and try to pay it.
4. Select the partially setup account on the connect existing account modal.
5. We link the partially setup account to the workspace, allowing user to continue setting up the account there. User should remain on the same view though because it is possible to continue setting the account up from the report view.

Scenario H:

Precondition: User has no connected or partially connected GBP accounts

1. Create a GBP workspace.
2. Submit a report on it.
3. Try to pay the report and select business account.
4. RHP opens and user is asked to connect bank account

Scenario I:

1. Sign into a new account.
2. Create a workspace and add a business bank account.
3. Delete the workspace.
4. Create a new workspace.
5. Submit a report and approve it.
6. Pay the report and select the bank account.
7. Verify you now see the split pay button with the bank account listed in the main portion of the button.
8. Go to Workflows and disconnect the bank account.
9. Go back to the report.
10. You should no longer see the split pay button or the bank account listed in the pay button because it was removed.

Scenario J:

Precondition:
User A's default currency is USD.
User B has at least one workspace.
User B doesn't have a bank account

1. [User A] Submit an expense in USD to User B.
2. [User B] Go to Reports > Expenses.
3. [User B] Click Pay button.
4. [User B] click on "Pay with workspace"
5. The user is able to procced with paying with workspace by adding a bank account

• 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.native.mp4

Android: mWeb Chrome

android.web.mp4

iOS: Native

ios.native.mp4

iOS: mWeb Safari

ios.web.mp4

MacOS: Chrome / Safari

web.mp4

MacOS: Desktop

desktop.mp4

[melvin-bot]

@dominictb 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]

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/SCREENS.ts	100.00% <ø> (ø)
src/libs/API/types.ts	100.00% <ø> (ø)
...gation/linkingConfig/RELATIONS/WORKSPACE_TO_RHP.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts	75.00% <ø> (ø)
src/libs/actions/Report.ts	55.38% <ø> (ø)
src/libs/actions/Search.ts	20.49% <100.00%> (ø)
...ges/ReimbursementAccount/USD/BankInfo/BankInfo.tsx	0.00% <ø> (ø)
.../pages/workspace/WorkspaceOverviewCurrencyPage.tsx	0.00% <ø> (ø)
...pages/workspace/WorkspaceResetBankAccountModal.tsx	0.00% <ø> (ø)
src/ROUTES.ts	12.60% <0.00%> (+0.10%)	⬆️
... and 16 more
... and 8 files with indirect coverage changes

[github-actions]

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

[joekaufmanexpensify]

@MrMuzyk I retested #77630 and the issue is fixed on the reports page. Paying the IOU there works as expected. However, we are incorrectly not showing the option to pay the IOU from the workspace chat or inside the report.

Adhoc

Production

[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, Desktop, and Web. Happy testing! 🧪🧪
Built from App PR #77751.

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

Desktop 💻	Web 🕸️
⏩ SKIPPED ⏩	https://77751.pr-testing.expensify.com
The build for Desktop was skipped

---

👀 View the workflow run that generated this build 👀

[joekaufmanexpensify]

Retested and the fix for #77630 works well

[joekaufmanexpensify]

@dominictb could you review?

[dominictb]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I verified proper code patterns were followed (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
  • 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 verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• 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
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• 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 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.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2025-12-18.at.23.40.40-compressed.mov

Checklist with full recordings from previous PR: #71659 (comment)

[dominictb]

BUG: Pay with workspace on an IOU does not open connect existing BBA page:

Screen.Recording.2025-12-19.at.00.18.24.mov

[joekaufmanexpensify]

I agree we should ideally do that, but I think it can be out of scope here and done as a follow up. I would put that in the new feature bucket, rather than really being a bug.

[dominictb]

🎀

[srikarparsi]

Looks good to me but there are conflicts that look like they need to be resolved

[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.2.97-0 🚀

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

[OSBotify]

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

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

[srikarparsi]

Discussing deploy blockers for this PR here

[OSBotify]

🚀 Deployed to production by https://github.com/francoisl in version: 9.2.99-8 🚀

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