MultiSafepay

Hi @arture

We believe the issue has been resolved in version 6.12.0, which we’ve recently released.

The problem was related to the timing of payment method registration in WooCommerce Blocks – the default pre-selected payment method wasn’t being properly initialized before the checkout rendered.

Please update to version 6.12.0 and verify the fix works as expected. If you encounter any further issues, please feel free to reopen this ticket.

On behalf of the development team, we sincerely appreciate your efforts in reporting and helping us identify this problem. Thank you again for your patience and detailed feedback.

Hello @marketemprende

Thank you for confirming the latest changes mitigate and help reduce the CPU usage.

For the moment, I will close this ticket. However, you should know our plan is to continue improving and refactoring our plugin for better performance during the next days.

Once again, thank you for your report.

Hi @marketemprende

We are investigating your report now and will get back to you as soon as possible.

Thanks for your comment.

Hello @jicao

Our apologies, because this ticket was outside our radar for a long time.
Thank you for your report, we will look into this and get back to you with more information.

Hi @aristotle25

Is not the first time we heard about something like this. Let me give you some insights, so you can check this on your end.

• You just mentioned you are using Elementor; and most probably, using Elementor to customize the “Thank You” page from WooCommerce?
• We are going to redirect the user to the thank you page, provided by WooCommerce, following WooCommerce development guidelines for a Payment gateway plugin. For that purpose we are using the “get_checkout_order_received_url” here: https://github.com/MultiSafepay/woocommerce/blob/6.3.1/src/Services/OrderService.php#L125
• Consider the “get_checkout_order_received_url” is a WooCommerce method: https://woocommerce.github.io/code-reference/classes/WC-Order.html#method_get_checkout_order_received_url
• What we saw in the past, is that Elementor does not return the “customized thank you page”, in that property.
• If we are not wrong, about you using a custom thank you page created by Elementor, then you (or your developers) should be capable of solving this issue on your end, following one of the two options:
  
  ====

1. By contacting Elementor and informing them about this issue or bug.
2. Using the filter “woocommerce_get_checkout_order_received_url”, which WooCommerce provides via the following method considering this documentation, to some how fix the URL being returned. For that purpose consider these two URLs as references: 2.1. https://woocommerce.github.io/code-reference/files/woocommerce-includes-class-wc-order.html#source-view.1777 2.2. https://developer.wordpress.org/reference/functions/add_filter/
   
   
   ====
   
   Feel free to get back to us with more information if we are wrong about this probable cause; or to confirm this is actually what is happening in your application.

• This reply was modified 2 years, 1 month ago by MultiSafepay.

Hello @landreiziger

We didn’t receive any reply from you after our latest comment.

I`m closing this ticket due to inactivity, however, please reopen it if needed.

Thanks.

Hello @landreiziger.

Could you contact us through our support service to check this together with you: [email protected]

Hi @biancaakanaonda

Our apologies for a long time without providing an answer to your question. It`s just it was out of our radar.

Not sure to fully understand your question. Our plugin provides many payment options, and between them, there is one called “Card payment”; for which the logo matches debit and credit card payments icons.

Please, let me know if this is enough to meet your requirements.