[HOLD for payment 2023-12-28] [$500] Send money - Bank account option is not present in Pay with Expensify menu

[lanitochka17]

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: 1.4.5-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com
2. Go to 1:1 DM
3. Click + > Send money
4. Select USD currency and enter an amount > Click Next
5. Click Pay with Expensify

Expected Result:

Bank account option will be present in Pay with Expensify menu

Actual Result:

Bank account option is not present in Pay with Expensify menu

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6295100_1701288930404.bandicam_2023-11-30_03-10-17-567.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01782e16325ea5e0f2
• Upwork Job ID: 1729983421600763904
• Last Price Increase: 2023-11-29
• Automatic offers:
• aimane-chnaif | Reviewer | 27911758
• dukenv0307 | Contributor | 27911760

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

Triggered auto assignment to @trjExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

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

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

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

[dukenv0307]

Proposal

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

What is the root cause of that problem?

In SettlementButton in the send money flow, we don't pass in the iouReport, so based on this condition, it will not show the personal bank account.

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

In the send money flow, we need to pass the iouType to SettlementButton and subsequently to AddPaymentMethodMenu. If the iouType is CONST.IOU.TYPE.SEND, we can allow the personal bank account to show.

We can add that condition to here, or can extract to a canUsePersonalBankAccount variable (similar pattern to the existing canUseBusinessBankAccount variable)

What alternative solutions did you explore? (Optional)

Pass a boolean, or a iouReport with only the type field, which can be used to indicate it's a send money request in AddPaymentMethodMenu.

[trjExpensify]

Hm, @kevinksullivan @joekaufmanexpensify can you guys chime in on this one?

1. My personal workspace currency is USD
2. I don't have a wallet enabled
3. I send money in USD
4. I tap Pay with Expensify on the confirmation screen
5. I see a debit card option?

Why aren't I prompted here to go through the flow and enable the wallet?

CC: @mountiny as well maybs from Bottom Up!

[mountiny]

Bank account option will be present in Pay with Expensify menu

There should be no business bank account option when sending money 1:1, but there should be one for personal bank account

@dukenv0307 solution is right except we do not want the business bank account but personal one here, we only check for hte IOU report

App/src/components/AddPaymentMethodMenu.js

Lines 82 to 92 in a83a35d

	...(ReportUtils.isIOUReport(iouReport)
	? [
	{
	text: translate('common.personalBankAccount'),
	icon: Expensicons.Bank,
	onSelected: () => {
	onItemSelected(CONST.PAYMENT_METHODS.PERSONAL_BANK_ACCOUNT);
	},
	},
	]
	: []),

but at this point there is no IOU report created yet so the option is not added

[dukenv0307]

@dukenv0307 solution is right except we do not want the business bank account but personal one here, we only check for the IOU report

Thanks @mountiny for point out the right expectation here. Proposal updated to cover the case of personal bank account.

[aimane-chnaif]

Thanks everyone for the discussion.
@dukenv0307's proposal looks good to me.
🎀 👀 🎀 C+ reviewed

[melvin-bot]

Triggered auto assignment to @Li357, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[melvin-bot]

📣 @aimane-chnaif 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

[melvin-bot]

📣 @dukenv0307 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[joekaufmanexpensify]

Why aren't I prompted here to go through the flow and enable the wallet?

@trjExpensify If you add a debit card, are you prompted to then set up your wallet? I'd expect you would be. We just prompt to you to add payment method as the first step of the wallet enable flow.

[dukenv0307]

@aimane-chnaif The PR is ready for review

[trjExpensify]

@trjExpensify If you add a debit card, are you prompted to then set up your wallet?

I only have a UK debit card unfortunately, so I didn't attempt to go further through the flow at the time.

I'd expect you would be. We just prompt to you to add payment method as the first step of the wallet enable flow.

But why would we only show the option for Debit card and not connecting a bank account to enable the wallet? The screenshot from here is the first thing I see.

[joekaufmanexpensify]

But why would we only show the option for Debit card and not connecting a bank account to enable the wallet? The screenshot from #32228 (comment) is the first thing I see.

This I'm not sure of. I would expect that we'd show bank account in every scenario too.

[trjExpensify]

Cool, so that's being addressed in this issue hopefully. Pretty strange bug to slip through though!

[kevinksullivan]

Hmm sorry totally missed this, but yeah I'm not sure why you're only seeing debit card here. That ain't right.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.14-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Personal bank account option is not present in Pay with Expensify menu #32423

If no regressions arise, payment will be issued on 2023-12-28. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

For reference, here are some details about the assignees on this issue:

• @aimane-chnaif requires payment automatic offer (Reviewer)
• @dukenv0307 requires payment automatic offer (Contributor)

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@aimane-chnaif] The PR that introduced the bug has been identified. Link to the PR:
• [@aimane-chnaif] 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:
• [@aimane-chnaif] A discussion in #expensify-bugs 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:
• [@aimane-chnaif] Determine if we should create a regression test for this bug.
• [@aimane-chnaif] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[kevinksullivan]

Hi @aimane-chnaif please complete the checklist above when you get a chance!

[melvin-bot]

@trjExpensify, @mountiny, @aimane-chnaif, @dukenv0307 Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

@trjExpensify, @mountiny, @aimane-chnaif, @dukenv0307 Huh... This is 4 days overdue. Who can take care of this?

[trjExpensify]

@aimane-chnaif awaiting the checklist. What's your ETA on completing that, please?

[aimane-chnaif]

• The PR that introduced the bug has been identified. Link to the PR: Create v1 Collect workspace Bottom Up flow #30582
• 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: https://github.com/Expensify/App/pull/30582/files#r1440329343
• A discussion in #expensify-bugs 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
• Determine if we should create a regression test for this bug.
• If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

There's already regression test (caught by QA) so no need another one

[trjExpensify]

Thanks! Confirming payments due are:

$500 to @aimane-chnaif for the C+ review
$500 to @dukenv0307 for the fix

Settled up!