[Due for payment 2026-04-20][$250] “Deleted Card” Label Shown for E-Card Transactions in Expense Report View

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number:
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @jasperhuangg
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Go to Staging environment
2. Open an expense report containing E-card transactions
3. View transaction details

Expected Result:

Transactions should display:
Correct card association (active/assigned card)
No misleading “Deleted card” label

Actual Result:

Some transactions show “Deleted card”

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022040084374328665354
• Upwork Job ID: 2040084374328665354
• Last Price Increase: 2026-04-03

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[MelvinBot]

Proposal

What is the root cause of that problem?

doesCardFeedExist() (CardUtils.ts:688-698) relies on getOriginalCompanyFeeds() to look up whether a transaction's card feed still exists. However, getOriginalCompanyFeeds() explicitly filters out entries where key === CONST.EXPENSIFY_CARD.BANK ('Expensify Card'). This means doesCardFeedExist('Expensify Card', cardFeeds) always returns false.

The isCardFeedDeleted flag is then computed as !!transaction.bank && !doesCardFeedExist(...) in both CardUtils.ts:1561-1563 (report view) and SearchUIUtils.ts:1776 (search view). For Expensify Card transactions (bank = 'Expensify Card'), this always evaluates to true.

Finally, TransactionItemRow/index.tsx:267-268 checks isCardFeedDeleted && cardID and displays the workspace.companyCards.deletedCard translation ("Deleted card") — which fires for every Expensify Card transaction.

What changes do you think we should make in order to solve the problem?

Guard the isCardFeedDeleted computation to skip Expensify Card transactions, since Expensify Cards are managed separately from third-party company card feeds and should never be flagged as "deleted feeds."

In both locations where isCardFeedDeleted is computed:

1. CardUtils.ts:1561-1563 (resolveTransactionCardFields): Add a check so that when transaction.bank === CONST.EXPENSIFY_CARD.BANK, isCardFeedDeleted is set to false instead of calling doesCardFeedExist.

2. SearchUIUtils.ts:1776: Same guard — when transactionItem.bank === CONST.EXPENSIFY_CARD.BANK, set isCardFeedDeleted to false.

This is the most targeted fix because it addresses the problem at the source (the flag computation) rather than patching it at the display layer, and it doesn't require modifying getOriginalCompanyFeeds or doesCardFeedExist which may intentionally filter Expensify Cards for other purposes.

What alternative solutions did you explore? (Optional)

• Modifying doesCardFeedExist to not use getOriginalCompanyFeeds: This would work but risks side effects since getOriginalCompanyFeeds intentionally excludes Expensify Cards from the company card feed list for display purposes.
• Adding a guard in TransactionItemRow: Would only fix the display but leave the underlying data (isCardFeedDeleted = true) incorrect, which could cause issues elsewhere.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @truph01 (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022040084374328665354

[wildan-m]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Transactions made with Expensify Cards incorrectly display a "Deleted card" label in the expense report view, even though the card is active and assigned.

What is the root cause of that problem?

doesCardFeedExist() uses getOriginalCompanyFeeds() to look up whether a transaction's card feed still exists:

App/src/libs/CardUtils.ts

Lines 688 to 701 in 8f18e9b

	function doesCardFeedExist(feed: CompanyCardFeed | undefined, cardFeeds: OnyxCollection<CardFeeds> | undefined): boolean {
	if (!feed || !cardFeeds) {
	return false;
	}
	for (const feedData of Object.values(cardFeeds)) {
	const companyFeeds = getOriginalCompanyFeeds(feedData);
	if (feed in companyFeeds) {
	return true;
	}
	}
	return false;
	}

However, getOriginalCompanyFeeds() explicitly filters out entries where key === CONST.EXPENSIFY_CARD.BANK ('Expensify Card'):

App/src/libs/CardUtils.ts

Lines 585 to 586 in 8f18e9b

	if (key === CONST.EXPENSIFY_CARD.BANK) {
	return false;

This means doesCardFeedExist('Expensify Card', cardFeeds) always returns false, causing isCardFeedDeleted to be set to true for every Expensify Card transaction in both resolveTransactionCardFields() and the search transaction mapping:

App/src/libs/CardUtils.ts

Lines 1561 to 1563 in 8f18e9b

	// Resolve isCardFeedDeleted
	if (cardFeeds !== undefined) {
	updates = {...updates, isCardFeedDeleted: !!transaction.bank && !doesCardFeedExist(transaction.bank as CompanyCardFeed, cardFeeds)};

App/src/libs/SearchUIUtils.ts

Line 1776 in 8f18e9b

const isCardFeedDeleted = cardFeeds === undefined ? undefined : !!transactionItem.bank && !doesCardFeedExist(transactionItem.bank as OnyxTypes.CompanyCardFeed, cardFeeds);

Finally, TransactionItemRow checks isCardFeedDeleted && cardID and displays "Deleted card":

App/src/components/TransactionItemRow/index.tsx

Lines 267 to 268 in 8f18e9b

	if (transactionItem.isCardFeedDeleted && transactionItem.cardID) {
	return translate('workspace.companyCards.deletedCard');

Additionally, getFeedNameForDisplay() also calls doesCardFeedExist() and would return "Deleted feed" for Expensify Card feeds when displaying card group names in search results:

App/src/libs/CardUtils.ts

Lines 737 to 740 in 8f18e9b

	const feedExists = doesCardFeedExist(feed, cardFeeds);
	if (!feedExists) {
	return translate('workspace.companyCards.deletedFeed');

What changes do you think we should make in order to solve the problem?

Fix doesCardFeedExist() to return true when the feed is CONST.EXPENSIFY_CARD.BANK. Expensify Cards are a built-in card type managed separately from third-party company card feeds — they always exist and should never be flagged as a "deleted feed".

Add an early return at the top of doesCardFeedExist():

if (feed === CONST.EXPENSIFY_CARD.BANK) {
    return true;
}

And widen the parameter type from CompanyCardFeed | undefined to CardFeed | undefined (the CardFeed type already exists and is defined as CompanyCardFeed | typeof CONST.EXPENSIFY_CARD.BANK).

This single-location fix addresses the root cause for all three callers: the isCardFeedDeleted computation in resolveTransactionCardFields(), the isCardFeedDeleted computation in SearchUIUtils.ts, and the getFeedNameForDisplay() function — without needing to patch each call site individually.

What alternative solutions did you explore? (Optional)

1. Guarding isCardFeedDeleted at each computation site — this would require changes in two locations (CardUtils.ts:1563 and SearchUIUtils.ts:1776) but would miss the third caller (getFeedNameForDisplay at line 737) which would still return "Deleted feed" for Expensify Card feeds.
2. Modifying getOriginalCompanyFeeds to not filter Expensify Cards — this would work but changes the semantics of a function that intentionally separates Expensify Cards from third-party company card feeds for display/management purposes.

Compare branch: https://github.com/Expensify/App/compare/main...wildan-m:App:wildan/87098-deleted-card-expensify-card?expand=1

[trasnake87]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[trasnake87]

Contributor details
Your Expensify account email: trasnake87@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~010f770315ab181656