You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-10-07] [CFI][FE 1/7] Payment history: add the "View payment history" RHP page and route #101828
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 + HeaderWithBackButton titled "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() in src/pages/settings/Subscription/CardSection/CardSection.tsx, which builds a Search query (type:expense, merchant Expensify, 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 betas from Onyx, keep viewPurchases() on the non-beta path, and only delete it when the beta is removed.
Keep the existing hasPurchases condition that decides whether the menu item renders at all.
Add the page title copy to every src/languages/*.ts locale.
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.
changed the title [-][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[/+]on Sep 30, 2026
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[/+]19 remaining items
nkdengineer commentedon Oct 27, 2026
@mallenexpensify Based on this, could you please update the payment summary here to $250?
mallenexpensify commentedon Oct 27, 2026
@nkdengineer , I think I might have messed that one up. I checked with Claude
Where 2026-09-19 is the cutoff for $250 price. Is there a link or discussion showing the project started before 2026-09-19 ?
nkdengineer commentedon Oct 30, 2026
@mallenexpensify We can close this now.
twisterdotcom commentedon Oct 30, 2026
$175 approved for @nkdengineer in Report ID: R00AEZwhfU8x.
Zapier Logs
Run ID: 00040eee-172f-a465-be0d-42880b17ec44SO: https://stackoverflowteams.com/c/expensify/questions/7582
mallenexpensify commentedon Oct 30, 2026
@twisterdotcom 👀 above plz
twisterdotcom commentedon Nov 2, 2026
All sorted. Too many comments with the string
payment summaryin for my poor little automation.