[Standardize payment button] Invoice feature

[hungvu193]

Explanation of Change

This PR implements one-click payment for Invoices.

Fixed Issues

$ #55876
PROPOSAL: N/A

Tests

Same as QA steps.

• Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Prerequisite:
User A: Your workspace has the invoice feature enabled.

1. Login with User A.
2. Send a couple of invoices to User B
3. Login with User B and pay the invoices from User A.
4. Verify that you can pay the invoice successfully for the first time.
5. After that, verify that you can click on the button to pay the invoice directly without using the dropdown menu.

• 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
  • MacOS: Desktop
• 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: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2025-10-22.at.17.05.58.mov

MacOS: Desktop

Screen.Recording.2025-10-22.at.17.07.00.mov

[codecov]

Codecov Report

❌ Patch coverage is 16.03774% with 89 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/components/SettlementButton/index.tsx	0.00%	64 Missing ⚠️
src/pages/home/report/PureReportActionItem.tsx	18.18%	9 Missing ⚠️
src/libs/ReportUtils.ts	0.00%	6 Missing ⚠️
src/libs/actions/BankAccounts.ts	33.33%	4 Missing ⚠️
...ts/SelectionListWithSections/Search/ActionCell.tsx	57.14%	3 Missing ⚠️
src/libs/actions/Policy/Policy.ts	0.00%	2 Missing ⚠️
...ionListWithSections/Search/TransactionListItem.tsx	0.00%	1 Missing ⚠️

Files with missing lines	Coverage Δ
...WithSections/Search/UserInfoAndActionButtonRow.tsx	100.00% <100.00%> (ø)
src/libs/SearchUIUtils.ts	70.30% <100.00%> (+0.03%)	⬆️
src/pages/home/report/ReportActionItem.tsx	100.00% <ø> (ø)
...rkspaceWorkflowsConnectExistingBankAccountPage.tsx	0.00% <ø> (ø)
...ionListWithSections/Search/TransactionListItem.tsx	1.63% <0.00%> (ø)
src/libs/actions/Policy/Policy.ts	32.13% <0.00%> (-0.09%)	⬇️
...ts/SelectionListWithSections/Search/ActionCell.tsx	51.51% <57.14%> (+3.12%)	⬆️
src/libs/actions/BankAccounts.ts	1.01% <33.33%> (+1.01%)	⬆️
src/libs/ReportUtils.ts	74.64% <0.00%> (-0.02%)	⬇️
src/pages/home/report/PureReportActionItem.tsx	52.87% <18.18%> (-0.61%)	⬇️
... and 1 more

... and 8 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hungvu193]

Mostly ready, will do a round of test later today.

[hungvu193]

I'd say this is ready for review! I'll complete the screenshots/videos tomorrow.

About paying on Search page. I'd like to wait until we have final decision on our convo here.

[melvin-bot]

@getusha 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]

[github-actions]

🚧 @joekaufmanexpensify has triggered a test Expensify/App build. You can view the workflow run here.

[grgia]

@hungvu193 could you merge main / fix the Mobil conflict?

Is there anything I need to know for this review?

[hungvu193]

Is there anything I need to know for this review?

Nothing special, please go ahead and review. I'm working on IOU, will resolve the conflict before EOD.

[getusha]

BUG: Unable to pay an expense with last payment method saved.

• Go to an expense with Mark as paid last payment value

Screen.Recording.2025-10-22.at.6.36.33.in.the.evening.mov

[hungvu193]

BUG: Unable to pay an expense with last payment method saved.

Can you reproduce it consistently? Is there any precondition?

Screen.Recording.2025-10-22.at.23.04.43.mov

[hungvu193]

I think I found the case here 🤔 , but I found it during testing #72847 lol 😂 . I believe it's also on main.
Steps:

1. Create expense > submit > approve > Pay it.
2. Create another expense.
3. Change it to another workspace.
4. Try to pay it with one-click payment.

Screen.Recording.2025-10-22.at.23.18.09.mov

Screen.Recording.2025-10-22.at.23.21.33.mov

Since it's expense related logic, I think we should also update the last payment method while changing the workspace. Can you handle it please? @getusha

[getusha]

Since it's expense related logic, I think we should also update the last payment method while changing the workspace. Can you handle it please? @getusha

i think we handled this case before, i'll take a look.

[hungvu193]

Cool. Let's not block this PR since this is also on main.

[grgia]

@getusha @hungvu193 what's left to fix before merging?

[hungvu193]

All yours @getusha

[getusha]

One small bug: Duplicate system message when marking an invoice as paid from Reports page

Screen.Recording.2025-10-24.at.4.20.34.in.the.afternoon.mov

[hungvu193]

One small bug: Duplicate system message when marking an invoice as paid from Reports page

Screen.Recording.2025-10-24.at.4.20.34.in.the.afternoon.mov

It's on main I believe.

#72651

[hungvu193]

Should be ready for your final review @grgia

[grgia]

@hungvu193 @getusha great work getting this so thoroughly tested! It tests well on my end, let's get this to QA & Customers 🚀

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by https://github.com/grgia in version: 9.2.39-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[OSBotify]

🚀 Deployed to production by https://github.com/puneetlath in version: 9.2.39-3 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