Skip to content

feat(card): prompt for personal details before virtual card reveal#91634

Merged
chuckdries merged 32 commits into
Expensify:mainfrom
DylanDylann:virtual-card-missing-details
Jul 2, 2026
Merged

feat(card): prompt for personal details before virtual card reveal#91634
chuckdries merged 32 commits into
Expensify:mainfrom
DylanDylann:virtual-card-missing-details

Conversation

@DylanDylann

@DylanDylann DylanDylann commented May 25, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #91461
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Test accounts required

  • Account A — US Expensify Card holder with a virtual Expensify Card assigned and no/incomplete personal details on file (no legal name / DOB / phone / any address sub-field missing).
  • Account B — UK/EU Expensify Card holder (ECUK) with a virtual Expensify Card assigned and no/incomplete personal details on file, with biometrics/passkeys enrolled.
  • Account C — US Expensify Card holder with a virtual Expensify Card assigned and complete personal details already on file (control / regression case).
  • Account D — a copilot/delegate connected to Account A.

1. Home time-sensitive task appears (missing details)

  1. Sign in as Account A
  2. Navigate to Home.
  3. Verify: an "Add personal details" time-sensitive card appears in the time-sensitive section, above the fold, with copy referencing the virtual Expensify Card.
  4. Tap the card.
  5. Verify: user is routed into the missing personal details flow (Name → DOB → Address → Phone → Confirmation).
  6. Complete the flow and verify that the App navigates to the card detail page

2. Wallet "Add details" row appears (missing details)

  1. As Account A, go to Settings → Wallet.
  2. Verify: an "Add details" action row is visible on the Expensify Card list item for the virtual card, with an info brick-road indicator on the Wallet tab icon.
  3. Tap into the virtual card details page.
  4. Verify: a Reveal details button is present with a masked card number above it.

3. Reveal-details flow starts personal-details prompt (US card)

  1. As Account A, tap Reveal details on the virtual card page.
  2. Verify: the missing personal details flow opens (Name step).
  3. Fill in Legal name → Next.
  4. Fill in DOB → Next.
  5. Fill in Address (street, city, state, zip, country) → Next.
  6. Fill in Phone number → Next.
  7. Verify: a Confirmation page appears summarizing all entered details.
  8. Tap Confirm.
  9. Verify: a magic-code prompt appears (US path).
  10. Enter the valid magic code and submit.
  11. Verify:
    • Card details (PAN, expiration, CVV) are revealed on the card page.
    • The user is not asked for a second magic code.
    • The home time-sensitive card disappears.
    • The Wallet "Add details" row disappears.
    • The Wallet brick-road indicator clears.

4. Reveal-details flow — SCA path (UK/EU card)

  1. Sign in as Account B.
  2. Repeat step 3 above (fill in personal-details form).
  3. On the Confirmation page, tap Confirm.
  4. Verify: the biometrics/passkey prompt appears (SCA), not a magic code.
  5. Complete the biometric/passkey challenge.
  6. Verify: card details are revealed on the card page and Home/Wallet indicators are cleared.

5. Reveal-details flow — no personal details needed (US)

  1. Sign in as Account C (personal details complete).
  2. Go to Settings → Wallet → virtual card.
  3. Verify: no home task appears, no "Add details" row on Wallet, no brick road.
  4. Tap Reveal details.
  5. Verify: user is taken directly to a magic-code prompt (no personal-details form shown).
  6. Enter the magic code.
  7. Verify: card details are revealed and there is no navigation regression (user stays on / lands back on the card page).

6. Reveal-details flow — no personal details needed (UK/EU)

  1. Sign in as an ECUK holder with details complete + biometrics/passkey enrolled.
  2. Go to Wallet → virtual card → tap Reveal details.
  3. Verify: a biometrics/passkey prompt appears (SCA), no personal-details form.
  4. Complete SCA.
  5. Verify: card details are revealed on the same page (no RHP close animation / no wallet-domain navigation flicker).

7. Reveal-details flow — incomplete address (edge case)

  1. Set up an account with legalFirstName, legalLastName, dob, phoneNumber populated but an incomplete address (e.g. addresses[0] exists but city is empty).
  2. Sign in and go to Wallet → virtual card.
  3. Verify: the "Add details" row is shown (partial-address must still trigger the flow).
  4. Tap Reveal details.
  5. Verify: the personal-details form opens on the Address step (or earliest incomplete field) rather than skipping straight to reveal.
  6. Complete the flow and confirm that reveal succeeds.

