fix: Frozen card cannot be replaced, but confirmation page show success description

[samranahm]

Explanation of Change

Fixed Issues

$ #84776
PROPOSAL: #84776 (comment)

Tests

Precondition:

• Expensify card is setup in workspace
• Admin assign a virtual Expensify card to a workspace member

Test - 01

1. Workspace member open Account > Wallet
2. Click on Expensify card and freeze the card
3. Press "Report virtual card fraud" > Deactivate card
4. Enter the magic code and on confirmation page verify the description

Card fraud reported
We’ve permanently deactivated your existing card. When you go back to view your card details, you’ll have a new virtual card available.

5. Press "Got it, thanks!" and verify user navigate to newly issued card

Test - 02

1. Admin assign a virtual Expensify card to a workspace member and freeze the card
2. Workspace member open Account > Wallet
3. Open the Expensify card and verify "Ask to unfreeze" and "Report virtual card fraud" button is available
4. Press "Report virtual card fraud" > Deactivate card > Enter the magic code and verify confirmation page open

Card fraud reported
Your card was permanently deactivated. Please contact an admin to issue a new card.

5. Press "Got it, thanks!" and verify user go back to Wallet page.
6. Open the cardholder's workspace chat and verify a new system message is posted

@cardholder's Expensify Card (ending in 1234) was permanently deactivated. Please contact an admin to issue a new card.

• Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as test

// TODO: These must be filled out, or the issue title must include "[No QA]."

• 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
• 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 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: https://expensify.slack.com/archives/C01GTK53T8Q/p1778688387618199
  • 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.mWeb.Chrome.mp4

iOS: Native

IOS.Native.mp4

iOS: mWeb Safari

IOS.mWeb.Safari.mp4

MacOS: Chrome / Safari

macOS.Chrome.Admin.frozen.card.mov

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[melvin-bot]

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

[Copilot]

Pull request overview

Updates the “Report virtual card fraud” confirmation screen copy so that users with a frozen virtual Expensify Card aren’t incorrectly told a replacement card will be issued.

Changes:

• Selects an alternate confirmation description when the affected card is in a suspended/frozen state.
• Adds a new reportFraudConfirmationPage.descriptionCardNotReplaced translation string across supported languages.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/pages/settings/Wallet/ReportVirtualCardFraudConfirmationPage.tsx	Chooses between the standard vs. “card not replaced” confirmation description based on card status.
src/languages/en.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/de.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/es.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/fr.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/it.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/ja.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/nl.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/pl.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/pt-BR.ts	Adds new localized string for the “card not replaced while frozen” scenario.
src/languages/zh-hans.ts	Adds new localized string for the “card not replaced while frozen” scenario.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/CONST/index.ts	93.89% <ø> (ø)
...nbox/report/actionContents/ActionContentRouter.tsx	92.00% <100.00%> (+0.05%)	⬆️
src/libs/actions/Card.ts	0.00% <0.00%> (ø)
.../Wallet/ReportVirtualCardFraudConfirmationPage.tsx	0.00% <0.00%> (ø)
...Wallet/ReportVirtualCardFraudVerifyAccountPage.tsx	0.00% <0.00%> (ø)
... and 40 files with indirect coverage changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3d01e5df1d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[joekaufmanexpensify]

I am not sure about the solution we decided on here. Let's discuss.

[samranahm]

Updated the PR to meet the latest requirements.

[MariaHCD]

@eh2077 could you please review this PR? Thanks!

[eh2077]

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 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-05-22.at.12.26.41.AM.mov

Screen.Recording.2026-05-22.at.12.27.03.AM.mov

Android: mWeb Chrome

Screen.Recording.2026-05-22.at.12.19.08.AM.mov

iOS: HybridApp

Screen.Recording.2026-05-22.at.12.21.57.AM.mov

iOS: mWeb Safari

Screen.Recording.2026-05-22.at.12.17.40.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2026-05-22.at.12.09.57.AM.mov

[eh2077]

I can hardly test the issue as the magic code command ResendValidateCode is strictly rate limited. It seems limit access by account, so switch IP with VPN doesn't work.

