#matt_link-noncard
quiet valeBOT
👋 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/1488993377063010406
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fossil trench
matt_link-noncard
indigo summit
Hello again, koopajah! hope you have been well.
fossil trench
👋 I don't really get your question. This request is a PaymentIntent creation
I looked at the PaymentIntent itself and it shows a "card" was used to pay
indigo summit
well, i think the problem that we are having on our side has to do with the payment method type of "link card", which i think is new as far as our system is concerned. When i have tried setting up other payments via link, what i get for the payment method type is whatever the underlying payment type is. example from lower environments: https://dashboard.stripe.com/acct_19sH6VHAuKxNQma4/test/payments/pi_3THUm5HAuKxNQma406cGVNXP
so, under payment method, it looks like this:
i would like to figure out how to get one that looks like this:
basically how do i create my own test version of pm_1THRo6BnxMPxdETub7JINEZv ?
fossil trench
The PaymentIntent you created has payment_method_types: { 0: "card", }, so you forced to only use card
And then on confirmation you seem to use PaymentElement and that offered Link as a payment method. Not sure how exactly, I'd have to see your code and how you initialize the whole thing
indigo summit
well, at some point Stripe's built-in Link sniffer is taking over when i check out twice in the same testing Incognito window. first time through i see the payment element stripe.js control that offers me either card or us bank account as a payment method type; pick one, fill in the information, and then at the end am prompted to save in Link. 2nd time through the Link button shows first. i'm not doing anything special to invoke it.
fossil trench
yeah we remember you used Link and show it
indigo summit
i think i might know what's happening. our connected account admins have the ability in our software to dictate which type of payment methods (card or bank) are accepted in certain areas of the application. the customer that is having the issue/error has bank payments turned OFF in the area that the error is happening. if the Link user was able to add a bank account somewhere else and add it to Link, i wonder if they get the option to choose a stored Link bank account when checking out even though we are only passing card as the allowed payment type to the payment intent creation.
I'm going to go try a couple of things... i think you can close this thread out. i have a decent idea of where to look although I would still love to know how i could get a payment method that has that detailed note in the grey box above it because then i would know i was testing something more similar.
fossil trench
yeah that is what's happening. If you use a saved bank account in Link, it still looks like a card for certain reasons
indigo summit
that's gotta be it. ok; off to make a test case and fix!
thanks so much for your help and knowledge; i truly appreciate you!
fossil trench
sure thing, glad I could help. That feature of Link can be really confusing when we "fake" a card to let the end customer using Link still pay however they prefer
it all makes sense, but it's hard to grasp
indigo summit
actually i did have one more question; i'm trying to test with a brand new link user; and it keeps recognizing one i used previously, even if i use a new incognito window. any way to defeat this?
indigo summit
hahaha glad it's not just me.
