We are a new Billwerk customer and have no webhooks in our Billwerk account dashboard yet. Once, we configure our private keys in the WC-plugin, the required webhooks are automatically created and we receive the message "WebHook has been successfully created/updated yada yada".
And even though the webhook is in fact created, it lacks proper event configuration. In our case, the only enabled invoice event was "invoice_authorized". Not enabling at least "invoice__settled", too, renders the entire order status sync feature broken, because WC doesn't even receive the necessary events to update the order status in WC. I have battled this with the ReePay support team for over a week now, without them noticing the actual problem (lack of enabled events in the WebHook config), either. And I'm not sure that I (==noob merchant) can be expected to figure this out on my own... but here we go :-)
I'm not sure, this is bug in the plugin per se. It might as well be a problem in Billwerks backend. But the WC-plugin said "WebHook has been successfully created/updated yada yada", when that was only half of the full picture.
We are a new Billwerk customer and have no webhooks in our Billwerk account dashboard yet. Once, we configure our private keys in the WC-plugin, the required webhooks are automatically created and we receive the message "WebHook has been successfully created/updated yada yada".
And even though the webhook is in fact created, it lacks proper event configuration. In our case, the only enabled invoice event was "invoice_authorized". Not enabling at least "invoice__settled", too, renders the entire order status sync feature broken, because WC doesn't even receive the necessary events to update the order status in WC. I have battled this with the ReePay support team for over a week now, without them noticing the actual problem (lack of enabled events in the WebHook config), either. And I'm not sure that I (==noob merchant) can be expected to figure this out on my own... but here we go :-)
I'm not sure, this is bug in the plugin per se. It might as well be a problem in Billwerks backend. But the WC-plugin said "WebHook has been successfully created/updated yada yada", when that was only half of the full picture.