Here's a little article about payment codes.
However BIP47 seems to require an additional "notification transaction" (@RGBkey already mentioned "cost and time", although I think it should be possible to automate everything) so the fee would be doubled. It's one per customer, so it would be fine if you re-visit the store or restaurant every now and then, but not if it's an one-time payment.
Yeah, there's a few reasons BIP 47 didn't take off. Clever idea, but not really useful enough given the trade offs.
Couldn't this (a static payment identifier for face to face businesses) be done using a Lightning network node name? I think so. Much more appropriate for this use case in other ways too.
Here's a little article about payment codes.
However BIP47 seems to require an additional "notification transaction" (@RGBkey already mentioned "cost and time", although I think it should be possible to automate everything) so the fee would be doubled. It's one per customer, so it would be fine if you re-visit the store or restaurant every now and then, but not if it's an one-time payment.
I don't know if stealth addresses had this problem, too. And don't ask me about LN compatibility ...
Using the lightning network, you could generate new payment request QRs for each payment and keep privacy, but it would require users being able to use the LN.