Skip to content

[Payment due @ZhenjaHorbach] [NoQA][Wise][Release 1] Business - UI - Entry Point Workspace - #104485

Merged
grgia merged 7 commits into
Expensify:mainfrom
software-mansion-labs:wise-global-reimbursements-workspace-entry-point
Oct 21, 2026
Merged

grgia merged 7 commits into
Expensify:mainfrom
software-mansion-labs:wise-global-reimbursements-workspace-entry-point

Conversation

@WojtekBoman

@WojtekBoman WojtekBoman commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Behind the wiseReimbursements beta, adds a dismissible "Pay people worldwide" banner to Workspace > Workflows > Payments for admins whose reimbursement bank account is eligible for Wise. Banner UI is shared with Wallet via WiseGlobalReimbursementsBanner. The intro page now opens via a global-reimbursements/:bankAccountID dynamic route from both entry points.

Fixed Issues

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

Tests

Test 1 - Workspace banner and intro page

  1. Sign in as a workspace admin with the wiseReimbursements beta enabled, on a workspace that reimburses via Expensify from a verified (OPEN) USD business bank account shared with you
  2. Navigate to Workspaces > the workspace > Workflows > Payments
  3. Verify that the "Pay people worldwide" banner shows below the Payments rows, with "Get started" and a close (X) button
  4. Click "Get started"
  5. Verify that the "Set up global reimbursements?" intro page opens in the RHP over Workflows, the URL ends with /global-reimbursements/<bankAccountID>, and the header says "Global reimbursements"
  6. Click "Not now"
  7. Verify that you are back on Workflows > Payments
  8. Click the X on the banner and reload the page
  9. Verify that the banner stays hidden

Test 2 - Wallet entry point and old deep link

  1. With the beta enabled and an eligible bank account, navigate to Account > Wallet
  2. Verify that the banner shows, "Get started" opens the intro page at settings/wallet/global-reimbursements/<bankAccountID>, and "Not now" returns to Wallet
  3. Open /settings/wallet/<bankAccountID>/global-reimbursements directly in the address bar
  4. Verify that it redirects to the new intro page URL and the page renders

Test 3 - Hidden when not eligible

  1. Verify that the Workspace banner is not shown when:
    • the wiseReimbursements beta is disabled
    • the user is not an admin of the workspace
    • Payments is set to track payments made elsewhere
    • the connected account is not USD, not a business account, or is pending deletion
    • the session is a supportal or copilot session
  • Verify that no errors appear in the JS console

Offline tests

  1. With the beta enabled and the Workspace banner visible, go offline
  2. Click the X on the banner
  3. Verify that the banner disappears immediately
  4. Go online and reload Workflows > Payments
  5. Verify that the banner stays hidden

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 verified any copy / text that was added to the app 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • 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)
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari Screenshot 2026-10-20 at 17 05 30
Screen.Recording.2026-10-20.at.17.05.42.mov

@codecov

codecov Bot commented Oct 20, 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.90% <ø> (ø)
src/ROUTES.ts 33.71% <100.00%> (+0.07%) ⬆️
src/SCREENS.ts 100.00% <ø> (ø)
src/libs/BankAccountUtils.ts 95.52% <100.00%> (+0.36%) ⬆️
src/libs/Navigation/linkingConfig/OldRoutes.ts 100.00% <ø> (ø)
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 62.50% <ø> (ø)
.../workspace/workflows/tabs/WorkflowsPaymentsTab.tsx 80.53% <100.00%> (+0.13%) ⬆️
src/types/onyx/DismissedProductTraining.ts 0.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 7.48% <0.00%> (ø)
... and 6 more
... and 7 files with indirect coverage changes

@WojtekBoman
WojtekBoman marked this pull request as ready for review October 20, 2026 15:20
@WojtekBoman
WojtekBoman requested review from a team as code owners October 20, 2026 15:20
@melvin-bot
melvin-bot Bot requested review from ZhenjaHorbach and removed request for a team October 20, 2026 15:20
@melvin-bot

melvin-bot Bot commented Oct 20, 2026

Copy link
Copy Markdown

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

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-20T15:40:18.652121Z 79b1c6b Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot
melvin-bot Bot requested review from joekaufmanexpensify and removed request for a team October 20, 2026 15:20
Comment thread src/libs/BankAccountUtils.ts Outdated
@github-actions

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.

@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: 79b1c6b225

ℹ️ 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/BankAccountUtils.ts Outdated
@joekaufmanexpensify

This comment has been minimized.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

BUG dismissing banner does not persist after signing out and back in

Do we need a fix similar to https://github.com/Expensify/Auth/pull/25678 for this too @grgia ?

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Otherwise working well!

@ZhenjaHorbach

ZhenjaHorbach commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

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 any copy / text that was added to the app 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • 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)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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-10-21.at.13.44.37.mov
Android: mWeb Chrome
Screen.Recording.2026-10-21.at.13.44.37.mov
iOS: HybridApp
Screen.Recording.2026-10-21.at.13.17.03.mov
iOS: mWeb Safari
Screen.Recording.2026-10-21.at.13.45.55.mov
MacOS: Chrome / Safari
Screen.Recording.2026-10-21.at.12.55.08.mov

@WojtekBoman

Copy link
Copy Markdown
Contributor Author

I've addressed this comment #104366 (comment) in this PR

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

Should we add a tooltip for close button?

Screen.Recording.2026-10-21.at.12.55.42.mov

@melvin-bot
melvin-bot Bot requested a review from grgia October 21, 2026 11:46
@melvin-bot melvin-bot Bot changed the title [NoQA][Wise][Release 1] Business - UI - Entry Point Workspace [Payment due @ZhenjaHorbach] [NoQA][Wise][Release 1] Business - UI - Entry Point Workspace Oct 21, 2026
@melvin-bot

melvin-bot Bot commented Oct 21, 2026

Copy link
Copy Markdown

🎯 @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/692501.

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.

Comment thread src/CONST/index.ts
CHANGE_POLICY_TRAINING_MODAL: 'changePolicyModal',
AGENTS_RULES_BANNER: 'agentsRulesBanner',
WISE_GLOBAL_REIMBURSEMENTS_WALLET_BANNER: 'wiseGlobalReimbursementsWalletBanner',
WISE_GLOBAL_REIMBURSEMENTS_WORKSPACE_BANNER: 'wiseGlobalReimbursementsWorkspaceBanner',

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.

lol sob this needs auth change too

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

NOTE: Auth PR pending for NVP - https://github.com/Expensify/Auth/pull/25722

@grgia
grgia merged commit 416ec1e into Expensify:main Oct 21, 2026
37 of 40 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 grgia 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/grgia in version: 9.5.16-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update is needed. The Wise global reimbursements banner and intro page in Workflows > Payments and Wallet only appear behind the wiseReimbursements beta, and the other changes (new route, BillingBanner tooltip prop) don't change anything users see.


view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/grgia in version: 9.5.18-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update is needed. The new "Pay people worldwide" banner and the Wise global reimbursements intro page are gated behind the wiseReimbursements beta. The only ungated change moves Enable global reimbursements higher in the bank account menu, and no help article describes that menu's order.


view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.5.18-1 🚀

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

Bundle Size Analysis (Sentry):

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.

6 participants