#conor_23723

1 messages · Page 1 of 1 (latest)

inner summitBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

native bronze
#

@swift wraith we just talked via an old thread and you were working on figuring out your syntax error.

swift wraith
#

I figured it out

#

But now have a new error

native bronze
#

What's the new error?

swift wraith
#

Not exactly sure what the problem is

#

I double checked the API keys and they are definitely the correct ones

native bronze
#

What is the Checkout Session ID that was used?

swift wraith
#

I will re run my app and add a console.log to check

#

Wait sorry - there is no checkout session id from my app - I am using the client secret to render the checkout

#

This is the client secret id that was generated - cs_test_b1Gb6EM2tk8wgpTutbWopywLAk9auRcTZKGV9n3vQZRlkjgVs3JPxW5X8H

#

But checkout id is not generated anywhere

#

Or if you know how I can log the checkout session?

native bronze
#

That's fine, I can use the client secret

swift wraith
#

perfect

native bronze
#

It looks like this was a Checkout Session created on a Connect account, so you probably need to authenticate your API calls as that connected account: https://stripe.com/docs/connect/authentication

I'd start by doing that client-side, since that's where the error is coming from: https://stripe.com/docs/connect/authentication#adding-the-connected-account-id-to-a-client-side-application

Learn how to add the right information to your API calls so you can make calls for your connected accounts.