#whiteancient_error

1 messages · Page 1 of 1 (latest)

rancid monolithBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1304366620600434749

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

winged ridge
#

Looks like you are still using the test mode API key at your backend

full pond
#

yes, that is supposed to be

#

I am still in dev mode

winged ridge
#

You should use live mode API key in backend instead.

full pond
#

The real site is not up and running yet

winged ridge
#

Are you using live mode publishable key at your webpage?

#

I noticed that you included stripeAccount. Was the checkout session created on the same connected account?

full pond
#

no. The public key is pk_test_df21ZEPtuDHuQaaXXXXXXXXXXXX

#

I suppose it is, since it works on localhost. Could it be different between different servers in a way I do not understand?

rancid monolithBOT
full pond
#

But you see this as a key-problem, not a "you are using the wrong versions somewhere"-problem. Just so I know what to look for?

winged ridge
#

Was the checkout session created on the same connected account?

full pond
#

Yes, the RequestOptions-boject is built upon the same accountId

woven igloo
#

hi! I'm taking over this thread.

full pond
#

As usual with these kind of problems I prolly do something really stupid, I just need help to understand in what area this stupidity is so I can find it.

woven igloo
#

do you have a link where I could reproduce the error?

full pond
#

You need to create an account, but you can fill rubbish, that is no problem

#

it is a test system

woven igloo
#

can you give me a test login/password?

full pond
woven igloo
#

thanks, having alook

#

looks like you are creating the Checkout Session directly on your own Stripe account. So why are you using

loadStripe(data!.publicKey, {
  stripeAccount: data!.accountId
}).

In your code?

#

you should remove stripeAccount.

full pond
#

Ok, so the problem is that I use my own account to test on, on this server. Because the payment should be through Connect!

#

But then I can not try with my own account I suppose

woven igloo
#

well you have to be consistent:

  • create the Checkout Session on the connected account, and also use stripeAccount on the frontent
  • or create the Checkout Session on your pwn account, and don't use stripeAccount
#

mixing the two is expected to not work

full pond
#

Great. Thanks! Very happy for your help. I will use a customer's account to try on and hopefully that will work 🙂

woven igloo
#

happy to help 🙂

full pond
#

of course it works!