[Payment card / Subscription] There is no Retry payment button but payment failed

[izarutskaya]

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: v9.0.4-6
Reproducible in staging?: Y
Reproducible in production?: N
Found when executing PR : #44268
Email or phone of affected tester (no customers): irvgut7@gmail.com and irvgut7+050724@gmail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

NewDot

1. Go directly to subscription page - https://staging.new.expensify.com/settings/subscription
2. Add a payment card if you don't have it
3. Click to Subscriptions (we should go to OldDot)

OldDot:

4. Subscribe to Expensify.org on Workspaces page
5. Go to Settings>Account>Payments
6. Scroll down (you should see that payment failing)

7 Go back to NewDot and click Retry payment

Expected Result:

The user should see the Retry payment button.

Actual Result:

When user returns to NewDot, he does not see Retry payment button but payment failed.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Recording.2598.mp4

Recording.2594.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @carlosmiceli (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[mountiny]

this is behind beta so not a blocker @blimpich in case you could handle this

[izarutskaya]

@dylanexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[izarutskaya]

We think this issue might be related to the #collect project.

[izarutskaya]

The added payment card is not displayed in production.

[blimpich]

Picking up at this is related to the subscription project.

[blimpich]

This is probably an internal issue. Going to label this as an internal hot pick for now.

It's possible that this is a frontend issue, haven't investigated enough to say for 100% sure.

[trjExpensify]

Looking at the steps:

OldDot:
Subscribe to Expensify.org on Workspaces page
Go to Settings>Account>Payments
Scroll down (you should see that payment failing)

... adding personal/corporate karma donations were out of scope of the project, so I wonder if we aren't getting updates for this failed billing scenario specifically or if it's paying your "normal" Expensify subscription. So it would be good to:

1. Test if Retry payment is missing for a subscription to Expensify NOT corporate/personal karma
2. If not, it's just related to corporate/personal karma donations, make that clearer in the issue.

CC: @MitchExpensify

[MitchExpensify]

1. I don't think we need to have a "Retry billing" banner for failed corporate karma payments in NewDot.
2. The failed July 5th payment looks to be on an individual subscription which could be a factor

I don't think we need to show individual subscription failed payment actions in NewDot do we?

[izarutskaya]

Both testing accounts are the owners of workspaces. Please check my videos. Thanks

Recording.2603.mp4

Recording.2601.mp4

[MitchExpensify]

Got it, the $4.99 charge is for an individual subscription so I don't think there is a bug here as nothing I can see related to a group workspace