Repository navigation
Closed
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionAuto-added when associated PR is deployed to productionDailyKSv2KSv2ExternalAdded to denote the issue can be worked on by a contributorAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.Something to build that is a new item.
Description
Coming from here, we need to add support for manual US personal bank accounts in NewDot. We support both Plaid and manual US personal bank accounts in OldDot. We support Plaid and manual for US business bank accounts in NewDot, but only Plaid for US personal bank accounts in NewDot now. We also need to begin collecting name, address, and phone number associated with the bank account in situations where it's not already on file. Final mocks:
Updated Plaid US personal bank account flow
New manual US personal bank account flow
Notes on changes
- We'll add the "Streamline payments" page to the personal bank account flow when you select United States in the country selector. This is an existing page we use with business bank accounts. We'll change the copy on it to fit personal bank accounts.
- Selecting "Login to your bank" will open the existing Plaid flow.
- Selecting "Connect manually" will open a new page to collect account and routing for a personal bank account. This is the same as the page where we collect these for a manually connected business bank account. Some details:
- I believe we do a backend verification of the account and routing submitted here in Expensify Classic. We should do the same here.
- Both fields will be required.
- After the new "What are your bank account details?" page in the manual flow OR the existing "Choose your bank account" page in the Plaid flow, we will ask for name, address, and phone number because we need to collect them to process certain payments. We already do this in Expensify Classic. Some details:
- This applies to both the Plaid and manual flows.
- These will be our standard name, address, and phone number components. All will be required
- We'll fill Profile > Private with the name, address, phone number collected here, similar to how we do with other forms in the product.
- We'll also store these details in the same place we do as the name, address, phone number collected when setting up a US personal bank account in Expensify Classic.
- The user will then land on our standard confirmation page. Proceeding on the confirmation page will add the bank account and land the user on the existing success page.
- If we already have the user's name, address, or phone number from Profile > Private on file, we'll skip the page(s) for whichever we already have, since the user can still edit them on the confirmation page, should they so choose.
- If they edit their name, address, or phone number that's already on file in this flow, we'll update them in Profile > Private with the new details.
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021986159927248666358
- Upwork Job ID: 1986159927248666358
- Last Price Increase: 2025-11-05
Issue Owner
Current Issue Owner: @joekaufmanexpensifyMetadata
Metadata
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionAuto-added when associated PR is deployed to productionDailyKSv2KSv2ExternalAdded to denote the issue can be worked on by a contributorAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.Something to build that is a new item.
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Oct 28, 2025
Current assignee @joekaufmanexpensify is eligible for the NewFeature assigner, not assigning anyone new.
melvin-bot commentedon Oct 28, 2025
melvin-bot commentedon Oct 28, 2025
Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (
NewFeature)joekaufmanexpensify commentedon Oct 28, 2025
Marked as
planningwhile we put some mocks together. Interested in your thoughts @dubielzyk-expensifydubielzyk-expensify commentedon Oct 29, 2025
Thanks Joe! I'll try and get some mocks together tomorrow 👍
joekaufmanexpensify commentedon Oct 29, 2025
Thanks!
dubielzyk-expensify commentedon Oct 30, 2025
Didn't get to it today, but will try again tomorrow 👍
dubielzyk-expensify commentedon Oct 30, 2025
I found time in the evening under the couch. However, I don't understand much from the description, but I put together a few screens that maybe you can start with and tag me in some comments of what you need?
Here's the Figma. If not, I'm online early tomorrow (your end of day) and can jump on to chat it out 👍 https://www.figma.com/design/vBXCQWjQExxcmZjFxbME4C/Add-Bank-Account-Flows--VBA--Wallet--Onfido-?node-id=3849-504
61 remaining items
joekaufmanexpensify commentedon Jan 22, 2026
Last PR went out to prod yesterday!
joekaufmanexpensify commentedon Jan 26, 2026
Only remaining steps are regression tests and then payment to @suneox
suneox commentedon Jan 28, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: New feature
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Test: Manual US Personal Bank Account Flow
Test Case 1: WITHOUT existing personal info
Test Case 2: WITH existing personal info
Do we agree 👍 or 👎
joekaufmanexpensify commentedon Jan 29, 2026
Regression issue: https://github.com/Expensify/Expensify/issues/594222
joekaufmanexpensify commentedon Jan 29, 2026
Payment Summary
joekaufmanexpensify commentedon Jan 29, 2026
@suneox Please request payment at your earliest convenience. Closing as this is otherwise all set!
trjExpensify commentedon Feb 3, 2026
approved $250 for @suneox.
nyomanjyotisa commentedon Oct 29, 2026
#104165 affected the personal-bank setup flow added in #75179: both address lines were joined with a newline. Fixed by #104823, which sends them separately.