Skip to content

Implement freeze card option#81880

Merged
dangrous merged 15 commits into
Expensify:mainfrom
ShridharGoel:frozenCard2
Feb 17, 2026
Merged

Implement freeze card option#81880
dangrous merged 15 commits into
Expensify:mainfrom
ShridharGoel:frozenCard2

Conversation

@ShridharGoel

@ShridharGoel ShridharGoel commented Feb 9, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Implement freeze card option.

Fixed Issues

$ #81638
PROPOSAL:

Tests

Precondition: Have an Expensify card.

  1. Enable the freeze card beta.
  2. Go to Account > Wallet.
  3. Click on an Expensify card.
  4. Verify the freeze option shows.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// 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
    • MacOS: Desktop
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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:
    • 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 Screenshot 2026-02-09 at 11 49 47 PM
Android: mWeb Chrome Screenshot 2026-02-09 at 11 50 15 PM
iOS: Native Screenshot 2026-02-09 at 10 24 17 PM
iOS: mWeb Safari Screenshot 2026-02-09 at 10 25 41 PM
MacOS: Chrome / Safari Screenshot 2026-02-09 at 9 48 40 PM

@ShridharGoel ShridharGoel requested review from a team as code owners February 9, 2026 16:18
@melvin-bot melvin-bot Bot requested review from JmillsExpensify and truph01 and removed request for a team and JmillsExpensify February 9, 2026 16:18
@melvin-bot

melvin-bot Bot commented Feb 9, 2026

Copy link
Copy Markdown

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

3 similar comments
@melvin-bot

melvin-bot Bot commented Feb 9, 2026

Copy link
Copy Markdown

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

@melvin-bot

melvin-bot Bot commented Feb 9, 2026

Copy link
Copy Markdown

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

@melvin-bot

melvin-bot Bot commented Feb 9, 2026

Copy link
Copy Markdown

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

@melvin-bot

melvin-bot Bot commented Feb 9, 2026

Copy link
Copy Markdown

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

Comment thread src/libs/Permissions.ts Outdated
Comment thread src/libs/CardUtils.ts
@ShridharGoel

Copy link
Copy Markdown
Contributor Author

@Pujan92 will be reviewing.

