Laeserin on Nostr: Just put it on my #NostrPass 💳 https://i.nostr.build/huYFtc3pAT7Acma4.jpg ...

Just put it on my #NostrPass 💳

quoting nevent1q…4d5v

Payment preferences are an aspect that hasn't been fully addressed in the current specification. The only payment fields described are in NIP-57 and they are lud16 and lud06, which are suitable for zaps but quite limited in scope. Users should have the ability to set different payment options for various methods such as on-chain, BOLT12, or any others. It would also be convenient to express payment preferences for specific use cases. For example, for zaps, users could choose between NIP-57 zaps, NIP-61 nutzaps, or alternative methods like BOLT12. For e-commerce, they might prefer on-chain transactions, a different BOLT12 offer, or any other method.

We were drafting a similar concept for the NIP-99 extension for e-commerce. In this draft, we proposed including a field in the kind 0 event called `payment_preference` where users/merchants can define how they want to receive payments.