Skip to content

Add personal card steps#84042

Merged
amyevans merged 27 commits into
Expensify:mainfrom
callstack-internal:add-personal-card-steps
Mar 26, 2026
Merged

Add personal card steps#84042
amyevans merged 27 commits into
Expensify:mainfrom
callstack-internal:add-personal-card-steps

Conversation

@narefyev91

@narefyev91 narefyev91 commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Add personal card with Plaid or direct bank US/non US

Fixed Issues

$ #78392, #78392, #78396, #84779
PROPOSAL:

Tests

Add personal card:

  1. Go to wallet page
  2. Click on Add personal card
  3. Choose US/non-US
  4. Choose either direct bank/mock bank or Other for US - and plaid for non-US
  5. Finish connection to bank
  6. Verify that use get to success personal card add screen
  7. Verify that new card appears in wallet page

Check error during connection:

  1. Go to wallet page
  2. Click on Add personal card
  3. Choose US/non-US
  4. Choose either direct bank/mock bank or Other for US - and plaid for non-US
  5. Finish connection to bank (not successfull)
  6. Verify that use get to error page
  7. Verify that user could start plaid connection
  • Verify that no errors appear in the JS console

Offline tests

Feature is not available offline

QA Steps

Add personal card:

  1. Go to wallet page
  2. Click on Add personal card
  3. Choose US/non-US
  4. Choose either direct bank/mock bank or Other for US - and plaid for non-US
  5. Finish connection to bank
  6. Verify that use get to success personal card add screen
  7. Verify that new card appears in wallet page

Check error during connection:

  1. Go to wallet page
  2. Click on Add personal card
  3. Choose US/non-US
  4. Choose either direct bank/mock bank or Other for US - and plaid for non-US
  5. Finish connection to bank (not successfull)
  6. Verify that use get to error page
  7. Verify that user could start plaid connection
  • 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

Details
web.mov

@melvin-bot

melvin-bot Bot commented Mar 3, 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

# Conflicts:
#	src/ROUTES.ts
#	src/SCREENS.ts
#	src/libs/Navigation/AppNavigator/ModalStackNavigators/index.tsx
#	src/libs/Navigation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts
#	src/libs/Navigation/linkingConfig/config.ts
#	src/libs/Navigation/types.ts
@codecov

codecov Bot commented Mar 6, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/CONST/index.ts 95.20% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
...h/SearchList/ListItem/TransactionGroupListItem.tsx 70.83% <ø> (ø)
src/components/Search/index.tsx 0.80% <ø> (+<0.01%) ⬆️
src/hooks/useSearchSections.ts 100.00% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
src/libs/CardFeedUtils.ts 89.47% <100.00%> (+0.12%) ⬆️
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 76.92% <ø> (ø)
... and 27 more
... and 23 files with indirect coverage changes

# Conflicts:
#	src/libs/Navigation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts
@narefyev91

Copy link
Copy Markdown
Contributor Author

@joekaufmanexpensify @amyevans - i think we could also start reviewing this one. Generally @amyevans could also test on new API for plaid. And @joekaufmanexpensify on direct bank account setup. I was able to test with Mock bank - was able to get successfully cards.

@narefyev91

Copy link
Copy Markdown
Contributor Author

@codex review

@github-actions

github-actions Bot commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@narefyev91 narefyev91 marked this pull request as ready for review March 10, 2026 09:51
@narefyev91 narefyev91 requested review from a team as code owners March 10, 2026 09:51
@melvin-bot melvin-bot Bot requested review from ShridharGoel and heyjennahay and removed request for a team March 10, 2026 09:51
@melvin-bot

melvin-bot Bot commented Mar 10, 2026

Copy link
Copy Markdown

@ShridharGoel 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 removed the request for review from a team March 10, 2026 09:51
Comment thread src/hooks/useImportPersonalPlaidAccounts.ts Outdated
Comment thread src/hooks/useUpdatePersonalCardBrokenConnection.ts
Comment thread src/pages/settings/Wallet/PersonalCards/steps/BankConnection/index.tsx Outdated
Comment thread src/pages/settings/Wallet/PersonalCards/steps/PlaidConnectionStep.tsx Outdated
Comment thread src/pages/settings/Wallet/PersonalCards/steps/PlaidConnectionStep.tsx Outdated
Comment thread src/pages/settings/Wallet/PersonalCards/steps/SelectCountryStep.tsx Outdated
Comment thread src/pages/settings/Wallet/PersonalCards/steps/PlaidConnectionStep.tsx Outdated
Comment thread src/pages/settings/Wallet/PersonalCards/steps/PlaidConnectionStep.tsx Outdated
@ShridharGoel

Copy link
Copy Markdown
Contributor

Android app keeps crashing on the plaid screen, anyone able to repro?

Screen.Recording.2026-03-26.at.1.32.05.AM.mov

@amyevans amyevans 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.

A couple things to note but overall looking great!

Comment thread src/pages/settings/Wallet/PersonalCards/steps/PlaidConnectionStep.tsx Outdated
Comment thread src/types/onyx/PersonalCard.ts Outdated
Comment thread src/types/onyx/PersonalCard.ts Outdated
Comment thread src/types/onyx/PersonalCard.ts Outdated
Comment thread src/types/onyx/PersonalCard.ts Outdated
Comment thread src/types/onyx/PersonalCard.ts Outdated
Comment thread src/libs/actions/PersonalCards.ts Outdated
Comment thread src/pages/settings/Wallet/PersonalCards/steps/BankConnection/index.tsx Outdated
@narefyev91 narefyev91 requested a review from amyevans March 26, 2026 12:33
@heekinho

Copy link
Copy Markdown
Contributor

Hey, I'm working on avoiding the infinite spinner when re-importing an existing card.
We have the option to wait this one get merged and then I open another PR to main, or we can integrate those small changes into this one before merging.
In any case I'd appreciate any feedback and lemme know how you do prefer. @narefyev91 @amyevans

@amyevans

Copy link
Copy Markdown
Contributor

@heekinho let's do it in a separate PR since this one is ready to go and I don't want to hold it up more, even if the changes are small 😄

I'm doing a final pass now and then will merge!

@amyevans amyevans 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.

:shipit:

@amyevans amyevans merged commit b54b996 into Expensify:main Mar 26, 2026
32 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

I have failed to help you. I let you down and for that I am sorry. Please try again later. This may be due to a Claude outage (check here).

Failure details: https://github.com/Expensify/Expensify/actions/runs/23647037372

@jponikarchuk

Copy link
Copy Markdown

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

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.

@narefyev91 Is there any use of this file?

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.

gentle bump @narefyev91

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.

@jponikarchuk

Copy link
Copy Markdown

This PR failing because of the issue #86600
This issue is reproducible in: iOS app

@jponikarchuk

Copy link
Copy Markdown

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.3.50-8 🚀

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