#andrei_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1344351449324326922
๐ 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.
- andrei_api, 2 days ago, 32 messages
Im talking about this
Hello ๐
What does the Address Element render when you create it?
let me show
Especially if you restrict it by either providing Brazil as the address.country in the defaultValues or specifying ['BR'] in the allowedCountries
Im using options like this
export const addressElementOptions: StripeAddressElementOptions = {
mode: 'billing',
allowedCountries: ['br'],
}
for AddressElement component
and my form looks like this
without neighborhood
Hmmm... okay I get the same thing when I test in my own integration.
Can you share the Checkout Session ID where you see Neighborhood?
ye, let me ask
cs_test_c1cDDMdtHL35DI7A9D5j9hnsQv2ZBnghhqekzPFSCA6O5IKqMNKcmpjlI5
Thanks, taking a look now
Okay, I see what you mean and I have confirmed the same behavior in my own Checkout Sessions.
Nice, any ideas how can I reproduce it by using Address Element component?
Unfortunately I'm not seeing an option for that right away. Let me double check a couple things
Sure, thanks
Okay I have not been able to find any options that will cause the Neighborhood input to render when using the Address Element.
I don't think Checkout is using an element that we provide through Stripe.js
It is Stripe because it's a UI that we built and maintain. But I do not think it is using only the Stripe.js elements we make publicly avaialable.
I have flagged your question internally but I cannot say if/when I will get an answer
so, in conclusion, stripe is using fields on checkout, that are not available publicly?
That is what I suspect, given that I cannot get the Address Element to display the Neighborhood input.
ok got it.
should we stay here in chat until we will receive response?
I don't think that would be productive. I have asked my colleagues and they have not been able to trigger this either.
When I eventually hear back, if it is supported I will request we document how to do it.
If it isn't supported I will put in a feature request that we add this capability.
But neither action is likely to happen quickly and we close out threads after ~45m of inactivity
oh, got it
Does this affect whether or not you use Checkout Sessions vs the Address Element?
Does it impact how well billing addresses function?
actually, yes
we are integrating stripe in our app and its necessary field for brazil market
Okay and you don't want to redirect customers to the Checkout Session?
Hmmm... have you looked into using the embedded Checkout approach? https://docs.stripe.com/checkout/embedded/quickstart
It would load the Checkout form inside a page on your site
does it possible to use this approach for setup mode?
Yes