Skip to content

Allow UK cards to change PINs in App#86163

Draft
rafecolton wants to merge 12 commits intomainfrom
uk-change-pin
Draft

Allow UK cards to change PINs in App#86163
rafecolton wants to merge 12 commits intomainfrom
uk-change-pin

Conversation

@rafecolton
Copy link
Copy Markdown
Member

@rafecolton rafecolton commented Mar 24, 2026

Explanation of Change

Allow UK cards to change PIN in-app, show alternate success screen directing them to an ATM.

Fixed Issues

$ #86143
PROPOSAL: N/A

Tests

  1. Create a GBP and EUR policy, set up a bank account, get provisioned for Expensify cards.
  2. Issue yourself a physical card on each policy and activate them.
  3. Execute the change PIN flow for each card on their respective card details page.
  4. Observe the EUR card shows the PIN changed success screen with the 🎉 , and the GBP one shows the crystal ball and tells you to visit an ATM.
  • Verify that no errors appear in the JS console

Offline tests

N/A, online only

QA Steps

Same as tests. Assign to @joekaufmanexpensify for QA.

  • 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

Android: Native
android.mov
iOS: Native
Screen.Recording.2026-03-23.at.8.04.16.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-03-23.at.7.51.40.PM.mov

@rafecolton rafecolton self-assigned this Mar 24, 2026
@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 2dab5e5b..9c9b2275 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -2373,6 +2373,9 @@ ${amount} für ${merchant} – ${date}`,
         frozen: 'Gesperrt',
         youFroze: ({date}: {date: string}) => `Du hast diese Karte am ${date} gesperrt.`,
         frozenBy: ({person, date}: {person: string; date: string}) => `${person} hat diese Karte am ${date} gesperrt.`,
+        changePinATMTitle: 'Geldautomaten aufsuchen',
+        changePinATMDescription:
+            'Verwenden Sie Ihre Karte an einem beliebigen Geldautomaten, um Ihre PIN-Änderung abzuschließen. Dies ist in Ihrer Region erforderlich. <concierge-link>Wenden Sie sich an Concierge</concierge-link>, wenn Sie Fragen haben.',
     },
     workflowsPage: {
         workflowTitle: 'Ausgaben',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index f1200a74..9abdbb95 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -2380,6 +2380,9 @@ ${amount} pour ${merchant} - ${date}`,
         frozen: 'Gelée',
         youFroze: ({date}: {date: string}) => `Vous avez gelé cette carte le ${date}.`,
         frozenBy: ({person, date}: {person: string; date: string}) => `${person} a gelé cette carte le ${date}.`,
