Fix: Partially set up bank account appears in the payment dropdown button by nyomanjyotisa · Pull Request #80083 · Expensify/App

nyomanjyotisa · 2026-01-21T06:17:08Z

Explanation of Change

Filter out partially set up bank accounts in getPaymentSubItems so they do not appear in the payment dropdown

Fixed Issues

$ #79563
PROPOSAL: #79563 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Precondition:

User A has a USD workspace with Invoices enabled.
User A has sent an invoice in USD to User B.

Perform the steps below as User B:

Create a USD workspace.
Go to workspace settings > Workflows.
Click Add bank account.
Click Connect manually.
Continue until Date of birth step.
Click outside RHP to close it.
Open the invoice report from User A.
Click Pay dropdown button.
Click Pay as a business.
Verify that the partially set up bank account does not appear in the payment dropdown.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android-Native.mp4

Android: mWeb Chrome

Android-mWeb.Chrome.mp4

iOS: Native

iOS-Native.mp4

iOS: mWeb Safari

iOS-mWeb.Safari.mp4

MacOS: Chrome / Safari

MacOS-Chrome.mp4

…tton

codecov · 2026-01-21T06:33:42Z

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/hooks/useBulkPayOptions.ts	`45.83% <0.00%> (-0.98%)`	⬇️
src/components/SettlementButton/index.tsx	`0.00% <0.00%> (ø)`
src/hooks/usePaymentOptions.ts	`0.00% <0.00%> (ø)`
... and 51 files with indirect coverage changes

melvin-bot · 2026-01-21T06:58:26Z

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

trjExpensify

@joekaufmanexpensify is this right to completely filter them out, or should selecting it continue them on in the add bank account flow?

joekaufmanexpensify · 2026-01-21T22:47:50Z

It would be ideal if selecting it prompted them to continue with the setup process. But if that's a more involved change, I also think this is fine for now, given the deprioritization of invoices.

trjExpensify · 2026-01-22T02:14:31Z

Cool, sounds good if it's expected right now. 👍

hungvu193

We have another usage of getPaymentSubitem here:

App/src/hooks/usePaymentOptions.ts

Line 166 in 3779ccf

const getPaymentSubitems = (payAsBusiness: boolean) =>

@nyomanjyotisa can you check if we also need to filter out the partially set-up bank account here too?

…tton

nyomanjyotisa · 2026-01-22T08:06:17Z

@hungvu193 I'm not sure about the scenario where the Pay button displayed as a secondary action button. But for consistency, I think we should filter it there as well

New-Expensify.mp4

I hardcoded the PAY action to always show for testing

App/src/components/MoneyReportHeader.tsx

Lines 1515 to 1527 in 3779ccf

    
               [CONST.REPORT.SECONDARY_ACTIONS.PAY]: { 
        
                   text: translate('iou.settlePayment', {formattedAmount: totalAmount}), 
        
                   icon: expensifyIcons.Cash, 
        
                   rightIcon: expensifyIcons.ArrowRight, 
        
                   value: CONST.REPORT.SECONDARY_ACTIONS.PAY, 
        
                   backButtonText: translate('iou.settlePayment', {formattedAmount: totalAmount}), 
        
                   sentryLabel: CONST.SENTRY_LABEL.MORE_MENU.PAY, 
        
                   subMenuItems: Object.values(paymentButtonOptions), 
        
               }, 
        
           }; 
        
           const applicableSecondaryActions = secondaryActions 
        
               .map((action) => secondaryActionsImplementation[action]) 
        
               .filter((action) => action?.shouldShow !== false && action?.value !== primaryAction);

hungvu193 · 2026-01-22T08:19:49Z

Cool. Thanks

hungvu193 · 2026-01-22T08:29:12Z

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

Screen.Recording.2026-01-22.at.15.59.40.mov

Android: mWeb Chrome

Screen.Recording.2026-01-22.at.16.02.12.mov

iOS: HybridApp

Screen.Recording.2026-01-22.at.16.17.45.mov

iOS: mWeb Safari

Screen.Recording.2026-01-22.at.16.03.17.mov

MacOS: Chrome / Safari

Screen.Recording.2026-01-22.at.15.27.51.mov

hungvu193 · 2026-01-22T08:39:25Z

@nyomanjyotisa Could you merge main again? I'm unable to open the report because of maximum render depth issue 😂

hungvu193 · 2026-01-22T08:47:01Z

Oh it's on main. Looks like it's a deploy blocker that's pending fix.

hungvu193

LGTM

lakchote · 2026-01-26T16:37:09Z

@nyomanjyotisa could you please solve conflicts?

nyomanjyotisa · 2026-01-27T01:00:25Z

@lakchote conflict resolved

lakchote

LGTM

OSBotify · 2026-01-27T07:33:56Z

✋ 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 · 2026-01-27T20:12:27Z

🚀 Deployed to staging by https://github.com/lakchote in version: 9.3.10-0 🚀

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

OSBotify · 2026-01-28T22:57:40Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.10-6 🚀

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

Fix: Partially set up bank account appears in the payment dropdown bu…

521936b

…tton

melvin-bot bot assigned nyomanjyotisa Jan 21, 2026

Fix: Partially set up bank account appears in the payment dropdown bu…

2a5672b

…tton

nyomanjyotisa marked this pull request as ready for review January 21, 2026 06:58

nyomanjyotisa requested review from a team as code owners January 21, 2026 06:58

melvin-bot bot requested review from hungvu193 and trjExpensify January 21, 2026 06:58

melvin-bot bot removed request for a team January 21, 2026 06:58

trjExpensify reviewed Jan 21, 2026

View reviewed changes

hungvu193 reviewed Jan 22, 2026

View reviewed changes

Fix: Partially set up bank account appears in the payment dropdown bu…

f4a5c70

…tton

hungvu193 approved these changes Jan 22, 2026

View reviewed changes

melvin-bot bot requested a review from lakchote January 22, 2026 09:05

Merge branch 'main' into issue-79563

2d0bffa

lakchote approved these changes Jan 27, 2026

View reviewed changes

lakchote merged commit 71844e9 into Expensify:main Jan 27, 2026
29 checks passed

OSBotify mentioned this pull request Jan 27, 2026

Deploy Checklist: New Expensify 2026-01-27 #80656

Closed

70 tasks

Conversation

nyomanjyotisa commented Jan 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov bot commented Jan 21, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

melvin-bot bot commented Jan 21, 2026

Uh oh!

trjExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

joekaufmanexpensify commented Jan 21, 2026

Uh oh!

trjExpensify commented Jan 22, 2026

Uh oh!

hungvu193 left a comment

Choose a reason for hiding this comment

Uh oh!

nyomanjyotisa commented Jan 22, 2026

Uh oh!

hungvu193 commented Jan 22, 2026

Uh oh!

hungvu193 commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

hungvu193 commented Jan 22, 2026

Uh oh!

hungvu193 commented Jan 22, 2026

Uh oh!

hungvu193 left a comment

Choose a reason for hiding this comment

Uh oh!

lakchote commented Jan 26, 2026

Uh oh!

nyomanjyotisa commented Jan 27, 2026

Uh oh!

lakchote left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Jan 27, 2026

Uh oh!

OSBotify commented Jan 27, 2026

Uh oh!

OSBotify commented Jan 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

nyomanjyotisa commented Jan 21, 2026 •

edited

Loading

codecov bot commented Jan 21, 2026 •

edited by github-actions bot

Loading

hungvu193 commented Jan 22, 2026 •

edited

Loading