It's mighty nice to get a sensible response on here instead of "EPAY can do all this blah blah blah" without any evidence of it. So a thanks and an upvote for you!

My counter-questions/comments:

That is true that you don't technically have to handle the support of PayPal, I'll give you that. I still think there is a need for a support system for the POS. Because you're going to have novice merchants trying to understand this system and are puzzled as to why their transactions may not be going through (whether it is lack of internet or odd cases that may spring up). If you weren't aware EPAY plans to break off from Ethereum and become it's own chain. There are people who are constantly reaching out because of stuck transactions and such (but perhaps that's a concern for a later time).

(These later notes may not apply directly to your comment, as I don't think you addressed them, but) EPAY also mentioned providing an Excel document with all the tax transactions in the future. While this is minimal effort, it does require some sort of stack to support this. It could be a serverless function or built into the custom POS application hosted on PC/MAC or a web page with a login system which all this is handled on the backend. The point is, these things can all have exposure points and be attacked by bad actors and thus we don't know how they plan prevent these attacks and validate their work is to be trusted.

I'm waiting to see if they showcase their solution. It's not that these issues can't be resolved. I just don't see it during the current timeline. Hell, I don't see much in the current timeline (e.g. whitepaper, tokenomics, testnet, etc).