Lots of 403 Errors

Hello @alexliii

The logs you are seeing on the PayPal developers side are not affecting the functionality of our plugin or the orders. This feature is only PayPal checking if the customer has got Reference Transactions active on their account. We used to display this as well in our plugin logs, but we have had complaints from merchants that this was not a desired situation, so we removed this log entry for our plugin logs since release 1.6.5.

This feature has no effect on the functioning of the plugin, and we currently do not see any reason for opening a case with PayPal to discuss this. Can you explain to us what the negative effect is of this showing up on the PayPal logs? Does it affect your site in any way? This request comes from PayPal, not the plugins, so it would not be solved on our side (the PayPal Payments plugin).

Let me know what your opinion is on this topic so we can decide how to proceed.

Kind regards,
Krystian

Hello @inpsydekrystian,

Let me know what your opinion is on this topic so we can decide how to proceed.

Thanks for reply.

if you are a store owner, you might know what we expect.

Checkout page is so fragile, and we always note that the customer checkout, and order received on Google GA4, but we actually did not received order, and there were even no failed order on Woocommerce, No failed email, no payment from customer. Sometimes, customer wrote us that they were charged, and we have to reply to them that we did not received the payment.

That is quite annoying and really awkwarded, right?

Again, the checkout page is fragile, and there might be following plugins used:

Cart flow plugin to improve checkout experience and upscale

abandoned cart plugin

Auto coupon plugin

checkout field editor plugin to dynamic change checkout fields

muticurreny switcher

multilanguage

chat support

Estimated delivery time and Google reviews baggage(please check this plugin at https://www.ads-software.com/plugins/wc-ship-est/, andhttps://support.google.com/merchants/answer/7105655?hl=en

Thank you page editor plugin

Well, maybe more:) or you might like to have a survey form to have poll to know how many plugins are used for checkout page on a site:)

So, straight forward, fast checkout, less potential conflicts and issues are expected for the PayPal Payment gateway

Otherwise, it is quite difficult to debug and find issue If there is any issues, right?

so, if I were your developer, I would provide separate option on woocommerce payment to enable PayPal standard, card payment, advanced payment, google pay, Apple, Pay later, …

But not mess them together into one complex interface and make things so complicated, so that we can optionally enable them one by one upon our needs.

time assumption and efficiency is quite important for us

I used woocommerce for five years, so I am still use it now, but most of sellers were gone to Shopify, that is true if you go to Facebook groups to have a chat.

Thanks

• This reply was modified 11 months, 3 weeks ago by alexliii.
• This reply was modified 11 months, 3 weeks ago by alexliii.
• This reply was modified 11 months, 3 weeks ago by alexliii.
• This reply was modified 11 months, 3 weeks ago by alexliii.
• This reply was modified 11 months, 3 weeks ago by alexliii.
• This reply was modified 11 months, 3 weeks ago by alexliii.

Hello @alexliii

Regarding your initial issues. In theory, the plugin performs these API calls check once every 30 days. I didn’t notice it at first, but with this number of errors, it looks like the transient is being called too often. I would point to a caching problem, recommending temporarily disabling any caching plugins to see if the problem persists.

Checkout page is so fragile, and we always note that the customer checkout, and order received on Google GA4, but we actually did not received order, and there were even no failed order on Woocommerce, No failed email, no payment from customer. Sometimes, customer wrote us that they were charged, and we have to reply to them that we did not received the payment.

I understand your observations and it’s a common problem, but I don’t fully understand how it relates to the issue you brought up in this thread?

so, if I were your developer, I would provide separate option on woocommerce payment to enable PayPal standard, card payment, advanced payment, google pay, Apple, Pay later, …

But not mess them together into one complex interface and make things so complicated, so that we can optionally enable them one by one upon our needs.

It’s important to consider that payment plugins typically offer their features as an all-in-one package rather than as separate modules. This approach is quite common in the WP environment.

Additionally, as an official integration of PayPal, we are required to include all features in the plugin. These features are activated based on the user’s eligibility and compliance with PayPal’s policies.

Kind regards,
Krystian

• This reply was modified 11 months, 3 weeks ago by Krystian from Syde.

It’s important to consider that payment plugins typically offer their features as an all-in-one package rather than as separate modules. This approach is quite common in the WP environment. 

Additionally, as an official integration of PayPal, we are required to include all features in the plugin. These features are activated based on the user’s eligibility and compliance with PayPal’s policies.

You can merge all features into one plugin, still it should support enabling each payment individually on Woocommerce payment settings page, like Google pay, Apple Pay, card payment, PayPal.

• This reply was modified 11 months, 3 weeks ago by alexliii.

You can merge all features into one plugin, still it should support enabling each payment individually on Woocommerce payment settings page, like Google pay, Apple Pay, card payment, PayPal.

Implementing such a change might not be widely favored among other users. A significant part of this concern is due to the potential confusion it could create in managing the plugin. Many users are accustomed to the existing format of plugin operation, and a drastic change might lead to some complications.

I will bring up this topic as user feedback in our weekly team meeting. However, I must mention that I cannot promise any specific outcome at this moment.

Kind regards,
Krystian

• This reply was modified 11 months, 3 weeks ago by Krystian from Syde.
• This reply was modified 11 months, 3 weeks ago by Krystian from Syde.
• This reply was modified 11 months, 3 weeks ago by Krystian from Syde.