xaim
Forum Replies Created
-
Hello, I wanted to follow-up on this support item. The issue was resolved.
It ended up not being either the Payzen or WooCommerce plugins – they are both working correctly.
It appears to have been a corrupted Page. When I removed everything, cleared cache and optimized the database. Reinstalled the plugins, and ran a transaction, it worked just as it was meant to.
Sometimes, it’s the really simple things…Hello, I wanted to follow-up on this support item. The issue was resolved.
It ended up not being either the Payzen or WooCommerce plugins – they are both working correctly.
It appears to have been a corrupted Page. When I removed everything, cleared cache and optimized the database. Reinstalled the plugins, and ran a transaction, it worked just as it was meant to.
Sometimes, it’s the really simple things…Thank you, this is very helpful!
I’m using WooCommerce 10.3.6 (latest version) and PayZen WooCommerce plugin version 1.15.5 (latest version).
I’ve been trying to get the WooCommerce Checkout page/button to redirect to the Payzen back office to process the payment but it fails. It is not getting to the Payzen back office for payment.
Instead the checkout page redirects to the woocommerce ‘cart’ page, with a ‘page does not exist’ notification.
The error message indicates that authorization failed.
This is the error message:
Notice Authentication failed: received invalid response with parameters: Array ( [wc-api] => WC_Gateway_Payzen [woocommerce-login-nonce] => [_wpnonce] => [woocommerce-reset-password-nonce] => ) CONTEXT: {“_legacy”:true}The transaction is meant to go to the Payzen back office, execute and return to the shop with a success message using the IPN – Instant Payment Notification.
The configuration has been checked and the TEST & PRODUCTION keys are correct.
Payzen says the issue is with the WooCommerce Plugin.
Can you help fix this?
There is a bug here and Payzen support said that they cannot assist further.Hi, thanks for that – PHP 8.4 (latest stable version was released November 2024)
Hello, was this issue resolved?
Thanks