#arti-villa_error

1 messages ยท Page 1 of 1 (latest)

frozen blazeBOT
#

๐Ÿ‘‹ 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/1344300372377997323

๐Ÿ“ 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.

oak pawn
#

๐Ÿ‘‹ happy to help

#

would you mind sharing more details? screenshots? access to your website with steps to replicate? etc.

pulsar spear
#

ok I managed to get it to work by disabling the billing details on the payment element.

          <PaymentElement 
            options={{ 
              layout: 'tabs',
              fields: {
                billingDetails: {
                  name: 'never',
                  email: 'never',
                  phone: 'never',
                  address: 'never'
                }
              }
            }} 
          />

I would have preferred if the payment element collected the billing information, but it doesn't.

oak pawn
#

I'm not sure I understand

frozen blazeBOT
oak pawn
#

if the Address Element is inside the Elements provider when confirming the Payment the addresses collected are automatically passed

#

is it in regards to when the customer chooses "same as shipping" ?

pulsar spear
#

If I disable the billing details fields in the payment element, I get another error but nowhere in the UI does a payment element actually collect any billing details.

#

Now if I remove the address billing element, it's complaining but there is no field in the payment element to collect any billing information.

hazy veldt
#

Hi there ๐Ÿ‘‹ jumping in as my teammate needs to step away. The Payment Element only collects billing details if they have a likelihood of improving conversion rates for the type of payment method that was selected, otherwise it avoids doing so to reduce customer friction.

pulsar spear
#

Okay, so then this means that the server has to disable this option or I do what I'm doing here using address element form.

hazy veldt
#

Can you elaborate on what that means a bit? From what you've shared so far I'm inferring that you're building a payment integration using our newest version of Checkout Sessions, where you use Elements to build the checkout UI. Is that correct, the approach we show here?
https://docs.stripe.com/checkout/custom/quickstart

pulsar spear
#

Yes, but in your example there are no address element forms. So when you start adding those, there are some client-side errors. In any case, I made it work by disabling the billing address collection on the payment element. so all good

#

I'm off to bed but think this works so we can close this issue