[WAITING ON CHECKLIST] [$250] Bank - Authorized payer is displayed as phone number@expensify.sms.

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: V9.2.90-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13177080/test-cases/48358512
Email or phone of affected tester (no customers): dreamnitethedragon+yydyd373@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Other

Action Performed:

Pre-condition
Invite a phone number user with admin role
Add a fully verified bank account VBA

1. Launch app
2. Go to workspace settings
3. Tap workflows
4. Tap Payer
5. Select phone number user

Expected Result:

Authorized payer must not be displayed as phone number@expensify.sms

Actual Result:

Authorized payer is displayed as phone number@expensify.sms.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022006877116217505002
• Upwork Job ID: 2006877116217505002
• Last Price Increase: 2026-01-01

Issue Owner

Current Issue Owner: @jliexpensify

[melvin-bot]

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[jliexpensify]

@jponikarchuk I'm a bit confused, where is this happening?

Authorized payer is displayed as phone number@expensify.sms.

Can you add a screenshot highlighting this?

[nyomanjyotisa]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Bank - Authorized payer is displayed as phone number@expensify.sms

What is the root cause of that problem?

The authorized payer display name is retrieved by directly accessing the displayName property from personal details instead of using the getDisplayNameOrDefault or formatPhoneNumber. For phone number users without display name, the backend sets displayName the same as login (e.g., "+1234567890@expensify.sms"), so directly accessing displayName returns the raw value with the SMS domain

App/src/pages/workspace/workflows/WorkspaceWorkflowsPage.tsx

Lines 106 to 109 in 66de3d6

	const displayNameForAuthorizedPayer = useMemo(
	() => getPersonalDetailByEmail(policy?.achAccount?.reimburser ?? '')?.displayName ?? policy?.achAccount?.reimburser,
	[policy?.achAccount?.reimburser],
	);

What changes do you think we should make in order to solve the problem?

We should use getDisplayNameOrDefault instead of directly accessing the displayName property

    const displayNameForAuthorizedPayer = useMemo(
        () => getDisplayNameOrDefault(getPersonalDetailByEmail(policy?.achAccount?.reimburser ?? ''), policy?.achAccount?.reimburser),
        [policy?.achAccount?.reimburser],
    );

App/src/pages/workspace/workflows/WorkspaceWorkflowsPage.tsx

Lines 106 to 109 in 66de3d6

	const displayNameForAuthorizedPayer = useMemo(
	() => getPersonalDetailByEmail(policy?.achAccount?.reimburser ?? '')?.displayName ?? policy?.achAccount?.reimburser,
	[policy?.achAccount?.reimburser],
	);

What alternative solutions did you explore? (Optional)

We could use formatPhoneNumber combined with getDisplayNameOrDefault (as done in WorkspaceWorkflowsPayerPage)

    const displayNameForAuthorizedPayer = useMemo(
        () => formatPhoneNumber(getDisplayNameOrDefault(getPersonalDetailByEmail(policy?.achAccount?.reimburser ?? ''), policy?.achAccount?.reimburser)),
        [policy?.achAccount?.reimburser, formatPhoneNumber],
    );

Or like this without getDisplayNameOrDefault

    const displayNameForAuthorizedPayer = useMemo(
        () => formatPhoneNumber(getPersonalDetailByEmail(policy?.achAccount?.reimburser ?? '')?.displayName ?? policy?.achAccount?.reimburser ?? ''),
        [formatPhoneNumber, policy?.achAccount?.reimburser],
    );

App/src/pages/workspace/workflows/WorkspaceWorkflowsPage.tsx

Lines 106 to 109 in 66de3d6

	const displayNameForAuthorizedPayer = useMemo(
	() => getPersonalDetailByEmail(policy?.achAccount?.reimburser ?? '')?.displayName ?? policy?.achAccount?.reimburser,
	[policy?.achAccount?.reimburser],
	);

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022006877116217505002

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov (External)

[yatin-italy]

Proposal

Please re-state the problem that we are trying to solve in this issue.

On the Workspace Workflows page, authorized payers with phone-number-based accounts were displayed using their internal identifier (e.g., +1234567890@expensify.sms) instead of a human-readable name or properly formatted phone number.

---

What is the root cause of that problem?

The page was deriving the display name using:

• createDisplayName directly with the reimburser and personal details

For phone-number-based users, this exposed the raw SMS-based identifier because the formatting was not applied at the presentation layer. Unlike other workflow pages, this page did not normalize the reimburser using getDisplayNameOrDefault and formatPhoneNumber.

---

What changes do you think we should make in order to solve the problem?

Solution: Refactor displayNameForAuthorizedPayer to normalize and format phone-number-based payers consistently.

Implementation Details:

• File: WorkspaceWorkflowsPage.tsx

• Changes Made:

  1. Destructured formatPhoneNumber from the useLocalize hook.
  2. Refactored displayNameForAuthorizedPayer useMemo to:
     • Use getPersonalDetailByEmail to fetch personal details
     • Use getDisplayNameOrDefault to compute a safe display name
     • Apply formatPhoneNumber to the result to ensure consistent formatting for phone numbers

Updated Code Snippet:

const { translate, localeCompare, formatPhoneNumber } = useLocalize();

const displayNameForAuthorizedPayer = useMemo(() => {
    const reimburser = policy?.achAccount?.reimburser ?? '';
    const personalDetail = getPersonalDetailByEmail(reimburser);
    const displayName = getDisplayNameOrDefault(personalDetail, reimburser);
    return formatPhoneNumber(displayName);
}, [policy?.achAccount?.reimburser, formatPhoneNumber]);

Result:

• Phone-number-based payers now appear with a properly formatted display name (e.g., +1 (234) 567-8900)
• SMS-based internal identifiers are no longer exposed
• Consistent with other workflow pages
• No impact on backend logic or authorization

---

What alternative solutions did you explore? (Optional)

1. Continue using createDisplayName without formatting

   • Does not fix SMS identifier exposure

2. Manually format SMS identifiers inline

   • Duplicates existing logic in getDisplayNameOrDefault
   • Harder to maintain

[cosmicvulpes]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.