Skip to content

Add personal card empty state, warning flow and upgrade flow#83211

Merged
amyevans merged 40 commits intoExpensify:mainfrom
callstack-internal:add-personal-card
Mar 5, 2026
Merged

Add personal card empty state, warning flow and upgrade flow#83211
amyevans merged 40 commits intoExpensify:mainfrom
callstack-internal:add-personal-card

Conversation

@narefyev91
Copy link
Contributor

@narefyev91 narefyev91 commented Feb 23, 2026

Explanation of Change

Add personal card empty state, warning flow and upgrade flow

Fixed Issues

$ #78390
$ #78393
$ #78394
$ #78395

Tests

Empty flow:

  1. Open wallet page
  2. Verify that user sees Add personal card button
  3. If user does not have any company card setup - banner in the bottom should be shown

Upgrade path:

  1. Have more than 2 personal cards and not paid workspace
  2. Click on Add personal card - Verify that upgrade screens with Create new workspace is shown
  3. Create new workspace - verify that new workspaces created/success page is shown

Warning page:

  1. User should be a part of workspace with company card existing direct feed
  2. Click on add personal card - verify that warning message is shown with 2 buttons "personal card" and "ask admin"
  3. Ask admin should open expense chat of the workspace
  4. If user is admin - should see different copy and 2 buttons "personal card" and "company card"
  • Verify that no errors appear in the JS console

Offline tests

Should working the same as in online

QA Steps

Pre-condition: user is on the personalCardImport beta

Empty flow:

  1. Open wallet page
  2. Verify that user sees Add personal card button
  3. If user does not have any company card setup - banner in the bottom should be shown

Upgrade path:

  1. Have more than 2 personal cards and not paid workspace
  2. Click on Add personal card - Verify that upgrade screens with Create new workspace is shown
  3. Create new workspace - verify that new workspaces created/success page is shown

Warning page:

  1. User should be a part of workspace with company card existing direct feed
  2. Click on add personal card - verify that warning message is shown with 2 buttons "personal card" and "ask admin"
  3. Ask admin should open expense chat of the workspace
  4. If user is admin - should see different copy and 2 buttons "personal card" and "company card"

For users NOT on the beta:
Verify Add personal card button does NOT show on the Wallet page

  • 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:
    • 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

Web web1 web2 web3 web4 web5
Mobile mobile1 mobile2 mobile3 mobile4 mobile5

# Conflicts:
#	src/SCREENS.ts
#	src/libs/CardUtils.ts
# Conflicts:
#	src/libs/Navigation/AppNavigator/ModalStackNavigators/index.tsx
#	src/libs/Navigation/types.ts
#	src/pages/settings/Wallet/WalletPage/index.tsx
#	src/pages/workspace/workflows/WorkspaceWorkflowsPage.tsx
# Conflicts:
#	src/pages/settings/Wallet/WalletPage/index.tsx
# Conflicts:
#	src/pages/settings/Wallet/WalletPage/index.tsx
@melvin-bot
Copy link

melvin-bot bot commented Feb 23, 2026

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

@narefyev91
Copy link
Contributor Author

@joekaufmanexpensify i think you could run ad-hoc and test these 3 issues:
#78390,
#78393,
#78394

@github-actions
Copy link
Contributor

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

@github-actions

This comment has been minimized.

@codecov
Copy link

codecov bot commented Feb 23, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/CONST/index.ts 94.30% <ø> (ø)
src/ROUTES.ts 15.34% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/components/Icon/chunks/illustrations.chunk.ts 0.00% <ø> (ø)
src/components/Section/index.tsx 92.00% <100.00%> (ø)
src/libs/CardFeedUtils.ts 88.75% <100.00%> (ø)
src/libs/CardUtils.ts 81.91% <100.00%> (ø)
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 75.00% <ø> (ø)
src/libs/actions/ImportTransactions.ts 59.01% <ø> (ø)
... and 12 more
... and 17 files with indirect coverage changes

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #83211.

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ⏩ SKIPPED ⏩
The build for Android was skipped The build for iOS was skipped
Web 🕸️
https://83211.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@joekaufmanexpensify
Copy link
Contributor

BUG:

Not seeing Company cards warning - employee when accessing the personal card flow from a non-admin member of a workspace with a company card feed. The admin warning is working as expected for admins though.

2026-02-24_12-52-59.mp4

@joekaufmanexpensify
Copy link
Contributor

Maybe BUG: Company cards ad banner is not flush with bottom of Assigned cards section

It was in the design doc . I feel like that might look slightly better, cc @Expensify/design in case you have thoughts on this.

Note: the Import transactions button is behind a separate beta and will be moving inside of the Add personal card flow once this PR is done. So while its placement looks odd now, it shouldn't actually be shipped to customers like this. cc @dylanexpensify

Design doc

image

PR

Screenshot 2026-02-24 at 12 54 54 PM

