Opayo Plugin Deprecation

I’ve gone through the https://mailchi.mp/ebizmarts/action-required-opayo-pci-4-csp-mandatory-update-march-2025?e=%5BUNIQID%5D and found that all mentioned about Magento extension nothing about wordpress

I’ve also searched for latest version of opayo
”WooCommerce Opayo Payment Suite” plugin but found that it is now deperecated
https://woocommerce.com/document/sagepay-form/

Above they asking for switch to
https://woocommerce.com/products/elavon-payments/
Jus correct above sentence

I reviewed the information, and it appears that the **"WooCommerce Opayo Payment Suite"** plugin has been deprecated. The documentation suggests switching to **[Elavon Payments](https://woocommerce.com/products/elavon-payments/)** as an alternative solution.

Additionally, the **Opayo PCI 4 CSP mandatory update** primarily focuses on the Magento extension, with no direct mention of WordPress-related solutions.

I’ve gone through the https://mailchi.mp/ebizmarts/action-required-opayo-pci-4-csp-mandatory-update-march-2025?e=%5BUNIQID%5D and found that all mentioned about Magento extension nothing about wordpress

I’ve reviewed the information from [this link](https://mailchi.mp/ebizmarts/action-required-opayo-pci-4-csp-mandatory-update-march-2025?e=%5BUNIQID%5D) and found that it only mentions updates related to the **Magento extension**, with no reference to WordPress.

I’ve also searched for latest version of opayo
”WooCommerce Opayo Payment Suite” plugin but found that it is now deperecated

I also searched for the latest version of the **"WooCommerce Opayo Payment Suite"** plugin and found that it has now been **deprecated**.

Above they asking for switch to

The documentation suggests switching to **[Elavon Payments](https://woocommerce.com/products/elavon-payments/)** as an alternative solution.

Regarding this order I found that query has failed due it has single quote in their name “Tracy O'Hare”, But now this case is also fixed

The query failure occurred due to a **single quote (')** in the name **"Tracy O'Hare"**, which likely caused a syntax issue in the SQL statement. However, this issue has now been **fixed**, presumably by properly escaping or handling special characters in the query.

on above order cron was not applied it may due to yesterday we have received so many spam orders during that time , may be server load cause the issue, but currently it is working fine
Just correct above

The cron job was not applied to the above order, possibly due to a high server load caused by a large number of spam orders received yesterday. However, it is currently working fine.