Wallet - Copilot not able to add United States bank account on the wallet page.

[mitarachim]

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.2.15-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #70408
Email or phone of affected tester (no customers): mysticque00@gmail.com
Issue reported by: Applause Internal Team
Device used: iPhone 13 / iOS 18.5
App Component: User Settings

Action Performed:

Precondition:

1. User B (Main account) already set user A as a copilot
2. Make sure that the copilot is full access

Steps :

1. Login with user A
2. Switch to user B
3. Open the wallet page
4. Click on Add bank account -> choose United States

Expected Result:

User directed to add United States bank account flow

Actual Result:

main account get blocked from adding United States bank account. "the not so fast" page displayed and indicated as the copilot account

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6946671_1758075297133.video_2025-09-17_09-11-59.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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.

[melvin-bot]

Triggered auto assignment to @cristipaval (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.