@ShridharGoel ShridharGoel marked this pull request as draft February 9, 2026 16:21
Comment thread src/pages/settings/Wallet/ExpensifyCardPage/index.tsx
);
}}
/>
{isBetaEnabled(CONST.BETAS.FREEZE_CARD) && isCardHolder && !isCardFrozen(currentPhysicalCard) && (

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ PERF-2 (docs)

Reasoning: The expensive operations isBetaEnabled(CONST.BETAS.FREEZE_CARD) and isCardFrozen(currentPhysicalCard) are performed before checking the simple condition isCardHolder. If isCardHolder is false, the expensive checks are wasted.

Suggested fix: Reorder the conditions to check the simplest ones first:

{isCardHolder && isBetaEnabled(CONST.BETAS.FREEZE_CARD) && !isCardFrozen(currentPhysicalCard) && (
    <MenuItem
        icon={expensifyIcons.FreezeCard}
        title={translate('cardPage.freezeCard')}
        style={styles.mt3}
        disabled={isOffline}
    />
)}

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think current condition is better since it will stop checking if beta is not enabled.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dd5c63bbfb

ℹ️ 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".

Comment thread src/libs/Permissions.ts Outdated
@ShridharGoel ShridharGoel marked this pull request as ready for review February 9, 2026 16:41
@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

These rows look very far apart, could you confirm the spacing and layout here?
CleanShot 2026-02-10 at 10 09 41@2x

Might wanna run a test build so I can play around as well

@shawnborton

Copy link
Copy Markdown
Contributor

Happy to a run test build, one sec 🚀

@MariaHCD MariaHCD removed the request for review from truph01 February 13, 2026 09:42

@MariaHCD MariaHCD left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall!

There are some type check failures:

Error: tests/unit/CardUtilsTest.ts(1885,26): error TS2352: Conversion of type '{ state: 7; nameValuePairs: { frozen: boolean; }; }' to type '{ cardID: number; state: ValueOf<{ readonly STATE_NOT_ISSUED: 2; readonly OPEN: 3; readonly NOT_ACTIVATED: 4; readonly STATE_DEACTIVATED: 5; readonly CLOSED: 6; readonly STATE_SUSPENDED: 7; }>; ... 24 more ...; nameValuePairs?: ({ ...; } & ... 2 more ... & OfflineFeedback<...>) | undefined; } & OfflineFeedback<...>' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Type '{ state: 7; nameValuePairs: { frozen: boolean; }; }' is missing the following properties from type '{ cardID: number; state: ValueOf<{ readonly STATE_NOT_ISSUED: 2; readonly OPEN: 3; readonly NOT_ACTIVATED: 4; readonly STATE_DEACTIVATED: 5; readonly CLOSED: 6; readonly STATE_SUSPENDED: 7; }>; ... 24 more ...; nameValuePairs?: ({ ...; } & ... 2 more ... & OfflineFeedback<...>) | undefined; }': cardID, bank, domainName, lastUpdated, fraud
Error: tests/unit/CardUtilsTest.ts(1903,26): error TS2352: Conversion of type '{ state: 3; nameValuePairs: { frozen: boolean; }; }' to type '{ cardID: number; state: ValueOf<{ readonly STATE_NOT_ISSUED: 2; readonly OPEN: 3; readonly NOT_ACTIVATED: 4; readonly STATE_DEACTIVATED: 5; readonly CLOSED: 6; readonly STATE_SUSPENDED: 7; }>; ... 24 more ...; nameValuePairs?: ({ ...; } & ... 2 more ... & OfflineFeedback<...>) | undefined; } & OfflineFeedback<...>' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Type '{ state: 3; nameValuePairs: { frozen: boolean; }; }' is missing the following properties from type '{ cardID: number; state: ValueOf<{ readonly STATE_NOT_ISSUED: 2; readonly OPEN: 3; readonly NOT_ACTIVATED: 4; readonly STATE_DEACTIVATED: 5; readonly CLOSED: 6; readonly STATE_SUSPENDED: 7; }>; ... 24 more ...; nameValuePairs?: ({ ...; } & ... 2 more ... & OfflineFeedback<...>) | undefined; }': cardID, bank, domainName, lastUpdated, fraud

@MariaHCD MariaHCD left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ShridharGoel could you take a look at the merge conflicts?

@codecov

codecov Bot commented Feb 15, 2026

Copy link
Copy Markdown

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/CONST/index.ts 87.39% <ø> (ø)
...rc/components/Icon/chunks/expensify-icons.chunk.ts 0.00% <ø> (ø)
src/libs/CardUtils.ts 77.21% <100.00%> (+0.09%) ⬆️
.../pages/settings/Wallet/ExpensifyCardPage/index.tsx 60.60% <100.00%> (-0.62%) ⬇️
... and 7 files with indirect coverage changes

@Pujan92

Pujan92 commented Feb 16, 2026

Copy link
Copy Markdown
Contributor

PR reviewer checklist failed bcoz it considers first checklist comment of @truph01. @truph01 can you plz delete comment #81880 (comment)

@Expensify Expensify deleted a comment from truph01 Feb 16, 2026
@MariaHCD

Copy link
Copy Markdown
Contributor

All yours @dangrous !

@dangrous dangrous merged commit b4269e7 into Expensify:main Feb 17, 2026
33 of 36 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 @dangrous has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ 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

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/dangrous in version: 9.3.21-0 🚀

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

@kavimuru

kavimuru commented Feb 18, 2026

Copy link
Copy Markdown

@ShridharGoel @MariaHCD Are expensifail accounts behind beta to have freeze card feature?

@IuliiaHerets

Copy link
Copy Markdown

@ShridharGoel, no freeze card option on the QA side.
Can you check it internally?

cc @MariaHCD @dangrous

image

@ShridharGoel

Copy link
Copy Markdown
Contributor Author

@MariaHCD Do you think it will be fine to QA test this feature once it is ready for release 1 ?

@MariaHCD

Copy link
Copy Markdown
Contributor

For now, QA is not under the Freeze Card beta as the feature is still a work in progress.

Once we have Release 1 ready, then we will add QA to the beta and it will be ready for testing 👍🏼

@IuliiaHerets

Copy link
Copy Markdown

@MariaHCD thanks. Can we check it off for now?

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.21-4 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.