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.