+        changePinATMTitle: 'Aller à un distributeur automatique',
+        changePinATMDescription:
+            "Utilisez votre carte à n'importe quel DAB pour terminer la modification de votre code PIN. Cela est requis dans votre région. <concierge-link>Contactez Concierge</concierge-link> si vous avez des questions.",
     },
     workflowsPage: {
         workflowTitle: 'Dépense',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 37cd7176..4efb35a7 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -2369,6 +2369,9 @@ ${amount} per ${merchant} - ${date}`,
         frozen: 'Bloccata',
         youFroze: ({date}: {date: string}) => `Hai bloccato questa carta il ${date}.`,
         frozenBy: ({person, date}: {person: string; date: string}) => `${person} ha bloccato questa carta il ${date}.`,
+        changePinATMTitle: 'Vai a un bancomat',
+        changePinATMDescription:
+            'Usa la tua carta a qualsiasi bancomat per completare il cambio del PIN. Questo è obbligatorio nella tua regione. <concierge-link>Contatta Concierge</concierge-link> se hai domande.',
     },
     workflowsPage: {
         workflowTitle: 'Spesa',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 8ea363a2..27a4c5eb 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -2344,6 +2344,9 @@ ${date} の ${merchant} への ${amount}`,
         frozen: '凍結中',
         youFroze: ({date}: {date: string}) => `${date}にこのカードを一時停止しました。`,
         frozenBy: ({person, date}: {person: string; date: string}) => `${person}が${date}にこのカードを一時停止しました。`,
+        changePinATMTitle: 'ATM を利用する',
+        changePinATMDescription:
+            'お住まいの地域では、暗証番号の変更を完了するには、任意のATMでカードをご利用いただく必要があります。ご不明な点がありましたら、<concierge-link>Concierge へお問い合わせください</concierge-link>。',
     },
     workflowsPage: {
         workflowTitle: '支出',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 4978d187..5af6b863 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -2367,6 +2367,9 @@ ${amount} voor ${merchant} - ${date}`,
         frozen: 'Geblokkeerd',
         youFroze: ({date}: {date: string}) => `Je hebt deze kaart op ${date} geblokkeerd.`,
         frozenBy: ({person, date}: {person: string; date: string}) => `${person} heeft deze kaart op ${date} geblokkeerd.`,
+        changePinATMTitle: 'Bezoek een geldautomaat',
+        changePinATMDescription:
+            'Gebruik je kaart bij een willekeurige geldautomaat om je pincodewijziging af te ronden. Dit is verplicht in jouw regio. <concierge-link>Neem contact op met Concierge</concierge-link> als je vragen hebt.',
     },
     workflowsPage: {
         workflowTitle: 'Uitgaven',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index a30d0aab..26261b59 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -2363,6 +2363,9 @@ ${amount} dla ${merchant} - ${date}`,
         frozen: 'Zamrożona',
         youFroze: ({date}: {date: string}) => `Zamroziłeś tę kartę ${date}.`,
         frozenBy: ({person, date}: {person: string; date: string}) => `${person} zamroził(a) tę kartę ${date}.`,
+        changePinATMTitle: 'Odwiedź bankomat',
+        changePinATMDescription:
+            'Użyj swojej karty w dowolnym bankomacie, aby dokończyć zmianę PIN-u. Jest to wymagane w twoim regionie. <concierge-link>Skontaktuj się z Concierge</concierge-link>, jeśli masz jakiekolwiek pytania.',
     },
     workflowsPage: {
         workflowTitle: 'Wydatki',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index b919fb7a..f6e2b5a2 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -2360,6 +2360,9 @@ ${amount} para ${merchant} - ${date}`,
         frozen: 'Congelado',
         youFroze: ({date}: {date: string}) => `Você bloqueou este cartão em ${date}.`,
         frozenBy: ({person, date}: {person: string; date: string}) => `${person} bloqueou este cartão em ${date}.`,
+        changePinATMTitle: 'Visitar um caixa eletrônico',
+        changePinATMDescription:
+            'Use seu cartão em qualquer caixa eletrônico para concluir a alteração do seu PIN. Isso é obrigatório na sua região. <concierge-link>Fale com a Concierge</concierge-link> se tiver alguma dúvida.',
     },
     workflowsPage: {
         workflowTitle: 'Gastos',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 048c91e5..08b9d2b9 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -2304,6 +2304,8 @@ ${amount},商户:${merchant} - 日期:${date}`,
         frozen: '已冻结',
         youFroze: ({date}: {date: string}) => `你于${date}冻结了此卡。`,
         frozenBy: ({person, date}: {person: string; date: string}) => `${person}于${date}冻结了此卡。`,
+        changePinATMTitle: '前往 ATM',
+        changePinATMDescription: '请在任意 ATM 使用您的银行卡完成 PIN 修改。这是您所在地区的必需步骤。如有任何疑问,请<concierge-link>联系 Concierge</concierge-link>。',
     },
     workflowsPage: {
         workflowTitle: '支出',

Note

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

View workflow run

@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 24, 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/ROUTES.ts 16.98% <ø> (+0.01%) ⬆️
src/SCREENS.ts 100.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 6.97% <ø> (+<0.01%) ⬆️
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 76.92% <ø> (ø)
.../pages/settings/Wallet/ExpensifyCardPage/index.tsx 69.91% <0.00%> (ø)
src/libs/Fullstory/common.ts 0.00% <0.00%> (ø)
...actorAuthentication/config/scenarios/ChangePIN.tsx 42.85% <20.00%> (-57.15%) ⬇️
... and 11 files with indirect coverage changes

@rafecolton rafecolton changed the title Uk change pin Allow UK cards to change PINs in App Mar 24, 2026
@rafecolton
Copy link
Copy Markdown
Member Author

Asked here for translation validations

@rafecolton rafecolton marked this pull request as ready for review March 24, 2026 03:38
@rafecolton rafecolton requested review from a team as code owners March 24, 2026 03:38
@melvin-bot melvin-bot Bot requested review from DylanDylann and trjExpensify and removed request for a team March 24, 2026 03:38
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Mar 24, 2026

@DylanDylann Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot removed the request for review from a team March 24, 2026 03:38
@rafecolton rafecolton requested review from chuckdries and joekaufmanexpensify and removed request for trjExpensify March 24, 2026 03:39
@DylanDylann
Copy link
Copy Markdown
Contributor

@codex review

title="cardPage.pinChanged"
subtitle="cardPage.pinChangedDescription"
/>
);
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.

I think we should pass isOfflinePINMarket in the payload and use payload.isOfflinePINMarket here.

@DylanDylann
Copy link
Copy Markdown
Contributor

DylanDylann commented Mar 24, 2026

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
    • MacOS: Desktop
  • 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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • 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 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)
  • 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
  • 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.
  • 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.
  • 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
iOS: HybridApp
Screen.Recording.2026-03-24.at.23.54.38.mov
MacOS: Chrome / Safari
Screen.Recording.2026-03-24.at.23.52.44.mov

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

ℹ️ 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".

@DylanDylann
Copy link
Copy Markdown
Contributor

The code changes look good, with just one minor concern. Since I can only test this flow using Jairo’s server, I’ll test and post evidence once it’s up.

@DylanDylann
Copy link
Copy Markdown
Contributor

Tested well!

@rafecolton
Copy link
Copy Markdown
Member Author

Decided to close this out after further discussion

@rafecolton rafecolton closed this Mar 24, 2026
@github-actions
Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@rafecolton rafecolton reopened this Apr 1, 2026
@rafecolton rafecolton marked this pull request as draft April 1, 2026 22:09
@rafecolton
Copy link
Copy Markdown
Member Author

Reopening and merging main, since we're using the ad-hoc in some testing

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 1, 2026

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 1, 2026

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #86163.

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ⏩ SKIPPED ⏩
The build for Android was skipped The build for iOS was skipped
Web 🕸️
https://86163.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 1, 2026

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

@github-actions
Copy link
Copy Markdown
Contributor

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

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.

4 participants