Skip to content

[Payment due @ZhenjaHorbach] [Personal Karma] Add NewDot toggle flow under Save The World#84504

Merged
flodnv merged 30 commits intoExpensify:mainfrom
fedirjh:personal-karma-new-dot
Apr 9, 2026
Merged

[Payment due @ZhenjaHorbach] [Personal Karma] Add NewDot toggle flow under Save The World#84504
flodnv merged 30 commits intoExpensify:mainfrom
fedirjh:personal-karma-new-dot

Conversation

@fedirjh
Copy link
Copy Markdown
Contributor

@fedirjh fedirjh commented Mar 8, 2026

Explanation of Change

This PR adds Personal Karma support to NewDot under /settings/teachersunite.

  • Adds a Personal Karma toggle card in Save The World settings.
  • Connects the toggle to the new UpdatePersonalKarma API action.
  • Shows a confirmation modal when disabling donations.
  • Prompts for adding a payment card when enabling without a billing card, and reverts toggle state if the modal is dismissed.
  • Shows the billing card details when Personal Karma is enabled.
  • Moves Personal Karma text to translations and adds localized strings across all app languages.
  • Adds reusable subtitle-with-link rendering (SectionSubtitleHTML) and reusable billing card rendering (BillingCardDetails) used by related settings sections.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/601130
PROPOSAL:

Tests

  1. Open /settings/teachersunite.
  2. Verify the Personal Karma card is shown with the Personal Karma title and description text:
    Donate $1 to Expensify.org for every $500 you spend each month Learn more.
  3. Toggle Personal Karma on with a payment card present.
  4. Verify the toggle is enabled and the billing card details are shown.
  5. Toggle Personal Karma off.
  6. Verify the stop-donations confirmation modal appears.
  7. Tap cancel and verify Personal Karma stays enabled.
  8. Toggle off again and confirm disable.
  9. Verify Personal Karma is disabled.
  10. Enable again on an account without a billing card.
  11. Verify add-payment-card modal appears.
  12. Dismiss the modal without adding a card and verify the toggle reverts to disabled.
  • Verify that no errors appear in the JS console

Offline tests

  1. Go offline and open /settings/teachersunite.
  2. Toggle Personal Karma on and off.
  3. Verify there is no crash and the UI remains stable.
  4. Reconnect and verify the latest state is synchronized.

QA Steps

Same as tests.

  • 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

CleanShot.2026-03-12.at.00.36.48.mp4
CleanShot.2026-03-12.at.01.35.39.mp4
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

fedirjh added 8 commits March 8, 2026 00:56
- Introduced ONYXKEYS for managing Personal Karma donation states.
- Added new API command and parameters for updating Personal Karma.
- Updated Subscription actions to include a function for updating Personal Karma.
- Added a help URL for Personal and Corporate Karma in the constants.
- Created a new BillingCardDetails component to encapsulate billing card information display.
- Replaced inline billing card rendering in CardSection with the new BillingCardDetails component for improved code organization and readability.
- Removed unused imports and optimized existing code in CardSection.
- Added new translations for the Personal Karma feature in German, English, Spanish, French, Italian, Japanese, Dutch, Polish, Brazilian Portuguese, and Simplified Chinese.
- Each translation includes title, description, prompts for adding a payment card, stopping donations, and the title for the donation card.
- Introduced a new SectionSubtitleHTML component to handle HTML subtitles with optional muted styling and link press handling.
- Replaced instances of RenderHTML in various pages (DomainSamlPage, SecuritySettingsPage, TroubleshootPage, WorkspaceReportsPage, IndividualExpenseRulesSection) with SectionSubtitleHTML for improved consistency and maintainability.
- Updated related styles and props to accommodate the new component.
- Integrated Personal Karma toggle functionality with modals for adding payment cards and disabling donations.
- Added new state management for displaying billing card details and handling user interactions.
- Updated UI components to include SectionSubtitleHTML for improved subtitle rendering.
- Enhanced user experience with confirmation modals for payment card actions and personal karma updates.
@melvin-bot
Copy link
Copy Markdown

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

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 8, 2026

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 93.65% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/ROUTES.ts 15.90% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 76.92% <ø> (ø)
...c/pages/workspace/reports/WorkspaceReportsPage.tsx 0.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 6.87% <0.00%> (-0.01%) ⬇️
...c/pages/settings/Security/SecuritySettingsPage.tsx 0.00% <0.00%> (ø)
... and 9 more
... and 6 files with indirect coverage changes

@fedirjh fedirjh requested a review from flodnv March 8, 2026 04:09
@flodnv
Copy link
Copy Markdown
Contributor

flodnv commented Mar 9, 2026

@garrettmknight do you want to review the product side of this PR?

fedirjh added 2 commits March 10, 2026 01:39
…dPage and CardSection

- Introduced a new PaymentCardDetails component for displaying billing card information.
- Replaced instances of BillingCardDetails with PaymentCardDetails in SaveTheWorldPage and CardSection for consistency and improved functionality.
@flodnv
Copy link
Copy Markdown
Contributor

flodnv commented Mar 10, 2026

@fedirjh checks failed

@trjExpensify trjExpensify self-requested a review March 10, 2026 16:15
Copy link
Copy Markdown
Contributor

@trjExpensify trjExpensify left a comment

