[Due for payment 2026-07-02] [$250] Update copy when inputting first and last name for a new business bank account

[clarajones-expensify]

Problem

When customers enter a first or last name that slightly differs from what is on their ID (usually a nickname like Josh instead of Joshua), their VBA will fail because we flag anything where the scanned ID info differs from what the customer typed in. This causes delays in the VBA review process, especially if the only fail is because the customer entered a nickname instead of their full name.

Solution

Update the copy during the bank account setup flow to inform customers that they should be inputting their legal name as it appears on their ID. For example, right beneath the What's your legal name? header, it could say: Please enter your full legal name as it appears on your ID.

Current UI:

Proposed UI:

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022060417292801121055
• Upwork Job ID: 2060417292801121055
• Last Price Increase: 2026-05-29
• Automatic offers:
• samranahm | Contributor | 111571388

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @dannymcclain (Design), see these Stack Overflow questions for more details.

[clarajones-expensify]

Hi @dannymcclain ! Before releasing this issue to be worked on, I wanted to get your opinion on adding a bit of copy as in the proposal above. Do you have feedback on how best to phrase this or design it so that customers will see it? Thank you thank you!

[samranahm]

Proposal

What is the root cause of that problem?

When customers enter a nickname (e.g. "Josh" instead of "Joshua") during the bank account setup flow, their VBA fails verification because the scanned ID info doesn't match what was typed. There is no hint text on the legal name screen telling users to enter their name exactly as it appears on their ID, so users don't know they should avoid nicknames.

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

FullNameStep.tsx

We need to add an optional formSubtitle prop to FullNameStep to follow the same pattern as the formDisclaimer prop on SingleFieldStep and the checkHelpLine text on ManualBankAccountDetailsStep and render it between the title and the first input using [styles.mb5, styles.textSupporting].

    <Text style={[styles.textHeadlineLineHeightXXL, formSubtitle ? styles.mb3 : styles.mb6]}>{formTitle}</Text>
    {!!formSubtitle && <Text style={[styles.mb5, styles.textSupporting]}>{formSubtitle}</Text>}

here

App/src/components/SubStepForms/FullNameStep.tsx

Lines 135 to 137 in 7e65978

	<Text style={[styles.textHeadlineLineHeightXXL, styles.mb6]}>{formTitle}</Text>
	<InputWrapper
	InputComponent={TextInput}

Add a legalNameSubtitle key to personalInfoStep in all locals

legalNameSubtitle: 'Please enter your full legal name as it appears on your ID.'

Pass formSubtitle={translate('personalInfoStep.legalNameSubtitle')} to FullNameStep in FullName.tsx and other two bank account setup flows

• PersonalInfo/subSteps/FullName.tsx
• PersonalInfo/substeps/LegalNameStep.tsx
• Wallet/InternationalDepositAccount/PersonalInfo/substeps/LegalNameStep.tsx

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[samranahm]

@dannymcclain @clarajones-expensify What about following the same pattern we use on other steps.

[clarajones-expensify]

@samranahm i like that a lot, makes sense to follow the existing pattern!

now that im looking at this a little more holistically, do you think we could also update the copy on the "What's your address" section? we have a lot of customers still using PO boxes and maildrops, so i'd like to make this more clear. Perhaps something like:

This must be a physical address, not a PO box or maildrop.

@dannymcclain would love your input on that copy

[samranahm]

Yes, we should update this as well and we could also consider

A physical address is required. PO boxes and mail drops are not accepted.

cc: @jamesdeanexpensify for visibility.

[dannymcclain]

Yeah I'm on board with all of this. Design/implementation-wise I totally agree, let's do it the exact same way we do on all the other screens 👍

Copy-wise, I like what you have for name, and I dig @samranahm's suggestion for the address copy update as well, but will defer to you and @jamesdeanexpensify!

[clarajones-expensify]

great! it would also be good to add that address subheader to the company address form as well

[clarajones-expensify]

posted in the product channel to get feedback: https://expensify.slack.com/archives/C03U7DCU4/p1780072664762129

[clarajones-expensify]

got approval from james!

[clarajones-expensify]

@samranahm to summarize here, let's make the following updates:

• First and last name, subheader says: Please enter your full legal name as it appears on your ID.
• Company address, subheader says: A physical address is required. PO boxes and mail drops are not accepted.
• Personal address, subheader says: A physical address is required. PO boxes and mail drops are not accepted.

is there a way to add data validation so that if either of the address inputs contain PO Box or PMB, we provide an error and tell the customer that PO boxes and maildrops are not accepted?

(PMB) stands for private mail box, and it indicates a commerical mail drop