#rdhelms_unexpected

1 messages · Page 1 of 1 (latest)

dapper narwhalBOT
#

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

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

lilac ridge
#

Hello, trying to understand exactly how this error gets raised. If I create a Checkout Session for any payment that also uses Tax and then select Guam in the UI I should get this error?

#

Trying to reproduce this on my own account but if you have a test mode checkout session I can reproduce in that could be helpful as well

dire pendant
#

Yeah let me capture some example steps using our app

#

network response from https://api.stripe.com/v1/payment_pages

{
  "error": {
    "code": "customer_tax_location_invalid",
    "doc_url": "https://stripe.com/docs/error-codes/customer-tax-location-invalid",
    "message": "The customer's location isn't recognized. Set a valid customer address in order to automatically calculate tax.",
    "type": "invalid_request_error"
  }
}
#

But that error is not shown anywhere in Stripe Dashboard logs or events

#

And then if I change the address to use a country of Guam instead, then the purchase succeeds

image.png
lilac ridge
#

Gotcha thank you. My first test Checkout page confirmed this with no error, so I'll compare our configs to narrow down the issue and we can figure out next steps from there. Sounds like I'm almost definitely escalating this to my eng colleagues because it is an error on our page and you aren't getting notified

dire pendant
#

Let me know if there are any other properties from our checkout session creation that you'd want to compare other than automatic_tax

#

Here are some of the other properties we're setting when creating the Checkout session

        ui_mode: 'embedded',
        customer_update: {
            address: 'auto',
            shipping: 'auto',
        },
        billing_address_collection: 'required',
lilac ridge
#

Thank you, will try those as well. I reproduced this on your site and got the erroring request ID in our logs, trying some more to narrow down the cause.

dire pendant
#

Sounds great, thanks

#

Other than just having the issue escalated to engineering, I'd also be curious to know if there's any way for us to know how many of our other customers may have been affected by this error. We only heard about this one because a user reached out, but we don't have any sense of how many people may have been unable to purchase without us knowing

lilac ridge
#

So the important difference seems to be subscription vs payment mode on Checkout. Without adding the customer update or anything else from your call I was able to start getting this error.
Filing something for this right now. Do you want to follow the progress on this fix in a ticket? Can look in to effected users and get back on that through that email as well.

dire pendant
#

That would be great, thanks

#

Thanks so much for investigating and reproducing the issue

dapper narwhalBOT
#

Hello @dire pendant, we have sent you a direct message, please check it at https://discord.com/channels/@me/1433178354571411537

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
lilac ridge
#

Can you use the above to create a case and let me know when it is submitted? I can grab from there and follow up through there

dire pendant
#

Will do

lilac ridge
#

Thank you!

dire pendant
#

I'm going to be unavailable here shortly - thanks again though for your diagnosing the issue and following up on that ticket. I'll keep an eye out for any further information there

lilac ridge
#

Of course! Thanks for the clear report and easy site to repro on. I will follow up through an email in the case shortly