Ok, to see if I understand:
The payment method is set by the Blesta button, so that the BTCPay invoice generated requires payment via that method.
BTCPay supports (Bitcoin or Lightning, or any of the 4 you mentioned) as returned.
You said:
But it appears that it may also be possible for us to allow the payment method (From the 4 mentioned) to be set in the gateway configuration in Blesta) so that the payment button generates a BTCPay invoice in the desired method. Or, we can simply remove the option and allow the client to select it.
What path would you recommend?
Allow the payment method (of the 4 options) to be set in the gateway config in Blesta, so that the button specifies that method when a BTCPay invoice is created.
Or, comment out the line so that the client is presented with the options?
Curious what you think is the best way to go. Do you think admins want to force the client to pay with Lightning or BTC on the gateway config level, or let the client choose? I assume that the client will only be able to choose from methods that have been configured in BTCPay Server? So if BTC is the only option, then only it will appear.