Standard Woocommerce button not working as expected

Hi @cutu234

You already have the following support thead open where you are asking pretty much the same thing. Please don’t create multiple support threads for the same topic as it just slows us down.

1. Customer data are not filled in by PayPal. That’s bad user experience.

That’s because it’s a redirect based solution where population of the checkout fields isn’t possible. Your customer needs to enter their address info on the checkout page when using this option. We can’t change that, it’s just how PayPal works.

2. The redirection takes sometime really long (up to 1 minute), so that we had too many orders that were not completed.

I already shared a test site in the other support thread where you can see the redirection is not slow. Your issue is likely specific to your site since we don’t receive other reports of a slow redirect to PayPal or from PayPal to your site. I will review your linked staging site.

The confirmation email is sent before the payment was processed. Some customers canceled the order. They thought they had already paid for it.

What order status is your confirmation email being sent on? The PayPal plugin does not call the WC_Order::payment_complete() method until after the payment is processed. That WooCommerce method is how the order’s status gets updated after a successful payment. We don’t observer any difference with emails when using the redirect based flow.

Kind Regards

Update: I tested your site and the redirect flow did not take more than a few seconds from start to finish.

Order #581418

I can provide screen captures with timestamps showing how quick it is if that’s necessary.

Kind Regards

Sorry for posting a duplicate. It was not my intention to make your life harder. I just lost track of my support threads.

Now, let’s set the minor issues aside. My main question is: Why is the process not the same (in our case) whether I use the PayPal or the standard Woocommerce button?

In our case, it is clearly the Woocommerce button, since the confirmation email is immediately sent, and PayPal is not loaeded in an iframe.

I probably miss something in the settings. I simply don’t know what. How would we change this?

Why is the process not the same (in our case) whether I use the PayPal or the standard Woocommerce button?

Because one implementation is a redirect and the other uses the PayPal wallet without a redirect. They exist to fulfill different needs that merchants have.

In our case, it is clearly the Woocommerce button, since the confirmation email is immediately sent

Can you elaborate on what you mean here? WooCommerce sends emails whenever the order status changes. The PayPal plugin doesn’t change the order status unless one of the following happens:

1. The payment fails, so the order’s status is set to failed and a note is added to the order.
2. The payment is authorized but not captured, so the plugin sets the order’s status to on-hold.
3. The payment is captured, so the plugin calls WC_Order::payment_complete() which results in WooCommerce setting a status of processing or completed.

Kind Regards

Thank you very much. This is probably a misunderstanding. I referred to this post where you said:

The same code is called whether you’re using the standard button or the PayPal button.

This is obviously not the case. However, it might depend on what you meant by “code”.

To simplify things: Is it the standard and intended behaviour that both methods do NOT work the same way? In this case, everything is just fine.

In our case it was a huge difference. Please, have a look at this chart. After changing from the Woocommerce to the PayPal button, pending orders dropped from up to 8 % to literally 0 %:

We didn’t anything else.

It might be a good idea to add some information to the tooltip on the settings page. How would I know as a user that both methods are different? In my case, I just didn’t even tested the PayPal button, since I preferred the standard Woocommerce button. So, I didn’t even know that the PayPal button calls the process in an iframe.

Don’t get me wrong. I appreciate your great work. But these small details can save the user (and you!) a lot of work.

Thank you very much!

• This reply was modified 1 year ago by cutu234.
• This reply was modified 1 year ago by cutu234.

This is obviously not the case.?

You’re welcome to review the code and confirm for yourself that the same code within the plugin is indeed called for both scenarios. The code is publicly available. The only difference is when the code is called, because one option redirects the customer to the PayPal page and the other opens the PayPal wallet.

Is it the standard and intended behaviour that both methods do NOT work the same way?

It’s just the checkout flow that’s different. Under the hood they work the same when it comes to processing the payment etc.

How would I know as a user that both methods are different?

Most merchants test functionality on their site before enabling on a live site. I’ve made a note to include addition info in the tooltip to make it more clear.

Kind Regards

Thank you very much. I don’t want to split hairs about “code”. As a user, I simply couldn’t know that one method calls an iframe, while the other triggers a redirect.

Most merchants test functionality on their site before enabling on a live site.

Well, I’m one of those merchants! ?? But why would I test the PayPal button, if I clearly prefer the standard button and do not know that these methods do not work the same? There’s simply no reason to do that. I hope, you get my point.

Anyway, I’m glad that everything works perfectly fine. And I’m very grateful for your good work and support.