#tim_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/1413209516635324426
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
joining in because I'm on the same team here
what's odd, is this account is both a LIVE account and a test account (acct_1JK5wmQISsiW5X09) is this expected?
Hi there
like why is a live account appearing in test mode when we search it? We are able to do test charges with the accounts but the Risk api isn't behaving with it properly?
Yes that is expected -- if you create an account in livemode then you can also take certain actions on it in testmode. It is generally recommended to just use a testmode-only account though for testing.
gotcha, and it's also expected that using that risk/account api would cause issues in this case?
Looking at that... definitely possible that isn't supported in test mode but checking as don't know off the top of my head
hello! fyi i'm taking over for my colleague as he has to run for the day
this is a private preview feature and our team's knowledge on it is a bit limited, but from digging into the code a bit it looks like this is only expected to work with test mode only accounts
it does look like y'all also submitted a ticket around this as well, correct?
the ticket was more just due to thinking the chat on discord wasn't working honestly
I think the issue is that we were testing a live account in test mode
gotcha! if you want to share more feedback on why it looked like discord wasn't working i'd be happy to take that to our team
but since other apis have worked in test mode on this live account we haven't seen this issue until now with this new API
nah, just confusion from the dev who submitted the ticket
and yeah it could be that there are additional restrictions in place due to this still being in private preview
For sure! I think we're all set here - thanks!
i did take a look at the ticket you submitted and passed it along to the right folks so we might be able to get more context on why this is set up with these restrictions eventually too
great! Thanks!