#louis-querel_unexpected
charred lavaBOT
👋 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/1306014417678368798
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
median stirrup
We also see the difference in the dashboard. Thank you for any help or assistance with this.
jagged coyote
Hi 👋
This is just how Link works. It does not expose card details.
median stirrup
Except that we are seeing something different with stripe checkout
jagged coyote
This isn't Checkout/Payment Element specific, it's that Links as a payment method obscures these details
That is likely because you have LInk in a different mode
Where it passes the data through, rather than being it's own payment method
median stirrup
Thank you Snufkin, let me just review a few things with my team and I will come back to this thread
jagged coyote
I'm checking with my team about what governs which type of mode Link operates in
When you create your payment intents for the payment element, are you explicitly passing link as a payment method type
median stirrup
Yes, as we currently cannot have enabled in automatic_payment_methods set to true. We need to be able to control which payment methods are available, even if some additional ones may be enabled on the account
jagged coyote
Okay so you are explicitly passing a payment_method_types parameter? Are you able to quickly test something with me?
median stirrup
I could, give me just a moment to start some services
jagged coyote
I see you are passing
0: "card",
1: "link",
},```
in this request: <https://dashboard.stripe.com/test/logs/req_Q9skHdYYh1bDEe>Essentially I want you to not pass "link". The payment element should still allow your customers to select Link via a little drop down menu
median stirrup
Let me try it out again, but we were not seeing that option before. Give me a moment
If there is a mismatch between the payment element and the payment intent, the following error occurs https://dashboard.stripe.com/test/logs/req_KuRBSBrT4vgCYp
I will redisable it in the payment element, but I do not expect to see Link after I do
jagged coyote
Sorry I'm not sure I follow. You won't see Link the carousel of payment method types but the option to log in to Link and use it as a payment method will be available.
Currently Link only works in Payment Method mode in the Payment Element. This causes the payment methods to be saved without any details for the underlying card
median stirrup
The payment method types need to be set in the payment element and in the backend when creating the payment intent. If I have it set in the payment element and not at the creation of the payment intent, I get the error that I mentioned in the link above.
However, if I set the payment element to also only have the card payment method type, the payment element no longer shows the option for Link
""" paymentMethodCreation: "manual",
paymentMethodTypes: ["card"],
captureMethod: "manual", """"
jagged coyote
Okay yes, if you are creating the Stripe elements object before you have your payment intent
median stirrup
Compared to. According to the documentation, we are using the flow that requires the creation of the confirmation token to allow the confirmation on the backend which does not require the webhooks to receive the confirmation of the payment intent
jagged coyote
Sorry by "Compared to" do you mean the two screenshots are for rendering the Payment Element with and without the "link" value in payment_method_types?
median stirrup
Sorry, yes. When it is enabled in the payment element we can see it, but we cannot do the creation of the payment intent afterwards using the confirmation token. We get the error https://dashboard.stripe.com/test/logs/req_KuRBSBrT4vgCYp
jagged coyote
Yes, the Payment Element and the Payment Intent need to be initialized with the same payment method types
median stirrup
Thank you for your help, I will continue to look into this tomorrow with my team
jagged coyote
It looks like you have Link turned on for all integrations. Unfortunately, it looks like Link is creating Payment Methods with type "link" when used with the Payment Element. This obscures the credit card details