codelogix

[hybrid loom]

Do you have examples of this? Is it possible you'r trying to use client secrets for PI that belong to a different account?

(different than the account the PK you use belongs to)

[silk flicker]

https://dashboard.stripe.com/test/logs?method[0]=get&path=%2Fv1%2Felements%2Fsessions&error_param=client_secret&success=false&direction[0]=connect_out&direction[1]=self&created[preset]=7D&ending_before=1678907818-req_MrbwZHlDivKXro

https://dashboard.stripe.com/test/logs/req_yxN2c7rNMo0xZT?t=1678908590

[hybrid loom]

https://dashboard.stripe.com/test/logs/req_MrbwZHlDivKXro

And what payment intent does that client secret belong to?

Are you working with payment intents on connected accounts (direct charge flow)?

[silk flicker]

on connected accounts

trying to find the payment intent

[silk flicker]

I'm pretty sure this is one -> pi_3MlzylL91mzKIzpG1rFvujHQ

[hybrid loom]

Right, yea, that was created using a connected account: https://dashboard.stripe.com/test/logs/req_JezHynJ7IVueET

You need to also provide that connected account id when intializing Elements

using the stripeAccount option when initializing Stripe.js eg:
https://stripe.com/docs/connect/direct-charges#create-a-charge

[silk flicker]

pi_3MeNHWL91mzKIzpG1cH4WHxj

but it shouldn't be a direct charge..we're using the on_behalf_of param for the connected account

[quick token]

Correct, you shouldn't use stripeAccount in stripe.js in that case

Still catching up here a bit. That last PI has a lot of errors from being confirmed after it was already successful but I don't think I see the elements error on it

Also I assume you get this elements error every time you try to initialize elements for this page?

[hybrid loom]

Ah my mistake -- I misread the PI info

[silk flicker]

no worries. it's strange in that it seems isolated to a specific instance, as I was able to make a successful payment intent on another instance, so might be on our end. Thanks for the helpful feedback! I'll follow up if I run into something else.