#asrob-paymentelement-link
drowsy wyvern
Are there any differences between the accounts or PaymentIntents?
fickle sierra
Does the UI possibly get tripped up with the + syntax (e.g. me+link@example.com)?
Between accounts? So it's weird it seems like sometimes it's letting me sign up but so far I haven't completely a checkout using Link and the only clue is the above screenshot. From what I can tell it's enabled on the Platform (test) level and is set to inherit that on the account (connected account level). How would I tell if there are any differences?
I'm not trying to use it in production ATM. Just on my local machine in dev mode.
drowsy wyvern
Are you creating direct charges or destination charges?
fickle sierra
Direct I believe. Can you confirm if this is necessary 'payment_method_types' => ['card', 'link',... .
drowsy wyvern
It depends, if you're using automatic_payment_methods while creating PaymentIntent then no you don't need it. But if you want to set payment method types explicitly then you can use payment_method_types parameter
fickle sierra
We're not using automatic payment methods. My confusion is link has never been added as a payment method and yet it still shows up. I thought it was under the card umbrella like Google & Apple pay
drowsy wyvern
can you share an example PaymentIntent ID where you're seeing link show up?
If you've not activated it or haven't added it as a supported payment method then it shouldn't show up
fickle sierra
pi_3Na1JbKLn2y9z7OB1lrWESBQ
Right, if it definitely IS activated do I need to pass link as a payment method? It at least on development seems to always want to create a new Link account (or acts like one doesn't exist). It has just seemed flakey.
Yea I'm not sure what's going on but on development I only have card and half the time it seems to think a Link account hasn't been created and sometimes it knows one has. I'll play with it some more because I can't articulate what is going on except to say it doesn't seem to consistently work how I'd expect (enter new email and signup OR enter existing email and allow me to checkout).
That payment intent is an example where Link just showed up e.g. we're not saying it's a valid payment method.
drowsy wyvern
Link is also shown based on the information stored in the browser cookies.
So if you've been clearing cookies or something after creating the link account then its possible that it doesn't show up randomly
fickle sierra
It always shows. It sometimes doesn't seem to understand that an email I've used previously really does have a Link account associated with it.
drowsy wyvern
It does seem like its enabled on the connected account acct_14fxn2FDlZuFWbQJ under
https://dashboard.stripe.com/test/settings/payment_methods
fickle sierra
Yea I appreciate your help but the inconsistent behaviour is what I'm trying to figure out and it's unclear to me if link does or does not need to be passed as a payment method. I again thought it was like Google & Apple pay and was under the card umbrella but the only reason I'm asking the question is because it seems to mostly think every email I provide does NOT have a link account. That payment intent where it's enabled
If I go to the page and enter an email it just sits there.
Like this:
The email entered definitely has a Link account
drowsy wyvern
I see. Thinking about the behaviour overall, since you're not passing in payment_method_types explicitly, the API looks at your dashboard setting. Let me check if we have any public docs explaining this behaviour
fickle sierra
I mean given the above screenshot I'd say it's enabled and for that environment/site we're not passing it as a payment method. With that said it can't seem to find the @gmail.com address where I can log into link.com and see saved cards. Something just feels off and I have no idea what.
sinful gull
👋 Taking over as it's quite involved. I know ~nothing about this so will take some time to figure out what's happening
Can you give me a concrete PaymentIntent id where it does appear so that I can compare the two accounts?
You also updated that PaymentIntent you shared earlier so many times. Would be awesome if you could create 2 brand new PaymentIntents @fickle sierra one on two separate accounts that exhibit a different behaviour for me to look into it
fickle sierra
Yea let me see if I can get that for you.
sinful gull
Our current assumption is that because you do not pass link in payment_method_types, Link will only show up for specific Standard accounts where Link works in what we call "passthrough mode" which is when we treat it as a normal card (like ApplePay and GooglePay). So the Standard account you are testing with right now is quite old right now and has that setting enabled, but newer accounts wouldn't (and would require link as a real PaymentMethod)
This would likely explain why that account sees it and others don't. My guess is your other Test Standard accounts are newer and don't have that old setting
asrob-paymentelement-link
fickle sierra
@sinful gull Rather than waste your time let me look into this some more. The issue on production may have been an inconsistently applied CSP. Just one of those days so it may be better to regroup.
sinful gull
sounds good. But ultimately if you don't pass link as a value in payment_method_types you basically will only see it on old connected accounts
so if you do want Link to show up you should move to pass it, or use automatic payment methods instead
fickle sierra
What does "old connected accounts" mean? You mean accounts where it was previously enabled?
That's helpful but opposite of how it works with Google / Apple Pay if I understand.
sinful gull
No it means accounts created say before 2023 that also have used Link at least once or something
And yes it's different, we own Link, we're designing it differently with a lot more advanced features
we did have Link work as a wallet for a while but now it's evolved a lot and is a standalone payment method like CashApp Pay or Paypal are
sleek sableBOT
fickle sierra
Strange. Good to know then. Yea by different I meant not intuitive because Apple / Google work the opposite way. We have customers using it in production that AFAIK we've never enabled (nobody knew what it was until recently) and we're definitely not passing it as a payment method currently.
sinful gull
I do recommend looking into enabling it on your integration
Obviously I am biased, I work for Stripe and we own this, but it makes checking out a lot faster for your end customers!
fickle sierra
Yea the reason it came up at all is because in 4000 transactions roughly 21% were from Link and nobody knew what it was. My point being it must have been auto enabled for "old connected" accounts.
sinful gull
correct
fickle sierra
21% of Wallet accounts
sinful gull
we launched Link end of 2021 I thiiiiiink
and at the time we increased adoption by making it "passthrough mode" like ApplePay and GooglePay
fickle sierra
Ok well I'll play with it some more. I know how it's supposed to work and our customers have clearly figured it out 😉
sinful gull
but the product has evolved a lot and is now its own PaymentMethod type with features/restrictions
but I get how, as a platform, it's tricky when you suddenly get a wallet like this but can't reliably reproduce. We tried to be careful with the feature rollout but Connect makes this hard
fickle sierra
Well I'll circle back if I continue to have problems but I appreciate everyones help.