ndeet

After some discussion with @dennisreimann it seems this is a bug (although an edge case): - the `paymentMethods` parameter on the API is required - when passing `paymentMethods` but with...

@NicolasDorier I think this is the same you already fixed for invoice refunds [here](https://github.com/btcpayserver/btcpayserver/commit/7b6a115adc816ffe387290ddb99eeae359896be3) which sets all payment methods if none is passed. Can we have that for pull payments...

@NicolasDorier can confirm this was fixed with 2.0, thank you.

I tried to reproduce and can confirm there is a problem. Tried replacing existing wallet and creating a new store, both times same error. Following setup, mainnet 2of3 multisig software...

> I should remove the payoutMethodId property from refund, and instead have optional payoutMethods like the pull payment endpoint. not sure if we should do breaking changes on the API...

Hey, sorry for the late review and thanks for your contribution. This example is better to be fit into the existing [examples/get_invoice.php](https://github.com/btcpayserver/btcpayserver-greenfield-php/blob/v2.8.1/examples/get_invoice.php#L35) file, see the other examples. All it does...

Thank you very much, one last thing would be to move it into the existing examples/get_invoice.php file and refactor the code to match the other examples there.

Hey Julien, you are not really receiving the orderID but instead use the orderID as a filter to return invoices with that orderID(s) assigned. You are using the invoice client...

I agree the case of "Create a new wallet" -> "watch-only wallet", we should have a way to disable that functionality. I never used that feature tbh as I either...

Hi, where did you see the "no post data" in the logs? From your webserver access logs it seems to be GET requests which can't contain any data and would...