@joekaufmanexpensify
Copy link
Contributor

@narefyev91 is there a reason this list of countries is not alphabetical? I would expect it to be.

image

@joekaufmanexpensify
Copy link
Contributor

I see it isn't actually possible to connect new personal cards yet on the adhoc, but will continue once it is 👍

@shawnborton
Copy link
Contributor

Agree with you Joe, looks like it's not matching the DD specs.

@narefyev91
Copy link
Contributor Author

BUG:

Not seeing Company cards warning - employee when accessing the personal card flow from a non-admin member of a workspace with a company card feed. The admin warning is working as expected for admins though.

2026-02-24_12-52-59.mp4

@joekaufmanexpensify for this one - issue related to missing data in Onyx. To make it working currently your test user should open workspace with company card feed. After that on wallet page you would be able to see warning RHP.
Problem here - that OpenPaymentsPage API call is not return "sharedNVP_private_domain_member_18441278" keys
(which has information about available feeds).
To make it working we need to adjust OpenPaymentsPage to return that data.

Before going to workspace:
Screenshot 2026-02-25 at 10 25 48

Goes to workspace:
Screenshot 2026-02-25 at 10 29 28

After coming back from workspace with feed:
Screenshot 2026-02-25 at 10 26 14

Click on add personal card:
Screenshot 2026-02-25 at 10 26 30

@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

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

@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #83211.

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ⏩ SKIPPED ⏩
The build for Android was skipped The build for iOS was skipped
Web 🕸️
https://83211.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@joekaufmanexpensify
Copy link
Contributor

@ShridharGoel could you check on the Travel CVV thing since you already have an account with that setup?

@joekaufmanexpensify
Copy link
Contributor

Confirmed BUG: showing HTML tags in employee and admin warnings and Maybe BUG: Ask your admin button for employee warning not working are fixed 👍

@joekaufmanexpensify
Copy link
Contributor

Started a thread on this archived workspaces thing so we can align more quickly.

@joekaufmanexpensify
Copy link
Contributor

@Expensify/design is there supposed to be a standard amount of space between the header and title on pages in a "flow" to add something? I noticed the gap at the top on a few of the personal card pages looks slightly larger than in the bank account flow, but not sure if this is a standardized thing.

Existing bank account flow

image

New personal card warning pages

image image

@ShridharGoel
Copy link
Contributor

Travel card placement looks fine now

Screen.Recording.2026-03-05.at.1.41.34.PM.mov

@narefyev91
Copy link
Contributor Author

@Expensify/design is there supposed to be a standard amount of space between the header and title on pages in a "flow" to add something? I noticed the gap at the top on a few of the personal card pages looks slightly larger than in the bank account flow, but not sure if this is a standardized thing.

Existing bank account flow

image ### New personal card warning pages image image

yeah it should be the same padding - already updated. Thanks!

@ShridharGoel
Copy link
Contributor

ShridharGoel commented Mar 5, 2026

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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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-03-05.at.7.39.21.PM.mov
Android: mWeb Chrome
Screen.Recording.2026-03-05.at.7.40.03.PM.mov
iOS: HybridApp
Screen.Recording.2026-03-05.at.7.24.49.PM.mov
iOS: mWeb Safari
Screen.Recording.2026-03-05.at.7.25.45.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-03-05.at.7.20.05.PM.mov

@ShridharGoel
Copy link
Contributor

@narefyev91 @joekaufmanexpensify Is it expected to not see the company cards banner here?

Screen.Recording.2026-03-05.at.7.22.23.PM.mov

@joekaufmanexpensify
Copy link
Contributor

Yes, expected. We're only supposed to show it on the empty state. It's removed when the user has any kind of personal or company card.

Copy link
Contributor

@amyevans amyevans left a comment

Choose a reason for hiding this comment

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

Looks great! 🚀

@amyevans amyevans merged commit 8575dc0 into Expensify:main Mar 5, 2026
31 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2026

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

@OSBotify
Copy link
Contributor

OSBotify commented Mar 5, 2026

✋ 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
Contributor

OSBotify commented Mar 6, 2026

🚀 Deployed to staging by https://github.com/amyevans in version: 9.3.32-0 🚀

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

@mitarachim
Copy link

Deploy Blocker #84357 was identified to be related to this PR.

@kavimuru
Copy link

kavimuru commented Mar 6, 2026

@narefyev91 @amyevans @joekaufmanexpensify
Pre-condition: user is on the personalCardImport beta

Is applause.expensifail.com domain is under beta to test this one? Also applause cannot add personal cards.

@joekaufmanexpensify
Copy link
Contributor

@kavimuru you can hold off from testing since it is behind beta and relies on another PRs to be fully functional. I will check it off

@OSBotify
Copy link
Contributor

OSBotify commented Mar 6, 2026

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.32-3 🚀

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.

10 participants