You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get an error when I try to refund an order in WooCommerce that was paid using BTCPay. This only happens when I click 'Refund $... via BTCPay'. The error is below.
How did you encounter this bug?
I enter the refund information in WooCommerce. 2. I click on 'Refund $... via BTCPay. 3. I get the error message that is pasted below.
Relevant log output
Exception creating pull payment: Error during POST to https://example.com/api/v1/stores/6BSKiz4zRqydQXtaYo1jj3MLDgLdqC3ZjtEhR5YqU5Bt/pull-payments. Got response (422): [{"path":"PaymentMethods[1]","message":"Invalid or unsupported payment method"}]
What browser do you use?
Firefox 132.0.1
Additional information
No response
Are you sure this is a bug report?
I confirm this is a bug report
The text was updated successfully, but these errors were encountered:
Hey @JCZwier tried to reproduce the error and found a different one but with BTCPay Server 2.0.
With BTCPay 1.13.x (which you seem to use) I could not reproduce your error. Your errors suggests that the payment methods passed to the pull payments endpoint is a nested array which is a bit weird. Can you give me more information about your setup so I can try to reproduce?
What PHP version do you use?
What settings do you have enabled on BTCPay Settings (on WooCommerce)
What BTCPay Server version are you running?
did you disable the original Payment method maybe? (in WooCommerce -> Settings -> Payments)?
What is your BTCPay version?
I'm running BTCPay v1.13.7+83c948d12 (Altcoins)
How did you deploy BTCPay Server?
I'm running BTCPay Server on a Docker instance
What happened?
I get an error when I try to refund an order in WooCommerce that was paid using BTCPay. This only happens when I click 'Refund $... via BTCPay'. The error is below.
How did you encounter this bug?
Relevant log output
What browser do you use?
Firefox 132.0.1
Additional information
No response
Are you sure this is a bug report?
The text was updated successfully, but these errors were encountered: