#mattcomroe_api
spark hullBOT
👋 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/1398319433361002617
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
cloud plume
Hi! Thanks in advance for your help!
cosmic cobalt
Hi, it looks like that payment method https://dashboard.stripe.com/test/logs/req_8HHBKR4uiK3k5N was created on
account ending in Qma4. However, you're attempting to create the PaymentIntent, https://dashboard.stripe.com/test/logs/req_Pckm0WyoXCCuJi on behalf of account ending in 0Nhkv. Since the payment method was created on that other accout, the mandate was created on that other account. You need to create a payment method on the Connected Account, https://docs.stripe.com/connect/authentication and try that PaymentIntent again.
cloud plume
thanks for the info! So, let me make sure I follow. The setupintent was created using on_behalf_of... evt_1Romo0HAuKxNQma4erQ5RJLp. That is so that the mandate will match the connected account, acct_1MF181H9z320Nhkv.
sorry, it's here: evt_1Romo0HAuKxNQma4erQ5RJLp
cosmic cobalt
The alternative is to use this flow: https://docs.stripe.com/payments/save-during-payment where you save the payment method on the first payment using the on_behalf_of flag so the mandate is collected on the Connected Account
cloud plume
oh wait i had it right the first time.
using the Checkout with the SetupIntent to initially add the payment method is a newer thing for us.. is that maybe part of the issue?
cosmic cobalt
you're right, it was created with on_behalf_of for pm_1RompCHAuKxNQma4t7UY1Umd
cloud plume
so this API request was done via the stripe js as part of checkout, right? req_8HHBKR4uiK3k5N
does that not support passing through on_behalf_of?
cosmic cobalt
I was moving too fast. Let me further look here
cloud plume
no worries! BACS has been a learning experience for all of us. 😉
cosmic cobalt
Ok, that is an additional feature to allow passing mandate_data on the confirmation request.
It had nothing to do with what I previouslt shared, sorry for the confusion
cloud plume
not a problem. i'll disregard the previous. 😄
cosmic cobalt
Our support team will be able to assist you better than I can: https://support.stripe.com/contact so you can use this
This was my first intuition but I then changed my mind as I saw the pm request and I was just moving too fast.
cloud plume
before i hop over to support; can you elaborate a little bit on "that is an additional feature to allow passing mandate_data on the confirmation request.", please? Do you mean that you think we are calling the confimPayment correctly but there's something missing in our Platform or account config and support will need to sort that out for us?
some feature we need to be gated in to?
cosmic cobalt
Yes exactly, there seems to be an additional feature to enable passing mandate_data on the confirmation request
You can share the above error message you saw from the request failing and ask them to add this feature on the account
cloud plume
is that undocumented or can you point me to something to bring to support to say "this doesn't work"?
ok will do.
thank you!
cosmic cobalt
Sure
cloud plume
appreciate you. have a good weekend!