Skip to content

[Due for payment 2026-02-23] Single-use & Expire-by Virtual Expensify Cards #77672

Closed

Description

@lakchote

For more context please read the design doc.

Will be handled by an external contributor (@nkdengineer).

Activity

  1. self-assigned this
    on Dec 15, 2025
  2. dukenv0307 commented on Dec 16, 2025

    @dukenv0307
    Contributor

    @lakchote I don’t have many tasks at the moment, so I can help take it as C+

  3. lakchote commented on Dec 18, 2025

    @lakchote
    ContributorAuthor

    @dukenv0307 the implementation should start in January, will you be available and responsive? This is a high-priority project.

  4. dukenv0307 commented on Dec 18, 2025

    @dukenv0307
    Contributor

    @lakchote Yes, I'll be available

  5. melvin-bot commented on Jan 13, 2026

    @melvin-bot

    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!

  6. nkdengineer commented on Jan 22, 2026

    @nkdengineer
    Contributor

    @lakchote After checking the design doc, we have three main tasks todo:

    • Update the create Expensify card flow
    • Update the edit card flow
    • Update display card

    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

  7. lakchote commented on Jan 23, 2026

    @lakchote
    ContributorAuthor

    @nkdengineer each task should have its own PR

  8. changed the title [-](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[/+] on Jan 23, 2026
  9. 45 remaining items

  10. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 9, 2026
  11. melvin-bot commented on Mar 9, 2026

    @melvin-bot

    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.

  12. removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 9, 2026
  13. MelvinBot commented on Mar 9, 2026

    @MelvinBot
    Contributor

    🔍 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:

    PR Title Merged Files Changed
    #80210 feat: Single-use and Expire-by virtual cards 2026-02-06 35 files
    #81783 Update edit card flow 2026-02-11 14 files
    #81832 Update card display for employee 2026-02-13 2 files

    Deploy Blockers (Regressions)

    Four deploy blockers were linked to this issue after the feature shipped:

    1. [Due for payment 2026-02-23] Expensify Card - Separator line is shown when there is no content below on Limit type page #82279 (Closed) — Separator line shown when there is no content below on Limit type page
    2. [Due for payment 2026-02-23] Expensify Card - Smart limit description is truncated when selected #82326 (Closed) — Smart limit description is truncated when selected
    3. [Due for payment 2026-02-26] Web - Expensify Card - "g" in Single-use is cut off on card row #82320 (Open) — "g" in Single-use is cut off on card row (Web)
    4. Expensify Card - Limit type still shows validity when Set expiry date is disabled #82458 (Closed) — Limit type still shows validity when Set expiry date is disabled

    Three of the four deploy blockers have been resolved. #82320 remains open (text truncation on the card row on Web).

    Payment Status

    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.

    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.

  14. lakchote commented on Mar 9, 2026

    @lakchote
    ContributorAuthor

    @lydiabarclay hi! Could you please process payment for @nkdengineer and @dukenv0307? Thanks!

  15. lydiabarclay commented on Mar 9, 2026

    @lydiabarclay
    Contributor

    Just to confirm @lakchote, $1000 for each?

  16. 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
  17. lydiabarclay commented on Mar 11, 2026

    @lydiabarclay
    Contributor

    Also @lakchote do we need a BZ checklist here?

  18. lakchote commented on Mar 13, 2026

    @lakchote
    ContributorAuthor

    @lydiabarclay, that's correct, $1000 for each

    No need, for a BZ checklist here as it's a new feature

    Thanks!

  19. lydiabarclay commented on Mar 14, 2026

    @lydiabarclay
    Contributor

    Payment Summary

    Contributor+: @dukenv0307 due $1000 via NewDot
    Contributor+: @nkdengineer due $1000 via NewDot

    ✅ No regression test needed

  20. quinthar commented on Mar 18, 2026

    @quinthar
    Contributor

    Approved $1000 to @dukenv0307

  21. twisterdotcom commented on Mar 19, 2026

    @twisterdotcom
    Contributor

    @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-6b3e906fb114
  22. bernhardoj commented on Jul 7, 2026

    @bernhardoj
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions