Skip to content

[Payment due @ZhenjaHorbach] [NoQA][Wise][Release 1] UI - Create Intro Screen - #104334

Merged
grgia merged 10 commits into
Expensify:mainfrom
software-mansion-labs:wise-global-reimbursements-intro-page
Oct 19, 2026
Merged

grgia merged 10 commits into
Expensify:mainfrom
software-mansion-labs:wise-global-reimbursements-intro-page

Conversation

@WojtekBoman

@WojtekBoman WojtekBoman commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

cc: @ZhenjaHorbach

Explanation of Change

Adds a beta-gated Wise global reimbursements intro page at settings/wallet/:bankAccountID/global-reimbursements. Shown only for open USD business bank accounts (new isEligibleForWiseGlobalReimbursements helper, unit tested), otherwise not-found. "Not now" returns to Wallet; "Get started" is a TODO until the next onboarding step exists. Wallet entry point comes in a follow-up PR.

Fixed Issues

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

Tests

  1. Enable the wiseReimbursements beta for your account

  2. Have an open USD business bank account in Account > Wallet and note its bankAccountID

  3. Navigate to /settings/wallet/<bankAccountID>/global-reimbursements

  4. Verify that the intro page shows the "Enable global reimbursements" header, the Earth with coins illustration, the "Set up global reimbursements?" heading, the "Pay members worldwide in their local currency." subtitle, and two buttons: "Not now" and "Get started"

  5. Tap "Not now"

  6. Verify that you land back on Account > Wallet

  7. Open the page again and tap the back button in the header

  8. Verify that you land back on Account > Wallet

  9. With the beta enabled, navigate to /settings/wallet/<bankAccountID>/global-reimbursements using the ID of a personal, non-USD, or not yet open bank account, or a non-existent ID

  10. Verify that the not-found page is shown

  11. Disable the wiseReimbursements beta and open the URL for the eligible account from the first test

  12. Verify that the page closes and you are returned to Wallet

  • Verify that no errors appear in the JS console

Offline tests

N/A - the page only reads bank account data already in Onyx and makes no API calls.

QA Steps

Same as tests

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 Simulator Screenshot - iPhone 17 Pro - 2026-10-19 at 11 21 23
iOS: mWeb Safari
MacOS: Chrome / Safari Screenshot 2026-10-19 at 10 30 55 Screenshot 2026-10-19 at 10 33 56

@melvin-bot

melvin-bot Bot commented Oct 19, 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 bun ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx bun ./scripts/generateTranslations.ts --compare-ref main

@WojtekBoman
WojtekBoman force-pushed the wise-global-reimbursements-intro-page branch from 6bc3f30 to e0b0f30 Compare October 19, 2026 09:13
@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 5dd7a081..c6b2a1b5 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -2828,6 +2828,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'Dieses Konto erfordert Ihre Aufmerksamkeit',
             unlock: 'Entsperren',
         },
+        wiseGlobalReimbursementsIntro: {title: 'Globale Rückerstattungen einrichten?', subtitle: 'Zahlen Sie Mitglieder weltweit in ihrer lokalen Währung.', getStarted: "Los geht's"},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `Karte zu ${walletName} hinzufügen`,
diff --git a/src/languages/el.ts b/src/languages/el.ts
index 3a0a2f2c..e774a8df 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -2884,6 +2884,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'Αυτός ο λογαριασμός χρειάζεται προσοχή',
             unlock: 'Ξεκλείδωμα',
         },
+        wiseGlobalReimbursementsIntro: {title: 'Να ρυθμιστούν οι παγκόσμιες αποζημιώσεις;', subtitle: 'Πληρώστε μέλη παγκοσμίως στο τοπικό τους νόμισμα.', getStarted: 'Ξεκινήστε'},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `Προσθήκη κάρτας στο ${walletName}`,
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 1255ad65..c58e926a 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -2738,6 +2738,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'Esta cuenta requiere atención',
             unlock: 'Desbloquear',
         },
