#admin-paymentelement-linkauthentication
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- admin-payment-element, 13 minutes ago, 44 messages
- hellodoc5514-connect-link, 4 days ago, 42 messages
- hellodoc5514, 6 days ago, 13 messages
- hellodoc5514, 6 days ago, 17 messages
You can add it if you want but it is not required if the customer is already signed in to Link
not sure what does that mean ? are you saying if i use the payment element and add link, if customer put the email , it has same effect as adding the linkauthenticationelement ?
@haughty parrot PaymentElement has no email field today for card payments. You need the LinkAuthenticationElement for it to work
if i enable Link payment on dashboard and enable automatic payment method, the link control shows on the payment element component
like this one
if i put the link Authentication Element, it looks like the following:
it has an extra email input
give me a few minutes to catch up
but doesn't contain the previous UI
sure, please take a look and let me know then
Hi there 👋 taking over here.
Can you summarize the question? It sounds like you've found a couple of ways to use Link, but I'm unsure what you're asking
they are asking what the point of LinkAuthenticationElement is since PaymentElement supports Link already
And then they shared detailed screenshots of attempts with and without LAE
I mean, as far as I can tell they are functionally the same, no?
Seems like it's just a matter of preference when it comes to UI and payment flow
yes, i'm interested to why i need LinkAuthenticationElement
since Payment Element already provides similar functions
We're still digging a bit to make sure there aren't any meaningful differences outside of UI, so we'll circle back in a few.
@haughty parrot mostly LinkAuthenticationElement was built before we added support for Link inside PaymentElement. And it allows developers to have the Link authentication way earlier in their form as many start with an email field.
But in terms of features, it's fine to just have it in PaymentElement and not use LinkAuthenticationElement at all
To add on a bit to that: LAE proves to be a bit more useful when used in conjunction with the Address Element, since putting LAE at the top of the page (before the Address Element and Payment Element) can autofill many of the downstream elements.
If you're not using or don't plan to use the Address Element, then you can mostly ignore LAE as koopajah suggested