Spike: Inconsistent tax behavior when using Express Checkout for virtual products

[gpressutto5]

Describe the bug

As noted in #7577 (comment), we have a fundamental problem calculating taxes for virtual products in Express Checkout. The problem happens because all the payment data is loaded when the page is rendered, so unless the customer is logged in, we have no data about their billing or shipping address. This data is only updated subsequently when we need to calculate the shipping fee, and since virtual products do not require shipping, the tax amount will not be updated.
In this issue we must look for a way to resolve this and calculate taxes correctly.
One idea I had is to always ask for a shipping address when using Apple Pay or Google Pay, even for products that don't require shipping.

The solution might be affected by #8297

To Reproduce

1. Go to the taxes settings and create different Taxes zones
2. On a new window, as a guest, clear all your cookies and local storage and use Apple Pay / Google Pay to pay for a virtual product
3. Experiment with different settings for "Calculate tax based on" (Customer shipping address / Customer billing address / Shop base address)

Actual behavior

Tax calculation is inconsistent

Screenshots

Apple Pay modal	Price changed after confirmed

From checkout select billing country US	See Apple Pay modal with US tax price	After confirming, it changed to Brazil because of the card

Expected behavior

Tax calculation should be correct

Additional context

7859784-zd-a8c

[zmaglica]

@dwainm this issue affects taxes, so I am moving this issue to the team Sigma. Feel free to reach out to me or ping another team lead if you think that someone else can work on this issue.

[pierorocca]

@zmaglica please go ahead an update the labels accordingly so that the workflow engine will move this out of the Shopper Experience project board. TY.

[gpressutto5]

@zmaglica This error is tax-related but specific to Apple Pay and Google Pay. It is not the core tax calculation that is wrong, but the logic behind the Payment Request not considering taxes correctly. This issue should be handled by team Heisenberg.

[zmaglica]

Hi @FangedParakeet . Could team Heisenberg work on this issue?

[zmaglica]

@zmaglica please go ahead an update the labels accordingly so that the workflow engine will move this out of the Shopper Experience project board. TY.

I noticed that you have set the label and based on the issue description, the label you set is the correct one. Do I need maybe set something else?

[pierorocca]

I noticed that you have set the label and based on the issue description, the label you set is the correct one. Do I need maybe set something else?

No worries. I had thought based on your comment Sigma was going to take this on. As it is PRB related and staying in Shopper the label as is is perfect. Sorry about that confusion.