+        wiseGlobalReimbursementsIntro: {title: '¿Configurar reembolsos globales?', subtitle: 'Paga a miembros de todo el mundo en su moneda local.', getStarted: 'Empieza'},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `Añadir tarjeta a ${walletName}`,
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index c629e2bd..3808f762 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -2833,6 +2833,11 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'Ce compte nécessite une attention particulière',
             unlock: 'Déverrouiller',
         },
+        wiseGlobalReimbursementsIntro: {
+            title: 'Configurer les remboursements globaux ?',
+            subtitle: 'Payez des membres partout dans le monde dans leur devise locale.',
+            getStarted: 'Commencer',
+        },
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `Ajouter la carte à ${walletName}`,
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 9db5fb5a..dcaa0424 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -2817,6 +2817,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'Questo conto richiede attenzione',
             unlock: 'Sblocca',
         },
+        wiseGlobalReimbursementsIntro: {title: 'Configurare i rimborsi globali?', subtitle: 'Paga i membri in tutto il mondo nella loro valuta locale.', getStarted: 'Inizia'},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `Aggiungi carta a ${walletName}`,
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index d412979f..a628acf7 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -2796,6 +2796,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'このアカウントには対応が必要です',
             unlock: 'ロック解除',
         },
+        wiseGlobalReimbursementsIntro: {title: 'グローバル払い戻しを設定しますか?', subtitle: '世界中のメンバーに現地通貨で支払えます。', getStarted: '使い始める'},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `${walletName} にカードを追加`,
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 60718020..eca1e5ed 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -2821,6 +2821,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'Deze account vereist aandacht',
             unlock: 'Ontgrendelen',
         },
+        wiseGlobalReimbursementsIntro: {title: 'Wereldwijde terugbetalingen instellen?', subtitle: 'Betaal leden wereldwijd in hun eigen lokale valuta.', getStarted: 'Aan de slag'},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `Kaart toevoegen aan ${walletName}`,
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 9792f3bf..dbe07ea4 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -2855,6 +2855,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'To konto wymaga uwagi',
             unlock: 'Odblokuj',
         },
+        wiseGlobalReimbursementsIntro: {title: 'Skonfigurować globalne zwroty kosztów?', subtitle: 'Płać członkom na całym świecie w ich lokalnej walucie.', getStarted: 'Zacznij'},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `Dodaj kartę do ${walletName}`,
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ca2cb4c9..b0a66637 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -2812,6 +2812,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: 'Esta conta precisa de atenção',
             unlock: 'Desbloquear',
         },
+        wiseGlobalReimbursementsIntro: {title: 'Configurar reembolsos globais?', subtitle: 'Pague membros no mundo todo na moeda local deles.', getStarted: 'Começar'},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `Adicionar cartão à ${walletName}`,
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 44a092b9..b175355b 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -2722,6 +2722,7 @@ const translations: TranslationDeepObject<typeof en> = {
             accountRequiresAttention: '此账户需要处理',
             unlock: '解锁',
         },
