#matt_link-connect
tough yokeBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253440973686571032
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
median houndBOT
unreal snow
Hi there 👋 that looks like a Payment Element integration there, and I may need more context about how you built/structured that flow to understand why Link is still being surfaced there and how to disable it.
Is this happening in both live and testmode? Do you have a test site that you'd be able to share with me where I can take a closer look at this flow?
The only thing coming to mind to try without more details, is to click the ... button seen in your first screenshot, and disable the toggle for Payment Element after expanding the Supported integrations option that appears in the settings screen that appears.
lunar agate
I did make sure that payment element was disabled, it requires that you keep one thing checked.
Yes this is on both production and testmode.
And yes I can share a test env with yout
possible to send you the link privately? I'd rather it not be public to the world if possible.
unreal snow
Sorry, I don't accept DMs here. If you'd like to start a private discussion, you can start that by contacting our Support team to open a case which is private:
https://support.stripe.com/?contact=true
Out of curiosity, are you manually declaring payment_method_types when creating the intent you're using with your Payment Element, or that you're providing directly when initializing Elements if you're using our deferred intents flow?
Thank you, I've pulled that into a notepad if you want to remove the message now.
lunar agate
devs say in regards to payment method types "no, this information come from paymentIntent"
unreal snow
I believe this is happening because Link is still on for your Direct Charge payments. Can you try setting it to Blocked here?
https://dashboard.stripe.com/test/settings/payment_methods/connected_accounts?config_id=pmc_1NO4jkFIw0ONrpAv5MHqzDIw
lunar agate
ok I made the change at the main account. wait for them to propagate
tough yokeBOT
native moat
matt_link-connect
unreal snow
I see it's stopped appearing on your test page for me.
lunar agate
it did for me as well
I am testing in production real quick
yeah that seems to have done it.
native moat
awesome!
lunar agate
seems weird that even though it was off at the connected account level. It required that I turn it off at the host account AND turn off the supported integrations.
I guess off... isn't off 😦
but that works for now. Our plan is to turn it back on once we can get the cookies/session info taken care of.
Is there any documentation on using payment elements in a Kiosk mode situation you can refer me to?
native moat
@lunar agate I don't think we have any docs for something like this. I don't think it's a supported use-case honestly as PaymentElement is for payments on the web on the consumer's own device, not to enter card details visually in a kiosk (you really shouldn't do that)
lunar agate
got it. Yeah we've phased them out and replaced with QR codes in most situations.
native moat
yeah that's much better
lunar agate
I would love to attach a terminal device to each kiosk. Or just get rid of them entirely. 🙂e
native moat
🙂