Yes, but I think a it should consider different options, not just lightning, so you create different list for every payment method? I remember nostr:nprofile1qqspdudqzqx5ellme3prp68qus5se3vynsddcexkv5la5p7qxxcswjcaxd3rp porpusing something using "w" tags in type 0, it was an interesting approach, but couldn't find the related conversation, maybe he can share some thoughts on this.

This could be an option, then we can have different labels for different methods, lets say lud16, bolt12, cashureq, btc, all of these are arrays that clients can iterate on to find a working payment option.