Paul Dechov

Hi,

Thanks for calling this out, and we’ll consider whether to remove it to avoid possible confusion.

The suggested code snippet is for a different extension, but should work if the filter name is replaced with ‘wcpay_payment_request_total_label_suffix’ – hope that helps.

Paul

Hi @morningstardesign,

Thank you for the feature request. There is CSV download functionality for the Transactions screen but not yet the Deposits screen. We are now tracking this in https://github.com/Automattic/woocommerce-payments/issues/2548

Cheers,

Paul

Hi,

We’ve identified a recent change in the 2.7.0 release that might be related but are still looking into what the cause here could be.

@tpzwoods Are you using the same WP admin user on both devices?

Hi @umutusu,

We were unable to reproduce the issue on our end, but the latest release (4.5.5) features a change that has been confirmed to fix the error. Thank you for reporting, apologies for the trouble, and do let us know if you’re still seeing an issue.

Regards,

Paul

Hi all,

We have determined that the conditions being reported do not constitute an exploit in the PayPal Checkout extension for WooCommerce. While it is true that the amount can be manipulated in the PayPal payment flow, this amount is validated against the WooCommerce order total before completing the order, and if it doesn’t match then the order will be left in an “On Hold” state. (In cases when the order is completed upon API payment request rather than IPN, the amount comes directly from the order, not a previous PayPal response.)

If we were to receive exploit steps that result in a completed WooCommerce order with a lower payment amount (can be reported here), we would act promptly to address the issue.

Thank you,

Paul

Jim,

Can you verify that “Enable automated taxes” is currently selected (at the top of WooCommerce ? Settings ? Tax ? Tax options)? If you remove the NY row from the “Standard rates” table, does that change the rate you see on checkout?

Paul

P.S. It doesn’t matter but just a note that I’m seeing 10603 as 7.375% as well.

Hi Jim,

You are expecting different tax rates depending on the customer’s New York State ZIP code, is that correct?

In that case, can you give one or more examples of a destination ZIP code for which you’re seeing a returned rate that differs from what you expect?
Here is a table of rates per locality, along with some other information on New York State taxes in case it’s helpful.

Paul

Hi zokkoz,

Thank you for reporting – this issue was due to an incompatibility with an update to PayPal’s checkout.js library.

Please update to version 1.6.9, which contains a fix.

Paul

Hi,

Thank you all for your patience, and for reporting and offering workarounds. Version 1.6.9 is now released with the fix described by @terminator_5505.

We will see what we can do to prevent breakage due to incompatibility with latest changes in the remote library (PayPal’s checkout.js in this case) in the future.

Regards,

Paul

Hi @k15lmk98,

The checkout form fields – including “Terms and Conditions” – are now properly validated upon opening the payment flow, as of the 1.6.4 release.

Regards,

Paul

Hi @blackstorm2014,

The store checkout information is now passed to PayPal to pre-fill the form on their end, as of version 1.6.4.

Regards,

Paul

Hi DarrenMooney,

Just wanted to let you know this issue should be fixed in the latest release.

Regards,

Paul

Hi emikim,

Thank you for reporting these behaviors.

We have released version 1.6.1 today, which may fix the PayPal window closing immediately, a bug we’ve seen across browsers but only after clearing the cache / in cases where a WooCommerce cart session has not yet been created. The redirection to an empty cart could be related, though we have not yet been able to reproduce this.

Would you be able to confirm whether these issues have been alleviated in the latest release?

Thank you,

Paul

Hi simonduchaine,

Thank you for your feedback. The “PayPal” logo was being omitted in horizontal layout when the primary “PayPal Checkout” button was the only button that appeared. This has been fixed in 1.6.1.

Regards,

Paul

Thanks all for reporting this. It should be fixed in 1.6.1.

Regards,

Paul