#april-connect-paymentintent
minor lava
Hi, taking a look here
dull aspenBOT
minor lava
Still taking a look here
coral field
april-connect-paymentintent
minor lava
The issue appears that when you create the Payment Intent, https://dashboard.stripe.com/test/logs/req_nRaVQnmUB0LZDv you do not use the Stripe Account Header. Then, on the ocnfirmation you do.
I think you're mixing up a couple of things here so let me add more details here
coral field
@dire eagle what are you trying to do/achieve exactly here? You seem to be a Connect platform so the first step would be to explain
- What kind of connected account types you're using: Custom, Express or Standard.
- What exact flow of funds are you aiming for: Destination Charges or Direct Charges or something else?
As my colleague explained, you seem to mix up both of those concepts so right now you are creating the PaymentIntent on the platform (your own account) but then confirming it on the connected account (because of how you initialize Stripe.js)
dire eagle
What kind of connected account types you're using: Custom, Express or Standard.
Standard
What exact flow of funds are you aiming for: Destination Charges or Direct Charges or something else?
we have an arrangement with stripe for rev share off of connected accounts transaction, we are not doing destination or direct charges.
what are you trying to do/achieve exactly here? You seem to be a Connect platform so the first step would be to explain
We have a platform that orchestrates order flow. We are using stripe as a payment provider. We want to allow our merchants to create payment intents and then confirm them in our backend after handling some server side actions.
coral field
we have an arrangement with stripe for rev share off of connected accounts transaction, we are not doing destination or direct charges.
That's not something that changes the flow of funds. You must be doing Destination or Direct so I need you to clearly confirm what you are doing
dire eagle
Direct then
coral field
Okay so you are a platform, you have your own Stripe account acct_123, and you have a connected account acct_ABCDE and you use Direct Charges where you create the PaymentIntent yourself on that specific connected account right?
dire eagle
The merchant is creating the payment intent with there connected account (currently), we are just confirming it
coral field
Okay that's the part that was confusing I think. Why is the merchant creating it exactly? This is not a normal flow as a Connect platform. You should be the one doing it
dire eagle
Why is the merchant creating it exactly?
Flexibility on our side, we could allow merchants to call an endpoint in our system to create it, but different merchants might want to create there payment intents in different ways and not even confirm payment in our server if they don't want to.
This is not a normal flow as a Connect platform. You should be the one doing it
We could create it but when working with the stripe team during our calls they did not mention this being a blocker. Additionally the other connect account (acct_1OLBxnJte4cqQKEB) in my post works as i would expect, is that just a bug that its working at all?
coral field
Okay, let's ignore this for a bit then but that might explain the overall problem/confusion my colleague had earlier
So now let's look at a concrete example where it failed. All you gave is the pi_123 id but nothing else and unfortunately with Connect that's not enough, especially if you aren't following a "more usual" integration path here.
So what exactly is the problem with pi_3OkXptINSdTE0nGJ0DiPdOhc?
dire eagle
The issue is that when confirming it, it returns a payment_method_configuration id error
https://dashboard.stripe.com/test/connect/accounts/acct_1NpZeCINSdTE0nGJ/payments/pi_3OkXptINSdTE0nGJ0DiPdOhc
specifically this
"message": "No such payment_method_configuration: pmc_1OkBeHINSdTE0nGJdGdPq7Mc"
"type": "invalid_request_error"
When i am using
https://dashboard.stripe.com/test/connect/accounts/acct_1OLBxnJte4cqQKEB/activity?backTo=list
I do not get those errors
coral field
Okay so whenever you confirm it, you must get an exact request id req_123 somewhere in the response, or in Chrome developer tools that would allow me to debug it
dire eagle
ah, would i need to trigger this issue again in order to find that req id or is it available in the dashboard?
coral field
I would say trigger the issue again
dire eagle
ok, going to take a bit to get my local setup again
coral field
All good. I'm trying to find that request in parallel, I think I know what it is and it'd be a real bug due to the way you are integrating Connect (which is tricky to help with if you already had deep discussions with other Stripes during your integration)
dire eagle
Thank you for the help so far, ill get the req id posted. If the issue is super hard to fix or w/e we could create the payment intent in our backend (im guessing like https://docs.stripe.com/connect/direct-charges#collecting-fees without the application fees) if that would unblock us.
coral field
yeah that's what I would do if I were you at least. But we should still debug this issue and see if we can fix it!
coral field
Okay I found some of the requests and I can confirm the "bug" here is because you didn't create the PaymentIntent yourself so it's causing issues.
I do think it "should" work as is, but we missed an edge-case for platforms like yours and it will likely take a while to fix
dire eagle
ah okay, thats good to know, thank you for the info
coral field
Sure thing! I flagged internally for now but you should flag it through your contacts too. And overall I think you'd be better off making sure you always create those PaymentIntents yourself to avoid any issues