Hmm, that could be one way. But I think it’s preferable if the nostr client when calling pay_invoice includes the zap info in a metadata field.
I think Damus already implemented it: https://github.com/nostr-protocol/nips/issues/1843
nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p nostr:npub1zk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q0gl6ef Are you aware of any NWC services which, in the `list_transactions`, properly provide the necessary attribution data for OUTBOUND zaps? Our service provides attribution for INBOUND zaps -- this is trivial, since we already have the data... we have the data because we generated the zap receipt! See below screenshot... this is the Rizful "list_transactions" data shown in Damus. You can see we have the INBOUND data but not the OUTBOUND data.
... So: for OUTBOUND zaps, we don't have the zap receipt, so we'd need to do some custom listening to relays for zap receipts for our users, and then add that to the "metadata" field in the "transactions_list"..... right? Or am I overcomplicating this?
