Skip to content

feat: Gather KYB documents when verification fails for USD BA's#76033

Open
MrMuzyk wants to merge 46 commits into
Expensify:mainfrom
callstack-internal:feat/75707-usd-flow-kyb-files
Open

feat: Gather KYB documents when verification fails for USD BA's#76033
MrMuzyk wants to merge 46 commits into
Expensify:mainfrom
callstack-internal:feat/75707-usd-flow-kyb-files

Conversation

@MrMuzyk
Copy link
Copy Markdown
Contributor

@MrMuzyk MrMuzyk commented Nov 25, 2025

Explanation of Change

  • Added a new step to USD VBBA flow that is conditionally showed if user failed automated verification

Fixed Issues

$ #75707
PROPOSAL:

Tests

Same as QA steps

  • Verify that no errors appear in the JS console

Testing this requires to have an account that was manually set to a certain state, ie: #75707 (comment)

We will make sure that current functionality works without any issues, ship the new step and look out for regressions - https://expensify.slack.com/archives/C01GTK53T8Q/p1778070528787499?thread_ts=1763989665.580719&cid=C01GTK53T8Q

Offline tests

QA Steps

Verify you can connect USD bank account to USD workspace without any issue

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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-native.mp4
Android: mWeb Chrome
android.mweb.mp4
iOS: Native
ios-native.mp4
iOS: mWeb Safari
ios.web.mp4
MacOS: Chrome / Safari
web.mp4

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Nov 25, 2025

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

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

@codecov
Copy link
Copy Markdown

codecov Bot commented Nov 25, 2025

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 92.30% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
.../ReimbursementAccount/ReimbursementAccountPage.tsx 0.00% <ø> (ø)
...mentAccount/USD/USDVerifiedBankAccountFlowPage.tsx 0.00% <ø> (ø)
src/types/form/ReimbursementAccountForm.ts 100.00% <ø> (ø)
src/libs/actions/BankAccounts.ts 9.96% <0.00%> (-0.08%) ⬇️
...unt/USD/utils/isUserAddressVerificationRequired.ts 0.00% <0.00%> (ø)
...Account/USD/utils/isUserDOBVerificationRequired.ts 0.00% <0.00%> (ø)
...es/ReimbursementAccount/USD/KYBDocuments/index.tsx 0.00% <0.00%> (ø)
... and 30 files with indirect coverage changes

@MrMuzyk MrMuzyk requested review from a team as code owners May 8, 2026 11:55
@melvin-bot melvin-bot Bot requested review from a team, gijoe0295 and trjExpensify and removed request for a team May 8, 2026 11:55
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 8, 2026

@gijoe0295 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 JmillsExpensify and removed request for a team May 8, 2026 11:55
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

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: ec512c7955

ℹ️ 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/ReimbursementAccount/USD/KYBDocuments/index.tsx Outdated
);

