Skip to content

[Home Page] Add a Time Sensitive case for failed billing for existing customers #81726

Closed

Description

@JmillsExpensify

Chatting with the Concierge team last week in SF, one common point of customer friction occurs when billing their payment card fails. We do notify them of email, though in-app we lack a clear place that notifies the user how to resolve, that's obvious and free of distractions.

In this issue we'll add a new Time sensitive case for failed billing, which has the following changes:

Design details

  • Section title is Time sensitive (strong text like all Home header titles)
  • Icon is Credit Card (tangerine 500; tangerine 100 border)
  • Supporting text is "Account > Subscription"
  • Bolded text is "We couldn't bill your card on file"
  • Button is "danger" color and text is "Fix"

Product details

  • This exclusively applies to existing customers with failed billing
  • This section only shows based on these conditions:
    • Non-zero PRIVATE_AMOUNT_OWED
    • PRIVATE_BILLING_STATUS, with declineReason of insufficient_funds, expired_card
    • User also has a failed purchases in the same table
  • Tapping the Fix button takes the user to /settings/subscription/add-payment-card (actually we might have a separate route if you have a card?)
  • The Time sensitive slot always appears at the top of the left-side of the Home page
Image

EXFY-18098

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    NewFeatureSomething to build that is a new item.
    on Feb 6, 2026
  2. melvin-bot commented on Feb 6, 2026

    @melvin-bot

    Current assignee @JmillsExpensify is eligible for the NewFeature assigner, not assigning anyone new.

  3. melvin-bot commented on Feb 6, 2026

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (NewFeature)

  4. dubielzyk-expensify commented on Feb 9, 2026

    @dubielzyk-expensify
    Contributor

    Could we change Account > Subscription to just Subscription or Your subscription? Feels overly detailed to me to explain where it lives when the button will navigate there anyways

  5. JmillsExpensify commented on Feb 11, 2026

    @JmillsExpensify
    ContributorAuthor

    I think we just decided to remove it.

  6. 23 remaining items

  7. melvin-bot commented on Mar 25, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  8. melvin-bot commented on Mar 25, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.43-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-04-01. 🎊

    For reference, here are some details about the assignees on this issue:

  9. melvin-bot commented on Mar 25, 2026

    @melvin-bot

    BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@ZhenjaHorbach] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
    • [] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
  10. melvin-bot commented on Mar 25, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  11. ZhenjaHorbach commented on Mar 25, 2026

    @ZhenjaHorbach
    Contributor

    I suppoe we don't need a payment here
    It's a part of the project
    So I think we can close it!

  12. grgia commented on Mar 26, 2026

    @grgia
    Contributor

    closing!

  13. changed the title [-][Due for payment 2026-04-01] [Home Page] Add a Time Sensitive case for failed billing for existing customers[/-] [+][Home Page] Add a Time Sensitive case for failed billing for existing customers[/+] on Mar 26, 2026
  14. JmillsExpensify commented on Apr 9, 2026

    @JmillsExpensify
    ContributorAuthor

    Looks like we didn't add regression steps for this one?

  15. JmillsExpensify commented on Apr 10, 2026

    @JmillsExpensify
    ContributorAuthor

    I added one

  16. JmillsExpensify commented on Apr 10, 2026

    @JmillsExpensify
    ContributorAuthor

    Let's be careful of closing issues that don't have regression tests.

  17. mountiny commented on Apr 11, 2026

    @mountiny
    Contributor

    thanks!

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 productionInternalRequires API changes or must be handled by Expensify staffNewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions