Hm that’s weird. I tried with nostr:npub1w27mc4aa6m0ufe3xs5z3m6qyr52gc0rglept7vqlwx4xeaf72tasnqz70r and nostr:npub1cm3rpgj7457yjuqnvdalxaauakqu0ndkpkyp5cldkyutpz4xszpsmk96wt too and got the same result — only saw the description on the receiver side.
https://blitz-wallet.com/.well-known/lnurlp/bullish?amount=1000&comment=hi
Yeah, LNURL doesn’t specify to save the comment in the invoice. See https://github.com/lnurl/luds/blob/luds/12.md
But we do it when we can to give more context to the payment
I’m just trying to understand why the invoice that’s created this way (via NWC):
```
const response = await client.makeInvoice({1000, description: "hi"});
```
Allows me to see the description when paying the invoice, but the one that’s created this way does not.
```
const invoice = await ln.requestInvoice({ satoshi: 1000, comment: “hi”});
```
This second method is what I’m using to implement payment for an e-commerce website. Not too much of an issue, but it would be nice if the customer could see the description (e.g. “Order #21shss”) when paying the invoice.
Ah, we check the description hash first rather than the description. Would you like to do a PR to fix the check? https://github.com/getAlby/hub/blob/master/lnclient/phoenixd/phoenixd.go#L286
