-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] Wallet - Deactivated card is not removed from Wallet when it is deactivated in Wallet page #52953
Comments
Triggered auto assignment to @abekkala ( |
@abekkala Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Job added to Upwork: https://www.upwork.com/jobs/~021861531007632186016 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
Still looking for proposals |
How a contributor outside US can reproduce this issue by adding a bank account and virtual card? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Hi, I'm Nicolay from Callstack - expert contributor group - and I would like to work on this issue. |
What findings: The same flow in removing card directly inside workspace - is working fine: @muttmuure we need some from BE side to check - why we get a new card aflter |
@abekkala Can you please add the |
Oh yeah, internal doesn't auto assign an engineer |
Triggered auto assignment to @lakchote ( |
|
We create a replacement card after |
@lakchote, So it's expected that the card is not removed when deactivated? |
What is expected is to have the card being replaced with the same values if it's an admin issued virtual card. That's what happened in the logs: So I'm not sure this issue is actually relevant? cc @MariaHCD since you've authored the code relevant to the replacement |
When a user reports fraud or that their virtual card is stolen, we deactivate the current one and re-issue a new one in its place. The new card will have the same configuration as the deactivated card such as card title, limit, etc. The card numbers will be different for the new card, however. So it seems like we need to make it more in the UI/UX that a new card has been issued |
@abekkala @lakchote @narefyev91 @fedirjh this issue is now 4 weeks old, please consider:
Thanks! |
@abekkala, @lakchote, @narefyev91, @fedirjh Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@abekkala, @lakchote, @narefyev91, @fedirjh 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@MariaHCD Should we update the UI and add a little badge cc @Expensify/design |
@shawnborton We have this message . Then we automatically reissue a new card. |
If we automatically reissue a new card, why do we show a blank page like this: Instead of just repopulating the page with the new details like this: I'm not too familiar with the card flows though so perhaps I am not understanding correctly. cc @MariaHCD @joekaufmanexpensify for more thoughts |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.65-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5250081
Email or phone of affected tester (no customers): applausetester [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Expected Result:
After the card is deactivated in Wallet, it should be removed in Wallet.
Actual Result:
After the card is deactivated in Wallet, it reappears.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6672815_1732265618675.20241122_164451.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @fedirjhThe text was updated successfully, but these errors were encountered: