stenerali_unexpected

[agile cedar]

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

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

[brittle burrow]

Where do you see auto? I dont' see it

Oh I see it now

Is this happening across all customers?

[crisp crystal]

yes, I have spot checked about a dozen customers and it's present on all of them

[brittle burrow]

Can you share your front-end code? We haven't seen any other reports of this

Also are you able to reproduce this on your test environment?

[crisp crystal]

Give me a few moments to take a look

[crisp crystal]

yes, it happens in our test environment pi_3Q17eaS7hdrxz3Dn1HwPmBBS pm_1Q17eaS7hdrxz3DnZDNdjwVg

We use the payment element and link authentication element to collect payment details

Could it be this code?

<PaymentElement
          id="payment-element"
          options={{
fields: {
              billingDetails: {
                email: "never",
                name: aConditionBeingTested ? "never" : "auto",
              },```

[autumn totem]

Hi there 👋 jumping in as my teammate needs to step away soon. I'm taking a closer look at that most recent payment method to see if I can spot exactly where that value is coming from.

I don't think it's the code you shared, that's for setting whether email and name should be shown in the Payment Element. I see the value being provided in this request:
https://dashboard.stripe.com/test/logs/req_TMlw99LvezXUv9

Are you able to share your code that confirms the payment intent client-side? I suspect that's where the value is coming from.

[crisp crystal]

Yep, you're right:

          clientSecret: response.data.clientSecret,
          confirmParams: {
            payment_method_data: {
              billing_details: {
                email,
                name: aConditionBeingTested ? nameInAddressElement : "auto",
              },
            },```

Thanks for the pointer.  This needs to be changed.