Choose a reason for hiding this comment

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

Overall, looking pretty good! Just a few things:

  1. The toggle label supplied in the mocks from @dannymcclain read Enable Personal Karma. The video in the OP is slightly different.
Image Image
  1. The video only shows one case (you have a card already). Can you show the other case where you have to add a payment card so the evidence matches the tests to sense check?

  2. Where did this copy change in the modal come from? Looks different to the mocks supplied in the parent issue.

Parent issue:
Image

PR:

Image

@fedirjh
Copy link
Copy Markdown
Contributor Author

fedirjh commented Mar 11, 2026

3. Where did this copy change in the modal come from?

we have this copy in OldDot. Will update it to match the OP

Screenshot 2026-03-11 at 8 08 28 PM

fedirjh added 3 commits March 11, 2026 23:39
…ature

- Introduced SETTINGS_SAVE_THE_WORLD_ADD_PAYMENT_CARD route in ROUTES.ts.
- Added ADD_PAYMENT_CARD screen to SCREENS.ts.
- Updated TeachersUniteNavigator to include the new ADD_PAYMENT_CARD screen.
- Modified linking configuration to route to the new screen.
- Adjusted SaveTheWorldPage to navigate to the new payment card screen and removed the old modal implementation.
@fedirjh
Copy link
Copy Markdown
Contributor Author

fedirjh commented Mar 12, 2026

@MelvinBot Fix prettier and lint errors?

@MelvinBot
Copy link
Copy Markdown
Contributor

Fixed the prettier and ESLint errors:

  • Prettier: Reordered imports alphabetically in PaymentCardDetails.tsx, SaveTheWorldPage.tsx, CardSection.tsx, and IndividualExpenseRulesSection.tsx
  • ESLint (prefer-early-return): Refactored the useEffect in SaveTheWorldPage.tsx to use an early return instead of wrapping the body in a conditional

@fedirjh fedirjh requested a review from trjExpensify March 12, 2026 00:52
@trjExpensify
Copy link
Copy Markdown
Contributor

Should this be out of WIP now?

@flodnv
Copy link
Copy Markdown
Contributor

flodnv commented Apr 7, 2026

Thanks @ZhenjaHorbach , please let me know when this is ready

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

Thanks @ZhenjaHorbach , please let me know when this is ready

I think I will complete the review tomorrow morning!

@flodnv
Copy link
Copy Markdown
Contributor

flodnv commented Apr 7, 2026 via email

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

Minor comment
But should we add a pending action for Karma toggle?

2026-04-08.16.46.06.mov

As we usually do

2026-04-08.16.46.43.mov

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

And should we have a dynamic price depending on location?
Or we will always have 1$?

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

Minor comment
But we can directly navigate to settings/teachersunite/add-payment-card
Even when we already have a card
I suppose it's better to show Not here page

Снимок экрана 2026-04-08 в 16 55 24

@fedirjh fedirjh requested a review from ZhenjaHorbach April 8, 2026 18:09
@fedirjh
Copy link
Copy Markdown
Contributor Author

fedirjh commented Apr 8, 2026

And should we have a dynamic price depending on location? Or we will always have 1$?

IT should match the oldDot behaviour which was 1$ regardless of the location.

@trjExpensify trjExpensify removed the request for review from heyjennahay April 9, 2026 13:49
Copy link
Copy Markdown
Contributor

@trjExpensify trjExpensify left a comment

Choose a reason for hiding this comment

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

Looks like my earlier review comments were addressed. 👍

@flodnv
Copy link
Copy Markdown
Contributor

flodnv commented Apr 9, 2026

@ZhenjaHorbach could we please get a final review? 🙏

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

I will recheck soon!

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

Not sure that we need to disable the toggle when we have a pending action
But we can leave it as it is

2026-04-09.17.17.43.mov

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

Not sure that we need to disable the toggle when we have a pending action But we can leave it as it is

2026-04-09.17.17.43.mov

But I will approve
Not sure if it's a critical issue

@melvin-bot melvin-bot bot changed the title [Personal Karma] Add NewDot toggle flow under Save The World [Payment due @ZhenjaHorbach] [Personal Karma] Add NewDot toggle flow under Save The World Apr 9, 2026
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 9, 2026

🎯 @ZhenjaHorbach, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/601130.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

@flodnv
Copy link
Copy Markdown
Contributor

flodnv commented Apr 9, 2026

Thank you!

@flodnv flodnv merged commit 643d371 into Expensify:main Apr 9, 2026
34 of 35 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 9, 2026

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

@fedirjh fedirjh deleted the personal-karma-new-dot branch April 9, 2026 17:46
@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/flodnv in version: 9.3.58-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

🤖 I reviewed the changes in this PR against the help site article at docs/articles/new-expensify/settings/Personal-Karma.md.

Changes are required. I've created a PR with the following updates:

  1. Toggle label: Updated from "Personal Karma" to Enable Personal Karma to match the exact UI text
  2. Disable flow: Added a separate section documenting the confirmation modal shown when disabling donations
  3. Payment card requirement: Documented that a billing card is required to enable Personal Karma, and that dismissing the payment card prompt reverts the toggle
  4. Billing card display: Documented that card details are shown below the toggle when enabled

Help site PR: #87571

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.

7 participants