8. Delegate/copilot access is not prompted

  1. Connect as Account D (delegate) into Account A's account.
  2. Navigate to Home.
  3. Verify: the "Add personal details" time-sensitive card is not shown.
  4. Go to Settings → Wallet.
  5. Verify: no "Add details" row and no brick-road indicator for the missing-details flow on Wallet (the delegate can't complete the reveal without the original account's auth).

9. Home task clears after details filled from a different flow

  1. Sign in as a fresh account with a virtual Expensify Card and no personal details, and a physical card also assigned.
  2. Complete the physical-card personal-details flow (which also captures name / DOB / address / phone).
  3. Return to Home.
  4. Verify: the "Add personal details" home task for the virtual card is gone (was auto-cleared because details are now complete).
  5. Go to Wallet → virtual card → tap Reveal details.
  6. Verify: reveal goes straight to the auth ceremony, no personal-details form.
  • 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

EU/UK virtual card

Screen.Recording.2026-06-26.at.17.24.58.mov

US virtual card

Screen.Recording.2026-06-26.at.17.28.21.mov

Reuses the existing MissingPersonalDetails flow for the virtual-card
reveal entry point so users with incomplete details fill them in
(name/DOB/address/phone) before viewing the card. ECUK virtual cards
go through the SCA reveal scenario afterwards; US virtual cards go to
the magic-code reveal page. PIN collection is already excluded for
virtual cards by the existing selector. Adds a red dot on the wallet
row and a home-page time-sensitive task as additional entry points.

Implements Expensify#91461.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@DylanDylann
DylanDylann requested review from a team as code owners May 25, 2026 16:38
@melvin-bot

melvin-bot Bot commented May 25, 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

@melvin-bot
melvin-bot Bot requested review from JmillsExpensify and lakchote and removed request for a team May 25, 2026 16:38
@melvin-bot

melvin-bot Bot commented May 25, 2026

Copy link
Copy Markdown

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

@DylanDylann
DylanDylann marked this pull request as draft May 25, 2026 16:40
@codecov

codecov Bot commented May 25, 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 Δ
...ultifactorAuthentication/config/scenarios/index.ts 100.00% <ø> (ø)
...ultifactorAuthentication/config/scenarios/names.ts 100.00% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
...rc/libs/MultifactorAuthentication/shared/VALUES.ts 100.00% <ø> (ø)
...imeSensitiveSection/hooks/useTimeSensitiveCards.ts 100.00% <100.00%> (ø)
src/pages/settings/InitialSettingsPage.tsx 85.71% <100.00%> (+0.20%) ⬆️
src/selectors/Card.ts 89.18% <ø> (-0.56%) ⬇️
src/libs/actions/Card.ts 0.00% <0.00%> (ø)
src/pages/home/TimeSensitiveSection/index.tsx 74.68% <66.66%> (-0.65%) ⬇️
src/libs/CardUtils.ts 82.82% <77.77%> (+0.19%) ⬆️
... and 13 more
... and 297 files with indirect coverage changes

Replaces the 4-API fan-out (updatePersonalDetailsForVirtualCard
calling UPDATE_LEGAL_NAME / UPDATE_DATE_OF_BIRTH / UPDATE_PHONE_NUMBER
/ UPDATE_HOME_ADDRESS) with a single new WRITE_COMMAND modeled on
SetPersonalDetailsAndShipExpensifyCards. Cleaner backend contract and
keeps the submission atomic from the FE perspective.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@DylanDylann

Copy link
Copy Markdown
Contributor Author

@chuckdries Would you like to take over this PR?

@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 26d5ace68bc..6c6f6240ae0 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -958,6 +958,11 @@ const translations: TranslationDeepObject<typeof en> = {
                 workspaceSubtitle: ({policyName}: {policyName: string}) => policyName,
                 personalSubtitle: 'Geldbörse',
             },
+            addVirtualCardPersonalDetails: {
+                title: 'Fügen Sie Ihre persönlichen Daten hinzu',
+                subtitle: 'Fügen Sie Ihre Daten hinzu, um Ihre Expensify Karte anzusehen und zu verwenden.',
+                cta: 'Details hinzufügen',
+            },
         },
         announcements: 'Ankündigungen',
         discoverSection: {
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 511d7baf7f4..52e08e15596 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -888,11 +888,7 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: 'Proporciona una dirección para recibir tu Tarjeta Expensify.',
                 cta: 'Añade dirección',
             },
