Andrew Camilleri

Look at our lightning charge support. You only implement what is available, and you only really need support for creating an invoice, checking if a specific invoice has been paid,...

This is indeed problematic. I think we need to rethink this. The main problem is that the export is not of invoices, but of payments, so refunds may not entirely...

> Marking for closing, as sadly, this problem is out of our control. We should probably not be using `Map` and use https://github.com/btcpayserver/btcTransmuter/blob/master/BtcTransmuter/Startup.cs#L186 instead

@ketominer Would you be willing to do some of the testing for this if I did a PR?

> @Kukks I agree on a global approach for rates. But I think this should be kept separate matter than Blazor. Having a global approach to get the rate, would...

Repro steps: *enable at least one payment method * Create invoice of 0 amount * Go to checkout URL * 500 error

We should remove the refund option from the UI potentially. The issue is when you forcefully go to the checkout url. (imagine cresting the invoice through api and using the...

With that amount of data, it would make more sense to add it to `posData` when submitting it

This is because LNURL is a "lazy" payment method, where it does not need the bitcoin/lightning node on invoice creation but only once it is shown. Realistically, we should check...

I will make lnurl not activate if node is down I guess