#asrob_code
haughty steepleBOT
đ 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/1296886169568673926
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
scenic finch
Hello! To clarify, are you setting explicit payment method types on your Payment Intent?
languid kiln
Apologies for the delay. Yes, we're setting explicit payment methods.
It's a Connect account and AFAIK just worked in the past.
scenic finch
Can you give me the ID of the Payment Intent so I can take a look?
scenic finch
This Payment Intent has a lot of update requests. Can you try creating a new Payment Intent with the desired payment_method_types set on the initial creation request, then see if it behaves the same?
Also, can you confirm you're initializing Stripe Elements with the client secret of the Payment Intent?
languid kiln
See if this is any better: pi_3QBKMaGdYMBuK3oN17E8ciA7
scenic finch
That's better. There are still some update requests that don't seem to be changing anything, but that shouldn't impact what you're trying to do.
languid kiln
It looks like it to me elements = stripe.elements({ clientSecret: client_secret });
scenic finch
Yep, that's correct. Do you still get that message with this Payment Intent?
languid kiln
Yes
scenic finch
That means those payment method types aren't enabled in the connected account's Dashboard, but since you're setting those payment method types explicitly that shouldn't matter and they should show up as long as they're valid for that particular payment.
On your page are you seeing card, Link, and Affirm as options?
languid kiln
So what is weird is it gives that error message but if I enter a test card it pops down the UI to save the card with Link with the correct email address pre-filled.
scenic finch
Right, that makes sense because you're in test mode. This would also work in live mode after the connected account onboards/activates Link and Affirm so they're valid options for the payment.
languid kiln
Ok, yea not sure what's going on here. I'll play with it some more but it's not a high priority just was fixing something else and this looked "broken"
scenic finch
I don't think anything is broken, it's just warning you that you'll see different behavior in live mode because the connected account you're using doesn't have Link or Affirm enabled.
languid kiln
Is the idea you wipe the test data frequently so I can re-signup frequently.
It does as far as I can tell but maybe I am incapable of interpreting your dashboard.
scenic finch
You would need to log in to the connected account's Dashboard, switch to live mode, then onboard/enable both Link and Affirm in the settings there. Are you perhaps looking at your platform's Dashboard instead?
It seems like the connected account is for testing only, as your platform is only connected to it in test mode.
languid kiln
As far as I can tell it's enabled in both (test/prod) for this account. It must be working somewhere so I'll just assume it's working because I'm not sure why I can't test the way I expect.
scenic finch
The other place to look would be here, on your platform account: https://dashboard.stripe.com/test/settings/connect/payment_methods
languid kiln
Wouldn't when it says "Inherit default (On)" effectively be inheriting from the Connect settings?
scenic finch
Can you show me a screenshot of what you're referring to?
languid kiln
scenic finch
Ah, so you're looking at the settings for that specific connected account via your platform account. Inherit there means it will inherit the setting the connected account itself sets in its own Dashboard, I believe.
Can you check here? https://dashboard.stripe.com/test/settings/connect/payment_methods
languid kiln
Right maybe I don't get Link but I thought if I'm logged in and provide a valid Link email id it gives me options to "pre-fill" CC details.
Maybe that's not true because test data (for Link) is wiped frequently?
scenic finch
Sorry, I think we're talking past each other. Go to the link I shared above, then click on Your connected accounts and tell me if Link is enabled there or not.
languid kiln
Yes. "On by default" (test mode)
scenic finch
Okay, now switch to live mode. Is it still enabled?
languid kiln
Same "On by default"
scenic finch
Okay. Do you have the Allow connected accounts to customize their own payment methods from the Dashboard setting on or off?
languid kiln
It's unchecked which I assume is off.
scenic finch
Okay, so that means Link should work fine in both test and live mode for direct charges from your platform because you're explicitly specifying Link as a payment method type on the Payment Intent.
Now, separately, it sounds like you have a different question about the email address used in Link? You're using an email address you used previously in test mode and you're expecting it to be recognized, but it isn't?
languid kiln
Right the thing that looks like it's not working is when a Link customer comes back (so yes).
scenic finch
You're using the same email on the same connected account, correct?
What I mean is you went through the Link account creation flow in test mode on this connected account with an email address in test mode, then you went back for a second payment with the same email address and the same connected account in test mode?
@languid kiln You still here?