[Due for payment 2025-05-20] [Due for payment 2025-05-14] Web - Wallet - Physical card RHP opens after deactivating virtual card with wrong MC

[IuliiaHerets]

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.1.41-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://github.com/Expensify/Web-Expensify/pull/46007
Email or phone of affected tester (no customers): nathanmulugetatesting+3702@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 11 / Chrome
App Component: User Settings

Action Performed:

1. Navigate to staging.new.expensify.com
2. Create a workspace > Connect with a bank account > Assign both a physical and virtual card to yourself
3. Navigate to wallet
4. Open the virtual card > Report virtual card fraud > Deactivate card
5. Enter a random number (Wrong magic code)
6. Click on "Got it, thanks!"

Expected Result:

Virtual card RHP opens

Actual Result:

Physical card RHP opens

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

Bug6824479_1746634441046.Bug6824408_1746630794848_bandicam_2025-05-07_16-51-18-984.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

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

[danieldoglas]

Doesn't look like a backend deploy blocker. Removing DeployBlocker