Skip to content

[Due for payment 2025-08-20] [$250] Payment card authentication issues #65681

Closed

Description

@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?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @jmusial
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

  1. Add a card for a subscription payment
  2. Stop when CardAuthenticationModal appears
  3. Close the modal
  4. Navigate to mobile app
  5. Every time you navigate to "Subscription" a NotFound page is there as a first page (Assume this is the modal, but not visible for apps ?)
  6. When clicking "Authenticate payment" You get a a NotFound page

Expected Result:

Assuming operations on cards are disabled on mobile apps user should see Subscription screen with no "Authenticate Payment" action and with information that this needs to be done on web app.

Actual Result:

Every time you navigate to "Subscription" a NotFound page is there as a first page (Assume this is the modal, but not visible for apps ?)
When clicking "Authenticate payment" You get a a NotFound page

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Simulator.Screen.Recording.-.iPhone.16e.-.2025-07-08.at.17.44.51.mp4
android.mov

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021945173372979056983
  • Upwork Job ID: 1945173372979056983
  • Last Price Increase: 2025-07-15
  • Automatic offers:
    • Krishna2323 | Contributor | 108209165
Issue OwnerCurrent Issue Owner: @laurenreidexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 8, 2025
  2. melvin-bot commented on Jul 8, 2025

    @melvin-bot

    Triggered auto assignment to @maddylewis (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.

  3. MelvinBot commented on Jul 8, 2025

    @MelvinBot
    Contributor

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

  4. ZhenjaHorbach commented on Jul 15, 2025

    @ZhenjaHorbach
    Contributor

    Can reproduce
    Can be a reviewer here !

    2025-07-15.09.55.01.mov
  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 15, 2025
  6. changed the title [-]Payment card authentication issues[/-] [+][$250] Payment card authentication issues[/+] on Jul 15, 2025
  7. melvin-bot commented on Jul 15, 2025

    @melvin-bot
  8. 44 remaining items

  9. melvin-bot commented on Aug 13, 2025

    @melvin-bot

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

  10. melvin-bot commented on Aug 13, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.93-7 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 2025-08-20. 🎊

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

  11. melvin-bot commented on Aug 13, 2025

    @melvin-bot

    @ZhenjaHorbach @laurenreidexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  12. Krishna2323 commented on Aug 15, 2025

    @Krishna2323
    Contributor

    @laurenreidexpensify Please note that I have ended the Upwork contract as I am now eligible for payments through NewDot. Thank you for understanding.

    Ref: #64948 (comment)

  13. ZhenjaHorbach commented on Aug 20, 2025

    @ZhenjaHorbach
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      It's more of a new feature

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    I'm not sure we need tests here since we just hid the buttons for native apps

  14. laurenreidexpensify commented on Aug 21, 2025

    @laurenreidexpensify
    Contributor

    Payment Summary

    • $250 @ZhenjaHorbach requires payment through NewDot Manual Requests (reviewer)
    • $250 @Krishna2323 requires payment through NewDot Manual Requests (Contributor)
  15. ZhenjaHorbach commented on Aug 21, 2025

    @ZhenjaHorbach
    Contributor

    Requested in ND !

  16. Krishna2323 commented on Aug 25, 2025

    @Krishna2323
    Contributor

    Requested in ND!

  17. quinthar commented on Aug 28, 2025

    @quinthar
    Contributor

    $250 approved to @ZhenjaHorbach

  18. flaviadefaria commented on Sep 8, 2025

    @flaviadefaria
    Contributor

    $250 approved for @Krishna2323

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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions