#klx_api
jovial jasperBOT
👋 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/1445004422194266193
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
buoyant viper
Desired attached
hallow urchin
👋 happy to help
buoyant viper
Our state attached
In both cases, no email is entered, Link is recognising based on the device or cookie I guess. But, we want the first screenshot - where it shows "pay another way". why doesn't ours have that same look? we've asked every LLM also, and coming up clueless
hallow urchin
buoyant viper
Hm ok let me try switch to that quickly.
hallow urchin
under https://docs.stripe.com/payments/link/elements-link you can see all the different ways you can implement link and how it will show up
the desired behavior is the LAE, whereas what you're using is the Link with PE
jovial jasperBOT
buoyant viper
updated to LAE, and we now have this - which is better, but it's still not the same. hm
in the screenshot i sent of the desired behaviour, their cart is also collecting email seperately above (higher field away from the payment element)
unless this differs in local, but i wouldn't imagine so
tbh, this will likely work for us. my preference would've probably been the same appearance as the screenshot i sent and i'm not sure why we can't seem to get it, but this is better with the clear change option atleast... so if you still have any idea what might be different, lmk 😅
limpid ruin
yeah sorry the intricacies of Link and how it is integrated and appears in the UI is very nuanced. if you want us to debug further, you'd likely need to write in to our team directly and we can investigate further. chances are there's some different behaviour on your account as opposed to what you've seen in the wild
buoyant viper
ok, sure. if we do decide to investigate further, is there a specific dev support email vs general stripe support?