+        wiseGlobalReimbursementsIntro: {title: '设置全球报销?', subtitle: '按当地货币向全球成员付款。', getStarted: '开始使用'},
     },
     addCardToDigitalWallet: {
         title: ({walletName}: {walletName: string}) => `将卡添加到 ${walletName}`,

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@WojtekBoman
WojtekBoman force-pushed the wise-global-reimbursements-intro-page branch from e0b0f30 to 8484c7c Compare October 19, 2026 09:39
@codecov

codecov Bot commented Oct 19, 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/SCREENS.ts 100.00% <ø> (ø)
src/components/ConfirmationPage.tsx 93.87% <100.00%> (+0.12%) ⬆️
src/components/Icon/chunks/illustrations.chunk.ts 0.00% <ø> (ø)
src/libs/BankAccountUtils.ts 94.54% <100.00%> (+0.31%) ⬆️
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 62.50% <ø> (ø)
src/styles/variables.ts 100.00% <ø> (ø)
src/ROUTES.ts 32.57% <0.00%> (-0.03%) ⬇️
...gation/AppNavigator/ModalStackNavigators/index.tsx 7.48% <0.00%> (-0.01%) ⬇️
...tings/Wallet/WiseGlobalReimbursementsIntroPage.tsx 0.00% <0.00%> (ø)
... and 11 files with indirect coverage changes

@WojtekBoman
WojtekBoman force-pushed the wise-global-reimbursements-intro-page branch from 8484c7c to 0cbe359 Compare October 19, 2026 09:44
@WojtekBoman

Copy link
Copy Markdown
Contributor Author

@codex review

@WojtekBoman

Copy link
Copy Markdown
Contributor Author

@MelvinBot review this

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 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-19T11:33:41.032810Z 3e5ef16 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.

@WojtekBoman WojtekBoman changed the title feat: add Wise global reimbursements intro page [NoQA][Wise][Release 1] UI - Create Intro Screen Oct 19, 2026
@MelvinBot

Copy link
Copy Markdown
Contributor

The code looks good overall. I found one mismatch to fix before merge and two small nits.

1. Beta-off behavior doesn't match the test steps. With the beta off, the page closes and returns to Wallet (WiseGlobalReimbursementsIntroPage.tsx:46-55). The PR description and test steps 3–4 say users should see the not-found page instead. QA will fail one of them. Pick one behavior and update the other. Closing the page matches the code comment, so updating the test steps is probably simplest.

2. Nits

  • The page renders null while betas or the bank account list load, so the right-hand panel stays blank. Other pages usually show FullScreenLoadingIndicator here.
  • wiseGlobalReimbursementsIntroIllustrationSize sits in the middle of the productMarketingWindow* group (variables.ts:379). Move it outside that group.
What I checked and found fine
  • The route, screen, linking config, SETTINGS_TO_RHP entry, and param types are all wired up.
  • isEligibleForWiseGlobalReimbursements handles undefined safely. Its tests cover type, currency, missing currency, and each non-OPEN state. It repeats the USD + business + OPEN part of shouldShowEnableGlobalReimbursementsButton (WalletPage/index.tsx:472-476). The follow-up Wallet entry-point PR could reuse the helper there.
  • A non-numeric bankAccountID becomes NaN, finds no account, and shows not-found as expected.
  • The translations for all 11 locales are present and look correct.
  • The no-op "Get started" button is fine behind the beta, since it's marked TODO.

view run

@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: 0cbe359aa4

ℹ️ 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/pages/settings/Wallet/WiseGlobalReimbursementsIntroPage.tsx Outdated
@WojtekBoman
WojtekBoman marked this pull request as ready for review October 19, 2026 11:18
@WojtekBoman
WojtekBoman requested review from a team as code owners October 19, 2026 11:18
@melvin-bot
melvin-bot Bot requested review from ZhenjaHorbach and removed request for a team October 19, 2026 11:18
@melvin-bot

melvin-bot Bot commented Oct 19, 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]

@melvin-bot
melvin-bot Bot requested review from joekaufmanexpensify and removed request for a team October 19, 2026 11:18
Comment thread src/libs/BankAccountUtils.ts Outdated
Comment thread src/pages/settings/Wallet/WiseGlobalReimbursementsIntroPage.tsx Outdated
Comment thread src/pages/settings/Wallet/WiseGlobalReimbursementsIntroPage.tsx Outdated

@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: 3e5ef1620a

ℹ️ 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/pages/settings/Wallet/WiseGlobalReimbursementsIntroPage.tsx Outdated
Comment thread src/pages/settings/Wallet/WiseGlobalReimbursementsIntroPage.tsx Outdated
@github-actions

