#clydstrife_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1367010707622854737
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! Can you share the connected account id for me to take a look? It will have the prefix acct_
sure
acct_1QoU24I3xVLFKN7u
Initially, I implemented the solution using the Platform account, and it worked well. However, the client wants to switch to using Direct Charges on the connected account. During this transition, I encountered an error while trying to fetch the connection token. It seems that the implementation differs significantly between using the Platform account and the Connected account. Which is why I'm reaching out for help on how to do this.
gimme a while to get back to you!
No worries, really appreciate it
so the thing is that this connected account is only connected in livemode right now. If you want to test, I would really recommend that you create and onboard a new account in test mode instead.
If you really want to use the same connected account but in testmode, you'll want to take a look at https://stripe.com/docs/connect/oauth-reference
Oh so if it was in Live mode this error wouldn't have shown?
yep, if it was in livemode this error shouldn't have shown
oh that's weird, is this intended?
It's not exactly intended, but it's somewhat of a known issue with using Terminal and connection tokens and direct charges
Ohhh I see gotcha, I'll try it in Live mode while I create and onboard a new account for test mode then. Thanks for the help.
alright, feel free to reach out again if you're still running into issues!