-            addVirtualCardPersonalDetails: {
-                title: 'Añade tus datos personales',
-                subtitle: 'Añade tus datos para ver y empezar a usar tu Tarjeta Expensify.',
-                cta: 'Añadir datos',
-            },
+            addVirtualCardPersonalDetails: {title: 'Añade tus datos personales', subtitle: 'Añade tus datos para ver y empezar a usar tu Tarjeta Expensify.', cta: 'Añade detalles'},
             addPaymentCard: {
                 title: 'Añade una tarjeta de pago para seguir usando Expensify',
                 subtitle: 'Cuenta > Suscripción',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 079293757c4..23252d0d36b 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -961,6 +961,11 @@ const translations: TranslationDeepObject<typeof en> = {
                 workspaceSubtitle: ({policyName}: {policyName: string}) => policyName,
                 personalSubtitle: 'Portefeuille',
             },
+            addVirtualCardPersonalDetails: {
+                title: 'Ajoutez vos informations personnelles',
+                subtitle: 'Ajoutez vos informations pour afficher et commencer à utiliser votre Carte Expensify.',
+                cta: 'Ajouter des détails',
+            },
         },
         announcements: 'Annonces',
         discoverSection: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 3feb94469cc..e5cb6ad3a59 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -959,6 +959,11 @@ const translations: TranslationDeepObject<typeof en> = {
                 workspaceSubtitle: ({policyName}: {policyName: string}) => policyName,
                 personalSubtitle: 'Portafoglio',
             },
+            addVirtualCardPersonalDetails: {
+                title: 'Aggiungi i tuoi dati personali',
+                subtitle: 'Aggiungi i tuoi dati per visualizzare e iniziare a usare la tua Carta Expensify.',
+                cta: 'Aggiungi dettagli',
+            },
         },
         announcements: 'Annunci',
         discoverSection: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 78c68061cdb..cde18967b15 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -942,6 +942,7 @@ const translations: TranslationDeepObject<typeof en> = {
                 workspaceSubtitle: ({policyName}: {policyName: string}) => policyName,
                 personalSubtitle: 'ウォレット',
             },
+            addVirtualCardPersonalDetails: {title: '個人情報を追加してください', subtitle: 'Expensify カードを表示して使い始めるには、詳細情報を入力してください。', cta: '詳細を追加'},
         },
         announcements: 'お知らせ',
         discoverSection: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 1a3fc48f906..eb89d8ba9ad 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -957,6 +957,11 @@ const translations: TranslationDeepObject<typeof en> = {
                 workspaceSubtitle: ({policyName}: {policyName: string}) => policyName,
                 personalSubtitle: 'Portemonnee',
             },
+            addVirtualCardPersonalDetails: {
+                title: 'Voeg je persoonlijke gegevens toe',
+                subtitle: 'Voeg je gegevens toe om je Expensify Kaart te bekijken en te gaan gebruiken.',
+                cta: 'Details toevoegen',
+            },
         },
         announcements: 'Aankondigingen',
         discoverSection: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 995aa727aeb..b265fd7409e 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -959,6 +959,7 @@ const translations: TranslationDeepObject<typeof en> = {
                 workspaceSubtitle: ({policyName}: {policyName: string}) => policyName,
                 personalSubtitle: 'Portfel',
             },
+            addVirtualCardPersonalDetails: {title: 'Dodaj swoje dane osobowe', subtitle: 'Dodaj swoje dane, aby wyświetlić i zacząć używać swojej Karty Expensify.', cta: 'Dodaj szczegóły'},
         },
         announcements: 'Ogłoszenia',
         discoverSection: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 6fa49367a32..0cfb8f18448 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -957,6 +957,11 @@ const translations: TranslationDeepObject<typeof en> = {
                 workspaceSubtitle: ({policyName}: {policyName: string}) => policyName,
                 personalSubtitle: 'Carteira',
             },
+            addVirtualCardPersonalDetails: {
+                title: 'Adicione seus dados pessoais',
+                subtitle: 'Adicione seus dados para visualizar e começar a usar seu Cartão Expensify.',
+                cta: 'Adicionar detalhes',
+            },
         },
         announcements: 'Comunicados',
         discoverSection: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 22ed75b0da0..00e60bf1f06 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -925,6 +925,7 @@ const translations: TranslationDeepObject<typeof en> = {
                 workspaceSubtitle: ({policyName}: {policyName: string}) => policyName,
                 personalSubtitle: '钱包',
             },