Copy link
Copy Markdown
Contributor

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

function WiseGlobalReimbursementsIntroPage({route}: WiseGlobalReimbursementsIntroPageProps) {
const bankAccountID = Number(route.params.bankAccountID);
const [bankAccountList, bankAccountListMetadata] = useOnyx(ONYXKEYS.BANK_ACCOUNT_LIST);
const [isLoadingPaymentMethods] = useOnyx(ONYXKEYS.IS_LOADING_PAYMENT_METHODS);

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.

NAB. can we default this to true like WalletPage? on a cold deep link the page paints not-found for a frame before the fetch starts

Suggested change
const [isLoadingPaymentMethods] = useOnyx(ONYXKEYS.IS_LOADING_PAYMENT_METHODS);
const [isLoadingPaymentMethods = true] = useOnyx(ONYXKEYS.IS_LOADING_PAYMENT_METHODS);

@grgia

grgia commented Oct 19, 2026

Copy link
Copy Markdown
Contributor
image image

I have the beta & open account but still see not here page following steps

@grgia

grgia commented Oct 19, 2026

Copy link
Copy Markdown
Contributor
image WOOP

@grgia

grgia commented Oct 19, 2026

Copy link
Copy Markdown
Contributor
Screen.Recording.2026-10-19.at.16.01.39.mov

@WojtekBoman the old button still opens corpay flow on my account with beta enabled, could we tighten the existing entry point for our beta? I'm fine to leave as is in this PR since it just adds a way to test the page, but I want to make sure that theses entry points are clearly cut with the beta.

Other than that, looks great!

@WojtekBoman

Copy link
Copy Markdown
Contributor Author

Screen.Recording.2026-10-19.at.16.01.39.mov
@WojtekBoman the old button still opens corpay flow on my account with beta enabled, could we tighten the existing entry point for our beta? I'm fine to leave as is in this PR since it just adds a way to test the page, but I want to make sure that theses entry points are clearly cut with the beta.

Other than that, looks great!

I'd like to handle it in https://github.com/Expensify/Expensify/issues/692498, is it ok for you? In this PR it should be available only via deeplink as this issue is only for adding the Intro screen

@ZhenjaHorbach

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-19.at.14.18.21.mov
Android: mWeb Chrome
Screen.Recording.2026-10-19.at.14.18.21.mov
iOS: HybridApp
Screen.Recording.2026-10-19.at.14.13.51.mov
iOS: mWeb Safari
Screen.Recording.2026-10-19.at.14.09.18.mov
MacOS: Chrome / Safari
Screen.Recording.2026-10-19.at.14.06.19.mov

@melvin-bot
melvin-bot Bot requested review from danieldoglas and grgia October 19, 2026 15:24
@melvin-bot melvin-bot Bot changed the title [NoQA][Wise][Release 1] UI - Create Intro Screen [Payment due @ZhenjaHorbach] [NoQA][Wise][Release 1] UI - Create Intro Screen Oct 19, 2026
@melvin-bot

melvin-bot Bot commented Oct 19, 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/692492.

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.

grgia
grgia previously approved these changes Oct 19, 2026

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

Code wise 👍

Note: We plan to do design QA when the entire flow is ready

# Conflicts:
#	src/libs/Navigation/types.ts
@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Intro screen LGTM and matches what I would expect 👍

image

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

NAB, is there a reason why we went with the longer Enable Global Reimbursements in the header versus just Global Reimbursements in the design doc?

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

If we want to change that, we can just do it in the next PR.

@grgia
grgia merged commit abff087 into Expensify:main Oct 19, 2026
39 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.

@grgia

grgia commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

@joekaufmanexpensify we'll make that copy change in this PR #104366 (review)

@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.15-1 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update is needed: the new global reimbursements intro page only shows behind the wiseReimbursements beta, and the PR adds no Wallet entry point to it, so most users can't see it yet.


view run

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