#linqisnice_unexpected
vivid slateBOT
đ 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/1292855360587174019
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
tawdry axle
Hello
What is the full error message that you see?
Ah you are using Connect
Are you initializing as the Connected Account on your frontend?
opaque vessel
Hmm, let me see. Can this be done entirely on the backend? so the frontend doesnt have to change anything?
tawdry axle
No because you are using embedded Checkout
opaque vessel
ok so doesnt this mean the backend needs to return the stripe account id (connected id) to the client? is this safe?
tawdry axle
Yes and yes
No one can access anything sensitive with object IDs without your secret key
So just never share that
opaque vessel
Right ok, so this is likely the culprit?
tawdry axle
Yep
opaque vessel
right! thanks a lot!!