Repository navigation
[Due for payment 2026-10-07] [CFI][FE 1/7] Payment history: add the "View payment history" RHP page and route #101828
Description
Sub-task of [CFI] Add a "View payment history" page with historical billing receipts and monthly user activity.
Goal
Clicking Account > Subscription > View payment history opens a new, empty View payment history page in the RHP instead of navigating to the Expenses (Spend) page.
Scope
- New screen name, route, and navigator registration for the page.
- Page shell only:
ScreenWrapper+HeaderWithBackButtontitled "View payment history", a loading skeleton, and an empty state. No purchase data yet — that lands in FE 2/7. - Repoint the entry point. The menu item currently calls
viewPurchases()insrc/pages/settings/Subscription/CardSection/CardSection.tsx, which builds a Search query (type:expense, merchantExpensify, Inc., all statuses) and navigates to the Expenses page. Route to the new page instead. - Gate the new destination on the payment-history beta. The backend push of the full purchase list is beta-gated (tracked in a separate internal issue), so until the whole feature has shipped the new page would be empty for everyone else. Read
betasfrom Onyx, keepviewPurchases()on the non-beta path, and only delete it when the beta is removed. - Keep the existing
hasPurchasescondition that decides whether the menu item renders at all. - Add the page title copy to every
src/languages/*.tslocale.
Files likely touched
src/SCREENS.ts— add underSETTINGS.SUBSCRIPTIONsrc/ROUTES.tssrc/libs/Navigation/linkingConfig/config.tssrc/libs/Navigation/AppNavigator/ModalStackNavigators/index.tsx- The settings navigator param list in
src/libs/Navigation/types.ts src/pages/settings/Subscription/PaymentHistory/(new)src/languages/*.ts
Acceptance criteria
- In beta: tapping View payment history opens the new RHP page; back returns to the Subscription page.
- Not in beta: behaviour is unchanged (Expenses page filtered to the Expensify merchant).
- Deep-linking the route directly opens the page — web and native, wide and narrow.
- Loading and empty states render with no layout shift.
Depends on
Nothing — this can start now. The beta itself is defined in the backend work; if that hasn't merged yet, wire against the agreed beta name so the gate is ready.
Easy to get wrong
- Deleting
viewPurchases()outright in this PR — non-beta users would lose all access to their receipts. - Registering the route in only one place. The screen constant, the route, the linking config, the modal stack, and the navigation param list all need it, or TypeScript and deep links break.
Issue Owner
Current Issue Owner: @mallenexpensifyMetadata
Metadata
Type
Projects
- Status
Activity
[-][CFI][FE 1/7] Payment history: add the "View payment history" RHP page and route[/-][+][Due for payment 2026-10-07] [CFI][FE 1/7] Payment history: add the "View payment history" RHP page and route[/+]6 remaining items
melvin-bot commentedon Oct 6, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 6, 2026
Payment Summary
Resolving PRs:
Add payment history page #102377
Contributor: @dukenv0307 does not require payment (Contractor)
Reviewer: @nkdengineer owed $175 via NewDot
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Oct 8, 2026
Payment Summary
Contributor+: @nkdengineer due $175 via NewDot
@nkdengineer plz complete the Contributor+ checklist and tag me in a post once you have. Thx
nkdengineer commentedon Oct 9, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: N/A (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 Template. Needed for all bugs AND new features
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
nkdengineer commentedon Oct 9, 2026
@mallenexpensify I completed the checklist.