#mallain23_error
proper owlBOT
👋 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/1352003743054565497
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
buoyant crow
Good question, both calls look to have been made on the same account. One of the calls was connect while the other wasn't, but that shouldn't effect thsi behavior specifically.
Does this flow work for you otherwise? Do you have any examples of this succeeding otherwise in live or test mode?
proper owlBOT
cerulean sleet
👋 stepping in here as Pompey needs to step away
Instead of passing the token here you would just pass the Card object that you get from the Token creation response via the payment_method param: https://docs.stripe.com/api/setup_intents/create#create_setup_intent-payment_method
Can you tell me why you are trying to pass this Token via payment_method_data.card?
dreamy plaza
how should it get passed
cerulean sleet
payment_method: "card_xxx"
dreamy plaza
we have a token from the client
buoyant crow
Just before I step out, I do now see that I mixed things up when looking at your log at first. It looks like the create token request happened on your platform account but the setup intent request happened on the connected account. If you initialize Stripe.js as the connected account, the setup intent call will recognize the ID on the second call
https://docs.stripe.com/js/initializing#init_stripe_js-options-stripeAccount
cerulean sleet
Ah yes, you also need to do that