#jarrett
1 messages ยท Page 1 of 1 (latest)
Hello ๐
Have you tried setting never to billingDetails when creating the element?
Awesome ๐ Glad that worked
So does it work or no? ๐
fwiw this works for me
fields: {
billingDetails: {
address: {
country: 'never',
postalCode: 'never'
}
}
}```
i just had never in the top
like billingDetails: 'never'
oh i'm missing fields
i see
it does work
sorry, total ammeature mistake
NP! ๐ Happens to me all the time lol
now the reason I even ask is because with address element you can't use link it seems like
is there a reason for this?
Ah I am not aware of such limitation
It should work with Address + Payment Element as per
https://stripe.com/docs/payments/link/accept-a-payment?platform=web&ui=elements&link-integration-type=at-payment
Oh I see what you mean, you can't pass the information you've already collected to the Address Element.
i mean that's not really my issue. i just noticed if you add Payment Element and Address Element Link disappears
but if you add Payment Element without Address Element, Link appears
i don't currently have a separate Link Element tho
yeah I think you need that in order for Address Element + Link to work
hmmm, odd. it's a little wierd cause it's just a random email field that we don't really need since we're signed into a dashboard
we already have the customers email
Hi ๐
Link might only collect email but it's used to create a Link account and use it as a payment method so the behavior is different.
What specifically in the UI is not appearing?
link
if you look at my first screenshot without the address element enabled, Link shows up
whereas my second one with the address element, it does not
Hi there ๐ thank you for the clarification, it sounds like you're referring to the box that is available to opt into Link at the bottom of the Payment Element.
Can you help us understand when that option disappeared? Was it removed immediately so that you did not see that section rendered at all, or was it removed when the invalid zip code was entered in the Address Element?
Additionally, are you passing an email address into the Elements when they're being created? I don't believe so as I believe doing so for an email that is already registered for Link would result in an authentication challenge being surfaced, but would like to confirm.
stepped away for a few but ill check all of this. the zip code is coming from a default value tho
Sounds good! Taking another look through our documentation, I think this may be expected though. It looks like in order to support Link and the Address Element, the Link Authentication Element must also be used:
https://stripe.com/docs/payments/link/accept-a-payment?platform=web&ui=elements&link-integration-type=before-payment#collect-shipping
i guess the best option is to just use my own address form for now as we do
i have another thing... if I have this box and I submit it by hitting enter, is it supposed to submit the payment element? this is broken as far as I can tell since i will then get the option to enter a code while I have errors on the form fields below
idk why it's even suggesting those fields are incorrect when I hit enter on the code field
Is the is a single form submission handler?
yes
Are you expecting it to validate against the code?
I would expect it to look for the code, then fall back to validating against the card input if the code is not present
if i hit enter on the input, i wouldn't expect it to submit the form
if i hit enter on the email for link, it submits the form
then 2 seconds later the code input pops up
I see what you mean. Give me a sec to try and reproduce
Sorry fo the delay. I haven't been able to reproduce on my integration