#josh-checkout-connect
idle osprey
Do you have a request ID for the request that failed?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
lilac ravine
Unfortunately these failures don't even seem to be showing up in the logs to get that request id, maybe this will help? This is the request log url https://dashboard.stripe.com/test/logs/req_nkaDttzd15FJq4?t=1702503831
idle osprey
Ah, okay. So the Checkout Session was made by the platform for this Connect account --> acct_1OID9uBlJtihPmkM
But you're trying to use it with this Connect account -->acct_1OAJ0iIyQopaXRtU
lilac ravine
So acct_1OID9uBlJtihPmkM is the connected account and acct_1OAJ0iIyQopaXRtU is the platform account. We are wanting to make a direct checkout session to acct_10ID[...] and have the fees paid back to acct_10AJ0[...] does that make sense?
So we're using the apii keys from the platform account and specifying the acct_10ID[...] account in the checkout session creation to enable the direct charges model.
That is what I thought I understood to be the approach from this documentation: https://stripe.com/docs/connect/creating-a-payments-page?platform=web&ui=payment-ui&destination-or-direct=direct-charges
idle osprey
Yeah, so you need to pass the Connect account's Account ID in all your Checkout Session API requests to ensure that it's being used on behalf of the Connect account. That's what's tripping you up here. This request that you sent me req_nkaDttzd15FJq4 doesn't have the Connect account's ID as a header, so Stripe assumes that the Checkout Session is on the platform's account
lilac ravine
Ok, that got it for me, thank you! Your team's support is fantastic!
idle osprey
Happy to help!
stray burrowBOT