Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Woo POS] Make Cash Payment independent from card payment events #15240

Open
staskus opened this issue Feb 21, 2025 · 1 comment
Open

[Woo POS] Make Cash Payment independent from card payment events #15240

staskus opened this issue Feb 21, 2025 · 1 comment
Labels
feature: POS priority: medium Planned tasks usually belonging to ongoing projects type: task An internally driven task.

Comments

@staskus
Copy link
Contributor

staskus commented Feb 21, 2025 •
edited
Loading

Issues such as #15233 have demonstrated that an unexpected event coming from CardPresentPaymentService could close or affect Cash Payment view in an unexpected way.

As discussed in the thread p1740129279262259-slack-C070SJRA8DP, we should handle both cash and card payment states separately, so we can handle all the scenarios as we need to. It may also allow opening Cash Payment view without delay since it wouldn't require waiting for payment cancellation.
@staskus staskus added type: task An internally driven task. feature: POS labels Feb 21, 2025
@dangermattic
Copy link
Collaborator

dangermattic commented Feb 21, 2025 •
edited
Loading

Thanks for reporting! 👍

@staskus staskus added type: bug A confirmed bug. priority: medium Planned tasks usually belonging to ongoing projects type: task An internally driven task. and removed type: task An internally driven task. type: bug A confirmed bug. labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature: POS priority: medium Planned tasks usually belonging to ongoing projects type: task An internally driven task.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@staskus @dangermattic