+            addVirtualCardPersonalDetails: {title: '添加您的个人信息', subtitle: '添加您的详细信息以查看并开始使用 Expensify 卡。', cta: '添加详细信息'},
         },
         announcements: '公告',
         discoverSection: {

Note

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

View workflow run

@DylanDylann
DylanDylann marked this pull request as ready for review May 26, 2026 14:40

@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: de5abedd4e

ℹ️ 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/MissingPersonalDetails/MissingPersonalDetailsContent.tsx Outdated
@DylanDylann
DylanDylann marked this pull request as draft May 26, 2026 17:34
@DylanDylann
DylanDylann marked this pull request as ready for review May 26, 2026 18:17
Comment thread src/pages/settings/Wallet/PaymentMethodList.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: 57adf876f9

ℹ️ 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/actions/PersonalDetails.ts Outdated
@rafecolton
rafecolton requested a review from chuckdries July 2, 2026 17:38
@chuckdries

chuckdries commented Jul 2, 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 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 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)
  • 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)
  • 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.
  • 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
android.UK.virtual.card.homepage.prompt.mp4
android.uk.wallet.page.no.prompt.mp4
iOS: HybridApp
ios.homepage.prompt.US.card.mp4
MacOS: Chrome / Safari
web.UK.virtual.card.wallet.page.prompt.mp4

@chuckdries
chuckdries merged commit f222dc4 into Expensify:main Jul 2, 2026
35 of 38 checks passed
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

OSBotify commented Jul 2, 2026

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

OSBotify commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/chuckdries in version: 9.4.27-1 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 I reviewed the changes in this PR against the help site files under docs/articles.

Docs changes are required. This PR adds a new step to the virtual Expensify Card reveal flow — cardholders with incomplete personal details are now prompted to add them (legal name, date of birth, address, phone number) before their card details can be revealed. The View your virtual card details section of Cardholder-Settings-and-Features.md previously described only the Reveal step and didn't mention this prompt.

Draft PR: #95294 — adds a note documenting the Add details prompt and how US (magic code) vs. UK/EU (biometrics/passkey) cardholders verify their identity to reveal the card.

Why no other articles were updated

The reveal flow for NewDot virtual cards is documented only in Cardholder-Settings-and-Features.md (new-expensify). The other Expensify Card articles cover setup, disputes, shipping/mailing address, spend rules, and 3D Secure — none of which describe the personal-details-before-reveal behavior this PR introduces. UI labels used in the docs update (Reveal, Add details) were verified against src/languages/en.ts.


@DylanDylann, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review.

@jponikarchuk

Copy link
Copy Markdown

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

@izarutskaya

Copy link
Copy Markdown

Hi @DylanDylann We can't verified this PR as we have only one account with non US bank account and when trying issue new virtual Expensify Card pop-up window appears about updating the currency to USD. Could you please check this internally? Thank you in advance

Account B — UK/EU Expensify Card holder (ECUK) with a virtual Expensify Card assigned and no/incomplete personal details on file, with biometrics/passkeys enrolled.

Recording.3855.mp4

@DylanDylann

DylanDylann commented Jul 6, 2026

Copy link
Copy Markdown
Contributor Author

@joekaufmanexpensify Could you help with QA on this PR?

@OSBotify

OSBotify commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.4.27-2 🚀

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

Bundle Size Analysis (Sentry):

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Yep! @izarutskaya my thinking is you were able to test everything besides test cases 4 and 6. Is that right? I'm proceeding as if that is the case right now, but please let me know if you need help testing any others.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Test cases 4 and 6 pass.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Only issue I ran into is I'm getting an error on the magic code when trying to update personal details from the profile page. We throw an error, but the code works. I'm unsure if it's related to this PR, though. Curious what others think?

2026-07-06_16-09-13.mp4

@chuckdries

Copy link
Copy Markdown
Contributor

Hmm, that seems too fast to be a backend response. Did you recently enter an incorrect code in a previous step? Maybe we're showing a stale error message that stuck around in Onyx?. CC @DylanDylann

@DylanDylann

Copy link
Copy Markdown
Contributor Author

It's working well on my side. In case we enter the wrong magic code, the error message is displayed at the bottom

Screenshot 2026-07-07 at 12 56 20

@joekaufmanexpensify Could you reset the cache and try again? I have the same thought as @chuckdries, this may be caused by some stale data

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Sounds good. I will retest.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

@trjExpensify also flagged an issue in Slack where he's being prompted to add his personal details to view his virtual card on the home page, even though his personal details are already on file.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

After signing out and back in I can't reproduce the magic code error anymore, so I think we're good there 👍

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.

9 participants