#paymentplugins_code

1 messages ¡ Page 1 of 1 (latest)

open palmBOT
#

👋 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/1266425099876044892

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

real wasp
#

I can provide a link to a testing site where this behavior can be observred. I just would prefer to share the link privately if possible.

plucky sphinx
#

Hello
You can DM me the link

real wasp
#

Ok, sent via feedback channel.

#

Yes, you're right, I can reproduce on your 4242.io domain. Why would the address element be disabled for a BNPL?

#

That prevents the customer from entering all of the required address info needed for tax calculations.

plucky sphinx
#

Are you use Stripe Tax API for the calculations? Just to make sure I am on the same page

real wasp
#

Yes, I am using the Stripe Tax API.

plucky sphinx
#

Are you using shipping mode or billing mode for address element?

real wasp
#

billing mode

plucky sphinx
#

what happens if you switch to shipping mode?

real wasp
#

Let me try real quick and I will get back to you.

plucky sphinx
#

Yup

real wasp
#

It's not disabled when mode = 'shipping'

plucky sphinx
#

Gotcha. Interesting...

real wasp
#

Yep, that is odd because the tax API can use a billing address if specified

#

Unfortuntaly I can't use the mode = 'shipping' workaround because this site is for digital products and when shipping mode is used, the PaymentElement renders a checkbox "billing same as shipping"

#

That will cause confusion for the customers

plucky sphinx
#

I think the fields get disabled as Klarna collects its own billing details..

Taking a step back, when exactly do you create the tax calculation? I see that you're rendering address element with payment element...

Aren't you really just confirming the payment at that point?

real wasp
#

Klara only collects the country code and full name fields which aren't enough to perform an accurate tax calculation.

The tax calculation is created once the customer enters their address info in the address element. When enough fields have values, the tax calculation is triggered.

Payment confirmation occurs server side. When the place order button is clicked, stripe.createPaymentMethod is called and then confirmation occurs server side.

plucky sphinx
#

Klarna collects full billing address but they don't provide that to us. PaymentElement is built to automatically collect whatever billing details required to complete the payment successfully. But that "automatic collection" part depends on the type of the payment method too.

The only workaround here is to use address element separate from PaymentElement and use the collected address to calculate taxes..

Stripe Tax API is recent and I don't think Elements team anticipated your usecase when they built the element

I'd also recommend filing a feature request via our support page
https://support.stripe.com/?contact=true

real wasp
#

Ok will do. To confirm I understand, I should have two separate <Elements> one that wraps the address element and one that wraps the payment element. That way they aren't communicating with one another?

plucky sphinx
#

Correct.. you can keep them on separate pages if that works for you

real wasp
#

Thanks for the info, I will give that a try.