const defaultValues = {
companyTaxID: reimbursementAccountDraft?.companyTaxID ?? [],
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Avoid reusing companyTaxID form key for KYB file uploads

This uses the same key as the business Tax ID text field (companyTaxID) but treats it as FileObject[] on this page. When a draft contains a prior Tax ID string (e.g., from editing), uploadedFiles.companyTaxID is initialized with that string and later spread/serialized as files, which can send invalid payload data (first character of the string) instead of an uploaded file. Use a distinct upload field key and map it explicitly to the API parameter to avoid cross-step type collisions.

Useful? React with 👍 / 👎.

@MrMuzyk
Copy link
Copy Markdown
Contributor Author

MrMuzyk commented May 8, 2026

Requested confirmation of translations

@trjExpensify
Copy link
Copy Markdown
Contributor

I think @joekaufmanexpensify is best suited for the product review of this one. Looks okay to me though!

@trjExpensify trjExpensify requested review from joekaufmanexpensify and removed request for JmillsExpensify and trjExpensify May 11, 2026 12:51
@joekaufmanexpensify
Copy link
Copy Markdown
Contributor

Nice, I'll take a look!

Copy link
Copy Markdown
Contributor

@gijoe0295 gijoe0295 left a comment

Choose a reason for hiding this comment

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

Haven't been able to test this because site is down

Comment thread src/languages/en.ts Outdated
userAddressVerificationDescription: dedent(`
Please upload one of the following files:
• Voter Registration Card
• Drivers License
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.

Suggested change
Drivers License
Driver's License

Comment thread src/types/onyx/ReimbursementAccount.ts Outdated
/** Statuses of additional checks hinting at missing documents user still needs to upload */
verifications?: {
/** points towards one of external providers */
externalApiResponse?: {
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.

Mismatch with backend screenshot here #75707 (comment)

Suggested change
externalApiResponse?: {
externalApiResponses?: {

}>
| undefined,
): boolean {
return status !== 'pass' && !!CONST.BANK_ACCOUNT.KYB_REQUESTOR_IDENTITY_ERROR.DOB.find((error) => qualifiers?.map((qualifier) => qualifier.key).includes(error));
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.

Please create a constant for 'pass' in CONST/index.ts.

Also why don't we check exact match === here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

We agreed that anything else than 'pass' status is enough to require a document from user

[CONST.BANK_ACCOUNT.STEP.COMPANY]: CONST.BANK_ACCOUNT.PAGE_NAMES.COMPANY,
[CONST.BANK_ACCOUNT.STEP.BENEFICIAL_OWNERS]: CONST.BANK_ACCOUNT.PAGE_NAMES.BENEFICIAL_OWNERS,
[CONST.BANK_ACCOUNT.STEP.ACH_CONTRACT]: CONST.BANK_ACCOUNT.PAGE_NAMES.ACH_CONTRACT,
[CONST.BANK_ACCOUNT.STEP.KYB_DOCS]: CONST.BANK_ACCOUNT.PAGE_NAMES.KYB_DOCS,
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 can't see we navigate to this step any where in App. Is it controlled by the backend?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

const [betas] = useOnyx(ONYXKEYS.BETAS);
const [isSelfTourViewed] = useOnyx(ONYXKEYS.NVP_ONBOARDING, {selector: hasSeenTourSelector});
const {accountID: currentUserAccountID} = useCurrentUserPersonalDetails();
const reimbursementAccountData = reimbursementAccount?.achData?.verifications?.externalApiResponse;
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.

Suggested change
const reimbursementAccountData = reimbursementAccount?.achData?.verifications?.externalApiResponse;
const reimbursementAccountVerificationData = reimbursementAccount?.achData?.verifications?.externalApiResponse;

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.

Can we move these functions to BankAccountUtils? I believe there could be more similar ones in the future.

const validate = (values: FormOnyxValues<typeof ONYXKEYS.FORMS.REIMBURSEMENT_ACCOUNT_FORM>): FormInputErrors<typeof ONYXKEYS.FORMS.REIMBURSEMENT_ACCOUNT_FORM> => {
const errors: FormInputErrors<typeof ONYXKEYS.FORMS.REIMBURSEMENT_ACCOUNT_FORM> = {};

for (const document of DOCUMENTS_CONFIG.filter((documentItem) => documentItem.required)) {
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.

Suggested change
for (const document of DOCUMENTS_CONFIG.filter((documentItem) => documentItem.required)) {
for (const document of requiredDocuments) {

@joekaufmanexpensify
Copy link
Copy Markdown
Contributor

This is just for Tincheck/LexisNexis/IDology, yeah ? I see the mocks in the GH issue mention GIACT, but then there is no mention of that in the detailed description.

@MrMuzyk
Copy link
Copy Markdown
Contributor Author

MrMuzyk commented May 13, 2026

Hey, the PR that this was held on was reverted so we need to wait a bit here before moving forward - Im currently fixing the issues that caused the revert - after that I'll get back to it.

This is just for Tincheck/LexisNexis/IDology, yeah ? I see the mocks in the GH issue mention GIACT, but then there is no mention of that in the detailed description.

Maybe @madmax330 can answer that - I was just told the fields to look out for 😅 If I remember correctly GIACT error is appearing in response already but we're not acting on the error in any way.

@MrMuzyk
Copy link
Copy Markdown
Contributor Author

MrMuzyk commented May 18, 2026

@gijoe0295

I've applied or responded to all of the comments, thank you. The PR that its is being held on right now is still in review. Hopefully we will be able to proceed here soon.

Let me know if you have any more comments regarding the code itself here. This was developed over spans of many months as various BE adjustments were needed. This thread might be helpful for you to get whole context

@MrMuzyk
Copy link
Copy Markdown
Contributor Author

MrMuzyk commented May 25, 2026

The PR its held on is still being tested atm -> #90302 (comment)

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