#theruv
supple wren
Hi there 👋 I'm not sure I'm grasping the question. At what point in the process are you interested in disabling Link? If you're not planning to accept Link payments then I'm not sure that using the Link Authentication Element is a good fit.
maiden estuary
I'm currently using Link to collect email address & also support link.
However I'd like to setup an AB test to disable link and see how that impacts conversion and card declines.
I want to explore if there is a way to programmatically use the link-element with payment elements, but disable Link as a payment method for certain transactions.
supple wren
You can use payment_method_types when creating the Payment Intents to override automatic payment methods, which would allow you to suppress Link if you don't include it in that array. I'm not certain offhand how the Link Authentication Element will behave in that scenario though.
https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_types
maiden estuary
I tried this where payment_method_types just contains "card" but the link authentication element still enables link
Do you have any ideas on how to approach this?
supple wren
The only thing that comes to mind is to not use the Link Authentication Element, and instead replace it with your own email collection field, if you don't want to accept Link payments.
maiden estuary
I've removed the link auth element but link is still rendered do you know how this can be removed?
supple wren
Dang, didn't realize it would still appear there. Now I think the only way to avoid Link being offered is to disable it for your account, which would prevent you from being able to A/B test.
maiden estuary
I understand. That's not ideal, but it's good to know.
Please let me know if you find a way to disable it without disabling it globally. 🙂
supple wren
Will do! Going to reach out to some folks to see if they have a suggestion.
sharp siloBOT
supple wren
@maiden estuary are you also using payment_method_types when creating the Payment Intent, and ensuring you don't pass link to that array?
I tested that on my site, and doing so suppreseed the presence of the Link field within the Payment Element:
maiden estuary
Hmm, thats strange. Yes I'm not passing link to the array - below is the paymentIntent
I'm using subscriptions and have it enabled in billing payment methods
in the dashboard
supple wren
Oh, I had assumed this was for one-time payments. Let me see if I can slam a sample Subscription integration together. For those I think the Payment Element will use a combination of what Payment Methods are enabled and what is enabled in your Invoice Template settings.
supple wren
Sorry for the delay, still working on it.
supple wren
@maiden estuary if you're still around. I was able to suppress Link in my Subscription flow by passing payment_settings.payment_method_types with only card while creating the Subscription:
https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_settings
Something I probably should have asked much sooner though, is whether you're using the deferred intents flow (where you render the Payment Element and collect payment method details first) or our more traditional flow where you create a Subscription and then use the client secret from its most recent Invoice's Payment Intent to render the Payment Element?
maiden estuary
Hey Toby! I'm using the traditional method where I generate a subscription and then render elements - would this not work with it?
I really appreciate your help
supple wren
I think it will. Though if the Payment Intent was already being created with only card listed as an available payment_method_type, then I'm a little worried there is something else I'm overlooking.
That's the same approach I was using, but realized I may have been making another bad assumption and wanted to clear that up 😅
Could you also share the ID of your account?