#andrew_code
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/1377739801893277798
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there
so there is not a way do actually prefill a phone number for Link signup.
But, Link comes with a pre-fill tool https://docs.stripe.com/payments/link/payment-element-link#automatic-link-prefill
I see... so it would search the page for something that looks like a phone number? Problem is the user enters their phone number on the previous step
So when there is already an email or a phone number populated on the checkout page, Link will scan for it and auto populate the phone number it into the Link singup/signin
But if we did print it out on the page somewhere, Link would find it? We print the email address so I guess we could put the phone number next to that
The Link tool will only scan the current page.
So yes, if you had the phone number on the same page as the Payment Element, the Link prefill tool should find it.
no problem
We do have a checkout variation that has the phone on the same page
But it doesn't seem to work
Does that phone field qualify?
Yes it should qualify. Is the Link tool enabled? It should be default though. You can check in your Link settings https://dashboard.stripe.com/settings/link#features
Yeah we were just checking. It's enabled
Just to clarify, the phone number in the shipping address gets pre-populated, but the Link tool is not catching it?
It isn't prepopulated, but the user enters it first, before they enter their credit card info
Does the phone number need to exist on the page before the payment element loads?
Yes. The tool "scans" for existing phone numbers on the same page only once when we the Payment Element loads.
Hi there - I'll be taking over for my colleague, who needed to step away
Looking at the docs, we specifically say that the Link prefill tool looks at input fields that have email/phone number. Let me see if I can find out more about that
Okay, thanks. It seems like it's not super useful if it won't pick up a phone number that the user enters after the page loads. According to your colleague it only "scans" when the page loads, so the phone number would need to exist inside an input field when the page loads. And I'm not sure what the use case would be for that?
Yeah, if that's the case it seems fairly limited
๐ฆ
I tried with a hidden input as well and that doesn't work
Do you have any example pages where the functionality is demonstrated?
I tried something similar - conferring with my teammates about this
We were having some trouble with this as well, and would need to talk to the product team about it. If you follow the instructions that will be sent to you via dm, you can open a support case and we can update you after the discussion with the product team.
I'm sorry, I know that's a poor experience here.
Hello @cloud spoke, we have sent you a direct message, please check it at https://discord.com/channels/@me/1377763389220327425
- ๐The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
All good, thanks
By the way, is there a page I can use for reference where you're rendering the payment element and the phone number is present on the page, as in the screenshot you sent? That would be useful to refer to when talking with the product team.
Sort of... this one has the phone field and payment element on the same page. But the phone field is not filled before the payment element loads.
https://v3staging.getflightpath.io/offer-03-crossover-testing/
And then this one you enter the phone on the first step of checkout, and then the payment element shows on the second step. So there we could add a hidden form field easily. But I was trying it locally, it's not deployed yet.
Got it - thank you!
Thank you too