@samranahm @MariaHCD do you have any ideas to mitigate this?

[samranahm]

@eh2077 Yes this happens a lot with me too during testing but I retry after 5-7 minutes and get the code successfully.

[samranahm]

@MariaHCD @dominictb Can you help regarding this?

[dominictb]

Maybe I should setup expensify card in a new workspace to test?

@eh2077 Please try this. Create the new workspace and connect bank account on dev env.

[eh2077]

@dominictb tried with a new workspace but got error The domain is not configured for Expensify Cards.

Screen.Recording.2026-05-21.at.11.04.45.PM.mov

[eh2077]

@samranahm Mind assigning virtual cards to my tests accounts from your workspace, so I can continue test? ericwdev001+d3@gmail.com, ericwdev001+d3@gmail.com and ericwdev001+88831@gmail.com

[eh2077]

hmm, tried with brand new account on staging server but can't bypass bank account verification

[MariaHCD]

Hmm, okay, strange - I have a test card workspace. @eh2077 I will assign two cards to ericwdev001+d3@gmail.com

1. A virtual card that you can freeze to test the user-freeze flow (Test 1)
2. And another Card that will be frozen by the admin i.e. me (Test 2)

[MariaHCD]

@eh2077 I've issued these two cards to ericwdev001+d3@gmail.com

[eh2077]

@MariaHCD Thanks for the help!

looks good and works well, checklist here #88831 (comment)

[samranahm]

@samranahm Mind assigning virtual cards to my tests accounts from your workspace, so I can continue test? ericwdev001+d3@gmail.com, ericwdev001+d3@gmail.com and ericwdev001+88831@gmail.com

Sorry @eh2077 for the late response, I was traveling. Happy to see @MariaHCD already assigned the cards and all tests passed!

[MariaHCD]

Looks good overall!

@samranahm I noticed that your screen recordings might not be up-to-date. Could you double check, please? We want to make sure the recordings reflect the actual changes in the PR.

[samranahm]

Ahh, these're outdated copies and I forgot to update the videos. I'll upload the new recordings shortly.

[samranahm]

@MariaHCD I've updated the videos please take a look.

[MariaHCD]

@samranahm looks like there's a merge conflict, could you merge main? 👀

[samranahm]

@MariaHCD conflict clear and PR ready, please take a look

[github-actions]

🚧 @MariaHCD 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, and Web. Happy testing! 🧪🧪
Built from App PR #88831.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-7e91ae5466f-393ba1f-004606076c3bbbe67360ea5a5e993d4e65461f8c/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-7e91ae5-393ba1f-c87e6d03e0571fef8623b5c203b2bfc3ea99b833/index.html

Web 🕸️
https://88831.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[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/MariaHCD in version: 9.3.81-0 🚀

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

[MelvinBot]

Yes, help site changes are needed. PR #88831 introduces a new scenario where reporting fraud on an admin-frozen card deactivates it without automatic replacement — the user must contact their admin for a new card.

The article docs/articles/new-expensify/expensify-card/Disputing-Expensify-Card-Transactions.md previously said "Follow the prompts to deactivate your card and request a replacement" which doesn't account for this case.

Draft PR created: #91595

Changes:

• Updated step 5 of the fraud reporting flow to remove the assumption of automatic replacement
• Added a Note clarifying both outcomes (self-frozen → auto-replacement, admin-frozen → contact admin)
• Added a new FAQ: "What happens when I report fraud on a card frozen by my admin?"

[jponikarchuk]

@samranahm @joekaufmanexpensify @MariaHCD @eh2077 Could you please confirm what is the expected result for step 6 test 2? We get that system message in workspace chat, but not in Admin room. Is this WAD or we should create an issue?

bandicam.2026-05-25.16-34-04-389.mp4

[MariaHCD]

@jponikarchuk the system message should be in the cardholder's workspace chat not in the admins room! So it is working as designed - just that there was a typo in the test instructions.

[samranahm]

My bad, that was just muscle memory from the system messages in the admins room. Thanks @MariaHCD for correcting it 🙌.

[OSBotify]

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.81-2 🚀

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