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
This issue has not been updated in over 15 days. @lakchote eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Summary: This is a completed feature implementation for "Single-use & Expire-by Virtual Expensify Cards." All three implementation PRs have been merged and deployed to production. The issue is currently open for payment processing.
Current State: Feature fully deployed. Payment of $1000 agreed upon by all parties. Awaiting final payment processing.
Implementation Overview
The feature was delivered across three PRs, all now merged:
lakchote (internal engineer) confirmed it as reasonable
The issue has the Awaiting Payment label
Notable Issue During Development
A backend compatibility issue was identified and resolved during development: the frontend was sending timestamps with milliseconds (e.g., 2026-02-10 08:00:00.000), but the PHP backend expected the format 2026-02-10 08:00:00 without milliseconds. This was caught and fixed before merge.
Payment processing needs to be completed for all three PRs.
No further code investigation needed. This feature is fully implemented and deployed. The remaining action items are resolving the open deploy blocker (#82320) and processing payment.
changed the title [-][Due for payment 2026-02-23] [Due for payment 2026-02-20] Single-use & Expire-by Virtual Expensify Cards[/-][+][Due for payment 2026-02-23] Single-use & Expire-by Virtual Expensify Cards[/+]on Mar 9, 2026
Activity
dukenv0307 commentedon Dec 16, 2025
@lakchote I don’t have many tasks at the moment, so I can help take it as C+
lakchote commentedon Dec 18, 2025
@dukenv0307 the implementation should start in January, will you be available and responsive? This is a high-priority project.
dukenv0307 commentedon Dec 18, 2025
@lakchote Yes, I'll be available
melvin-bot commentedon Jan 13, 2026
This issue has not been updated in over 15 days. @lakchote eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
nkdengineer commentedon Jan 22, 2026
@lakchote After checking the design doc, we have three main tasks todo:
Do we want to do each task in one PR or only do this in one PR?
I'm working on updating the Expensify card flow here
lakchote commentedon Jan 23, 2026
@nkdengineer each task should have its own PR
[-](Single-use & Expire-by Virtual Expensify Cards) [HOLD Backend impl] Single-use and Expire-by virtual cards[/-][+](Single-use & Expire-by Virtual Expensify Cards) Single-use and Expire-by virtual cards[/+]45 remaining items
melvin-bot commentedon Mar 9, 2026
Triggered auto assignment to @lydiabarclay (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.MelvinBot commentedon Mar 9, 2026
🔍 Issue Analysis
Summary: This is a completed feature implementation for "Single-use & Expire-by Virtual Expensify Cards." All three implementation PRs have been merged and deployed to production. The issue is currently open for payment processing.
Current State: Feature fully deployed. Payment of $1000 agreed upon by all parties. Awaiting final payment processing.
Implementation Overview
The feature was delivered across three PRs, all now merged:
Deploy Blockers (Regressions)
Four deploy blockers were linked to this issue after the feature shipped:
Three of the four deploy blockers have been resolved. #82320 remains open (text truncation on the card row on Web).
Payment Status
nkdengineerproposed $1000 total: $500 for PR feat: Single-use and Expire-by virtual cards #80210, $250 each for PRs [Single-use and Expire-by virtual cards]: update edit card flow #81783 and [Single-use and Expire-by virtual cards]: update card to display for employee #81832dukenv0307(C+) approved the pricinglakchote(internal engineer) confirmed it as reasonableAwaiting PaymentlabelNotable Issue During Development
A backend compatibility issue was identified and resolved during development: the frontend was sending timestamps with milliseconds (e.g.,
2026-02-10 08:00:00.000), but the PHP backend expected the format2026-02-10 08:00:00without milliseconds. This was caught and fixed before merge.Open Items
No further code investigation needed. This feature is fully implemented and deployed. The remaining action items are resolving the open deploy blocker (#82320) and processing payment.
lakchote commentedon Mar 9, 2026
@lydiabarclay hi! Could you please process payment for @nkdengineer and @dukenv0307? Thanks!
lydiabarclay commentedon Mar 9, 2026
Just to confirm @lakchote, $1000 for each?
[-][Due for payment 2026-02-23] [Due for payment 2026-02-20] Single-use & Expire-by Virtual Expensify Cards[/-][+][Due for payment 2026-02-23] Single-use & Expire-by Virtual Expensify Cards[/+]lydiabarclay commentedon Mar 11, 2026
Also @lakchote do we need a BZ checklist here?
lakchote commentedon Mar 13, 2026
@lydiabarclay, that's correct, $1000 for each
No need, for a BZ checklist here as it's a new feature
Thanks!
lydiabarclay commentedon Mar 14, 2026
Payment Summary
Contributor+: @dukenv0307 due $1000 via NewDot
Contributor+: @nkdengineer due $1000 via NewDot
✅ No regression test needed
quinthar commentedon Mar 18, 2026
Approved $1000 to @dukenv0307
twisterdotcom commentedon Mar 19, 2026
@nkdengineer has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-cde7-a7fd-c930-6b3e906fb114bernhardoj commentedon Jul 7, 2026
The PR for this issue causes the limit type to be shown twice when the card is revealed.