I haven't tested it out, but I think yes. It looks like it depends on the recipient's Lightning wallet.
And yes, it behaves exactly like in your example on your home page.
So the problem lies in the recipient's Lightning wallet?
OK, I think what you are talking about is that the recipient of your zap is not generating a "zap receipt" .. one of the most difficult and unreliable parts of the zap spec ( https://github.com/nostr-protocol/nips/blob/master/57.md ) ..... Can you tell me, are the failures "consistent per recipient"? You should find that there are some recipients who always produce zap receipts (you see the confirmation) and others that never produce zap receipts (you never see the confirmation). If you look at our home page rizful.com you can see an example of a user (Peter Todd) whose implementation is broken, his implementation doesn't produce zap receipts.
Discussion
Yes. This happens to be exactly what we are working on -- benchmarking wallet implementations and seeing where the problems are for zaps. The best way to receive zaps is with an always-on lighting node like Alby Cloud or Rizful.com -- yes, self-hosting is great for other reasons, but we are seeing a LOT of self-hosted nodes that fail to receive zaps, or take 10+ seconds to send zap receipts -- and lots of other problems.
That explains it. Thank you!