#akzent_ece-tax

1 messages · Page 1 of 1 (latest)

sharp fossilBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1287909121349259305

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

full stump
#

👋 I'm not sure I understand your use case. Why do you have AddressElement if you use ExpressCheckoutElement? GooglePay and ApplePay have their own address saved with their individual profile(s)

magic willow
#

I need to retrieve the address from the ExpressCheckoutElement and call our internal tax API to calculate taxes then re-ender the ExpressCheckoutElement with the new total including taxes

#

With ExpressCheckoutElement we get access to the address only on "onConfirm", after the customer has seen the total and agreed to pay

full stump
#

Sorry I read this as two opposing sentences.
You want the address from GooglePay, you know GooglePay only gives the address after submitting, so you have to adapt your use-case and get the address after submitting (which is still before the real confirmation)

#

If you use AddressElement, it's going to confuse the end user that won't know which address you are planning to use no?

magic willow
#

ahh right. clicking "confirm" on the ExpressCheckoutElement modal is only generating an Intent right? then we still need the customer to click on a Confirmation button to trigger creation of Customer/Subscription and confirmPayment

full stump
#

Not really but I don't get your vocabulary right now sorry 😅

magic willow
#

haha sorry

full stump
#

What do you see in Test mode when you try this end to end?

magic willow
#

the reason we have all 3 elements on the page is so Design can put the Apple/Google/Link element elsewhere on the page and it isn't tied to the top of PaymentElement

image.png
#

so if they choose to click GooglePay, should we hide the AddressElement?

#

when they click "Pay", what happens? is the "total" amount shown actually charged? Or do we have time to adjust it for taxes after they click "Pay". Seems like we need to show the Customer the FULL total + taxes in this modal, but we're not able to

image.png
#

Basically, my main concern is not being able show the Customer the ACTUAL total being charged on this modal because we haven't calculated taxes yet

full stump
#

so if they choose to click GooglePay, should we hide the AddressElement?
Yes I wouldn't show AddressElement at all in that flow

#

when they click "Pay", what happens
at that point it goes back to your code and you control what's next such creating a PaymentMethod, confirming a PaymentIntent, etc. There are many ways to integrate all those products and APIs so it depends on your integration

#

but after clicking pay the UI is going to be dismissed so whatever adjustment you want should happen earlier.

magic willow
#

but after clicking pay the UI is going to be dismissed so whatever adjustment you want should happen earlier.

I can't make an adjustment to the total earlier because the ExpressCheckoutElement doesn't give me the address until the customer clicks "Pay"

full stump
#

Okay i asked my team and yeah it's just not supported at all today unfortunately. We have callbacks for shipping details but not billing details. So you can't get their address upfront to calculate tax unfortunately

#

akzent_ece-tax

magic willow
#

is this the same case if I use Apple/Google pay inside the PaymentElement instead of the ExpressCheckoutElement?

full stump
#

yes

magic willow
#

Do these elements only work with tax-less products then??

full stump
#

yes

magic willow
#

are there any technical downsides to requiring the customer to enter a shipping address and then using that as their billing address to calculate taxes and re-render the element?

full stump
#

Technical downsides no (and you can see the shipping address selected with ExpressCheckoutElement). I can't speak about tax compliance/rules