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
Hide expired virtual Expensify cards from the Expensify Wallet #84752
Bug: Expired virtual card still visible in Expensify Wallet
A virtual card ending in 0371 expired on 5 March 2026 but continues to appear in the Expensify Wallet as of 10 March. The issue persists after signing out and back in, ruling out a session or Onyx update problem.
The card should be removed from the Wallet once it has expired.
Note: There will be a backend fix to prevent them from being returned in the first place if they are expired. With that being said, we should, as a safety measure, hide them if we encounter them.
[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 requirement
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
lakchote commentedon Mar 10, 2026
cc @nkdengineer
nkdengineer commentedon Mar 10, 2026
@lakchote Please assign me
lakchote commentedon Mar 10, 2026
Done
nkdengineer commentedon Mar 11, 2026
@dukenv0307 The PR is ready for review.
nkdengineer commentedon Mar 16, 2026
@lakchote Raised a follow-up PR cc @dukenv0307
nkdengineer commentedon Mar 31, 2026
@mallenexpensify The PR was deployed to production 2 weeks ago. This is ready for payment.
2 remaining items
melvin-bot commentedon Apr 2, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Apr 2, 2026
Payment Summary
Contributor: @nkdengineer due $250 via NewDot
Contributor+: @dukenv0307 due $250 via NewDot
@dukenv0307 plz complete the BZ checklist and tag me in a post once you have. Thx
dukenv0307 commentedon Apr 13, 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 requirement
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-a218-a726-a8f7-4ea3cab78474dukenv0307 commentedon Apr 13, 2026
@mallenexpensify Done
garrettmknight commentedon Apr 14, 2026
$250 approved for @dukenv0307
twisterdotcom commentedon Apr 22, 2026
@nkdengineer has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-518c-a458-bfe3-1c68287e8be4