[Due for payment 2026-03-16] [$250] Expensify Card - Partially set up bank account appears in Settlement account list

[nlemma]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.22-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-5661/folder/13176890/41237383/1198787376
Email or phone of affected tester (no customers): applausetester+sjdionsjods@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Workspace is set up with Expensify card with business bank account.

1. Go to staging.new.expensify.com
2. Go to Account > Wallet.
3. Click Add bank account > Make payments.
4. Select United States.
5. Enter 011401533 as routing number and 11112222 as account number > Next/
6. Close the RHP.
7. Go to workspace settings > Expensify Card.
8. Click Settings > Settlement account.
9. Click on the partially set up bank account.

Expected Result:

Partially set up bank account should not appear in Settlement account list.

Actual Result:

Partially set up bank account appears in Settlement account list.
When user selects the partially set up account, it reverts to the previous account.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7082202_1771492470885.6.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @jliexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022028951277966910192
• Upwork Job ID: 2028951277966910192
• Last Price Increase: 2026-03-03

[melvin-bot]

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When a user partially sets up a bank account (enters routing/account numbers but doesn't complete the full setup flow), that bank account appears in the Expensify Card Settlement account list (Workspace > Expensify Card > Settings > Settlement account). Selecting it causes a brief switch that then reverts to the previous account.

What is the root cause of that problem?

The function getEligibleBankAccountsForCard() in src/libs/CardUtils.ts:388-393 only filters bank accounts by type === 'BUSINESS' and allowDebit === true. It does not check the bank account's state field, so accounts in SETUP, VERIFYING, or PENDING states pass through and appear in the settlement account selector.

The utility function isBankAccountPartiallySetup() already exists in src/libs/BankAccountUtils.ts:14-16 and correctly identifies these incomplete states, but it is not used by the card settlement account filter.

Other similar filters in the codebase correctly exclude partially set up accounts — for example, usePaymentOptions.ts:172-176, useBulkPayOptions.ts:109-113, and WorkflowUtils.ts:518-524 all check isBankAccountPartiallySetup() before including accounts in their lists.

The "revert" behavior happens because updateSettlementAccount in src/libs/actions/Card.ts makes an optimistic update, the backend rejects the partially set up account, and the failureData handler (line 716-726) restores the previous paymentBankAccountID.

What changes do you think we should make in order to solve the problem?

Add a state check to getEligibleBankAccountsForCard() and getEligibleBankAccountsForUkEuCard() in src/libs/CardUtils.ts to exclude partially set up bank accounts. The filter predicate should additionally check !isBankAccountPartiallySetup(bankAccount?.accountData?.state) (importing from BankAccountUtils), consistent with the pattern used elsewhere in the codebase.

What alternative solutions did you explore? (Optional)

An alternative would be to check bankAccount?.accountData?.state === CONST.BANK_ACCOUNT.STATE.OPEN instead, which is slightly more restrictive (also excludes DELETED, LOCKED, VALIDATING states). WorkflowUtils.getEligibleExistingBusinessBankAccounts uses this approach. Either would fix the bug, but using isBankAccountPartiallySetup() is more consistent with the existing pattern in payment option filters.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022028951277966910192