[Due for payment 2026-08-21] [$250] [CFI] Company Cards - Expand feed removal confirmation copy to mention deleted unsubmitted transactions

[MelvinBot]

Problem

When an admin removes a card feed, the confirmation modal warns "Are you sure you want to remove this card feed? This will unassign all cards." This undersells the impact: removing a feed also deletes unsubmitted (unreported/draft) transactions. Admins — especially new ones — can trigger a destructive action without understanding the full consequences, and for commercial feeds they currently can't re-add the feed themselves.

Solution

Update the removal confirmation copy to also mention that unsubmitted transactions will be deleted.

Copy key: workspace.companyCards.removeCardFeedDescription in src/languages/en.ts:6338

Current:

Are you sure you want to remove this card feed? This will unassign all cards.

Proposed:

Are you sure you want to remove this card feed? This will unassign all cards and delete unsubmitted transactions.

The modal title (removeCardFeedTitle, e.g. "Remove Mock Bank feed") stays as-is. The Spanish string src/languages/es.ts:6088 should get the equivalent update.

Slack thread: https://expensify.slack.com/archives/C07NMDKEFMH/p1785797681542709

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022086826828482385942
• Upwork Job ID: 2086826828482385942
• Last Price Increase: 2026-08-10

Issue Owner

Current Issue Owner: @mallenexpensify

[trjExpensify]

@MelvinBot draft a proposal for this change.

[MelvinBot]

Proposal

What is the root cause of that problem?

The feed-removal confirmation copy only mentions one of the two destructive side effects. Removing a card feed both unassigns all cards and deletes unsubmitted (unreported/draft) transactions, but the confirmation string only warns about the first. As a result an admin can confirm a destructive delete without understanding the full consequences.

The string is rendered as the prompt of the confirm modal in WorkspaceCompanyCardsSettingsPage.tsx:221, which resolves to the workspace.moreFeatures.companyCards.removeCardFeedDescription key. (Note: the correct key path is workspace.moreFeatures.companyCards.…, not workspace.companyCards.… as written in the issue body — the line numbers cited are correct.)

The gap is only in the copy — the sibling card-level strings already spell out this behavior, e.g. unassignCardDescription ("Unassigning this card will remove all unsubmitted transactions"), so the feed-level string is simply out of step.

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

Update the confirmation description in both language files to also mention deleted unsubmitted transactions. Title (removeCardFeedTitle) stays unchanged.

English — src/languages/en.ts:6338:

• Current: Are you sure you want to remove this card feed? This will unassign all cards.
• Proposed: Are you sure you want to remove this card feed? This will unassign all cards and delete unsubmitted transactions.

Spanish — src/languages/es.ts:6088:

• Current: ¿Estás seguro de que deseas eliminar esta fuente de tarjetas? Esto anulará la asignación de todas las tarjetas.
• Proposed: ¿Estás seguro de que deseas eliminar esta fuente de tarjetas? Esto anulará la asignación de todas las tarjetas y eliminará las transacciones no enviadas.

The Spanish wording reuses the existing convention "transacciones no enviadas" already used in the neighboring unassignCardDescription string, so it stays consistent across the company-cards flow.

This is a copy-only change in the two src/languages/*.ts files — no component or logic changes are required.

What alternative solutions did you explore? (Optional)

• List both consequences on separate lines / as bullets for extra clarity. Rejected as heavier than needed — a single appended clause matches the phrasing style of the sibling card strings and keeps the modal compact.
• Also address the "can't re-add commercial feeds themselves" concern raised in the issue background. That's a separate functional gap (not copy) and out of scope for this copy update; it should be tracked separately if desired.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/97842#issuecomment-5186067361) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[melvin-bot]

⚠️ Could not update price automatically because there is no linked Upwork Job ID. The BZ team member will need to update the price manually in Upwork.

[melvin-bot]

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

[melvin-bot]

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