joe-connect

[weary copper]

Hi what's your question

[valid briar]

hi, sorry hit return too early, have edited original question.

I'm following this guide https://stripe.com/docs/connect/creating-a-payments-page?platform=web&ui=payment-ui&destination-or-on-behalf-of=destination&destination-or-direct=direct-charges&client=react#accept-a-payment

but keep getting the above error when attempting to Mount the Checkout with the returned client secret.

chrome console shows these 404's with the secret

[cosmic sentinel]

joe-connect

[weary copper]

Ok can you share the checkout session id or request id for creating the session?

[valid briar]

sure, here is one ```tsx
"id": "cs_test_a12z2d98qbK9lt6LdeQvcWUptQoQ0gpms6yKXKLMV7h0VW8juaA0H3wjL6"

^ checkout session id

[weary copper]

Looks like our docs omitted something important

So when you do direct charges you pass stripe account header to the checkout session (which you correctly did)

However, you also need to pass this client side when initializing stripe here: https://stripe.com/docs/js/initializing#init_stripe_js-options-stripeAccount

in this section: https://stripe.com/docs/connect/creating-a-payments-page?platform=web&ui=payment-ui&destination-or-on-behalf-of=destination&destination-or-direct=direct-charges&client=html#mount-checkout

We'll get this changed in our docs

[valid briar]

ah ok. so instead of const stripePromise = loadStripe(STRIPE_PUBLISHABLE_KEY); it's missing the stripeAccount? as per - https://github.com/stripe/stripe-js/blob/master/types/stripe-js/stripe.d.ts#L1342-L1347

[weary copper]

yep just add that stripe account param to the call

with the connect account id you used in the session creation request

[valid briar]

great, let me give that a go