Remove LNURL-Pay from the checkout page

Describe the bug LNURL-pay doesn’t really make sense on the checkout page and should only be used for offline pos. Too many options in the checkout are confusing for users.

To Reproduce the bug Steps to reproduce the reported bug:

1. Go to ‘…’
2. Click on ‘…’
3. Scroll down to ‘…’
4. See error

Expected behavior

Screenshots

Your BTCPay Environment (please complete the following information):

• BTCPay Server Version:
• Deployment Method:
• Browser:

Logs (if applicable)

Setup Parameters

Additional context

[Kukks]

Good point. Haven’t thought about this. Only activate when amount is 0? It’s just weird to have several “bitcoin” options?

This is the default behavior afaik

Checked, it is not. We should change it then.

I propose:

• we enable lnurl by default when LN is configured
• NOT enable lnurl when invoice is not a topup invoice as a default
• We make “Only enable the payment method after user explicitly chooses it” on by default

[Kukks]

NACK, LNURL Pay is the only option that works for topup invoices in conjunction with lightning.

Getting back to this, it seems that LNRURL isn’t the only option and that amountless invoices have been around for a while. It also seems that whatever security concerns were, they were addressed. We’d have to check this, but if correct, then LNURL-Pay can potentially be removed entirely from the checkout itself and be used for an offline PoS, exciting to see people using this feature already.

We would need to ensure that LN implementations have all included this alteration. Another drawback is potentially bad UX on wallets which will show a payment screen with “0 sats to pay and confirm”