Clayton R

If those are empty or not yet set, the result is $0.

They can’t be empty because if they were, the class-wc-checkout.php file from core WooCommerce would trigger a validation error. WooCommerce validates that all required fields have a value; if they don’t then WooCommerce shows a notice on the checkout page. The order can’t be processed unless all required fields pass validation. As you confirmed, the WooCommerce order has the correct address info, which is why the order was allowed to have the payment processed.

customer clicks the PayPal button on the cart or product page and completes payment on PayPal’s side before reaching the WC checkout form

No, that is not correct. The payment is processed using the standard WooCommerce flow.

the customer’s address comes from PayPal’s API response

That is not correct. The address does not come from PayPal since you confirmed you have the Disable PayPal Shipping Address option enabled.

That difference in behavior points directly at the Express flow — which is your plugin’s code

You stated in your original post that this was not the express checkout flow. Here is a direct quote:

Place Order button (not Express Checkout)

Can you show where in your plugin’s execution order the customer tax address is set relative to

I can explain to you how it works.

1. The customer clicks the PayPal button.
2. A request is made to the WordPress API which routes to the CartOrder class.
3. The customer’s address info is updated, using the checkout form data.
4. The PayPal order is created and the response contains the PayPal order ID
5. The PayPal wallet opens and the customer then makes their payment method selection.
6. The customer clicks the “Complete payment” button in the PayPal wallet.
7. Control is returned to the PayPal plugin and the checkout form is submitted.
8. WooCommerce updates the customer object using the checkout form data. https://plugins.trac.ww.wp.xz.cn/browser/woocommerce/tags/10.7.0/includes/class-wc-checkout.php#L1310
9. WooCommerce triggers the cart calculation.
10. WooCommerce validates all of the checkout form data and if any required fields are missing, the process is exited and a notice is shown on the checkout page. It’s impossible that the address info is empty because if it was the validation here would fail.
11. No validation errors so WooCommerce creates the WooCommerce order and populates the address info using the checkout form data. As you confirmed, the order’s address info is correct and it comes directly from the form data.
12. WooCommerce tells the PayPal plugin to process the payment.

There is no part of that process where the PayPal plugin is manipulating the order address info, the order totals, or the cart totals.

Hi @joyryde

When the PayPal button is clicked, your plugin makes a POST to its REST route (cart/order) to create the PayPal order object before WooCommerce creates the WC order.

That’s not a bug, it’s designed that way. You must create a PayPal order ID when the PayPal button is clicked, because that’s how PayPal works. PayPal requires that the button click callback returns a PayPal order ID.

but the shipping address from the checkout form has not yet been fully committed to the WC customer/session at the point your REST handler runs.

WooCommerce updates the session when the customer enters their address info via the update_checkout event that triggers an ajax request. If the address is incomplete, there will be a validation error when you click the PayPal button.

You should have the Validate Checkout Fields option enabled since you are not relying on PayPal to provide the customer’s shipping address info. https://paymentplugins.com/documentation/paypal/advanced-settings/#validate-checkout-fields

The fact that the WooCommerce order has a tax value of $0 wouldn’t be related to the PayPal plugin because it doesn’t interact with the order creation logic.

The bug appears intermittent because it depends on the exact timing of when the customer’s address data is flushed to the WC session relative to when the REST request hits CartOrder::handle_post_request()

That code doesn’t create the WooCommerce order though. The WooCommerce order is created during the checkout flow after all required fields have been validated by Woo. If an address is incomplete, it would result in a notice showing on the checkout page. The PayPal plugin doesn’t create WooCommerce orders so it wouldn’t have anything to do with a $0 tax calculation.

Anything in CartOrder like WC()->cart->calculate_totals() has no bearing on the order creation which occurs later after the checkout form is submitted. During the checkout process, WooCommerce re-calculates the cart totals, using the checkout form data that was already entered by your customer.

Kind Regards

Hi @karlob

We encountered the same issue when trying to process refunds via the WooCommerce mobile app.

Can you share the error log? The AjaxFrontendHandler is not involved in the refund process so I’d like to review the error log.

That code has been in place since nearly the first release of this plugin several years ago so it’s odd that errors would just now start triggering for you.

You can reach out via the support widget via the WordPress Admin > WooCommerce > PayPal > Support page and we can share the next release.

Kind Regards

Hi @adampaine

Thank you for contacting Payment Plugins. This is an interesting concept to use Stripe’s merchant of record functionality within a WooCommerce store. I’ve forward this on to Stripe’s internal team so they can shed some light on what something like that could look like.

Kind Regards,

Hi @karlob

In the next release, we’re going to be deprecating the AjaxFrontendHandler class where that error occurred because it’s no longer needed.

Kind Regards

Hi @barnabas1

Thank you for contacting Payment Plugins. Let me have the code for the predictive address search functionality reviewed so I can confirm if it’s possible to build that into the Stripe plugin.

It seems to me that this feature should be available through core rather than a payment solution since a merchant is likely to offer other payment gateways like PayPal, Square, etc.

Kind Regards

Hi @devtestconcise

Thank you for contacting Payment Plugins. Can you confirm that you’re using our plugin, which is called “Payment Plugins for Stripe WooCommerce”? There is another plugin called “WooCommerce Stripe Payment Gateway” so I wanted to confirm that you are using our plugin.

Kind Regards