Closed lmeyer1 closed 2 years ago
@theodorspringwallee Sorry to say, we had to leave your product and Postfinance altogether. I was chasing after you from december 2021 until this summer. I lost hundreds of hours trying to debug your mess and trying to get feedback form the support. We had even a video meeting with PF and one of your collegue. There we understood, that your company is not providing a serious collaboration, but is just leading everyone astray, trying to gain some time and money without working. I never saw something like that.
Don't take it personnaly, it's perhaps not your fault, but wallee is just sucking !!!!
@theodorspringwallee
You closed this issue as Fixed
, what is not true. It would have been more honest to close it as Won't fix
, wouldn't it ?
Describe the bug The webhook URL created by the module always uses the URL of the
shop #1
. In a multishop environment, when Postfinance Checkout is installed in any other shop, the webhook URL will point to theshop #1
, and thus the payment process will not work. When Postfinance's servers make their request to the webhook URL, an error 500 is returned, and thus the payment does not succeed.To Reproduce Steps to reproduce the behavior:
example.net
)https://example.com/module/postfinancecheckout/webhook
, the URL ofshop #1
. The webhook should of course use the domain of the shop where Postfinance Checkout Flex is configured.Expected behavior I expect the Postfinance Checkout module pfpayment to work for every shop in a multishop installation, not only shop 1.
Software versions (please complete the following information):