i can confirm that zaps are a pain in the butt. i have an open issue to make them better and more consistent. you're probably having one of several issues that seem to always reoccur. soon we'll get a template setup for zaps so this dosn't happen.

here are some issues that i've personally seen.

AI struggles to figure out how to properly implement zaps, struggling with kind:9734 (sending those to relays instead of the LNURL provider), publishing the kind:9735 zap receipt properly, the Lightning address endpoint request formatting, Zap amounts in milisats, Zap buttons using and detecting WebLN on desktop (Alby) and still sending attempting to execute the Lightning invoice even though WebLN is used. NWC struggles as well, trying to maintain the connection and re-establish the connection.