#nic.diblasi-Terminal
wraith thorn
clever crane
To be more specific. The connect account was onboarded with our live key and we're trying to create a connection token to the terminal sdk using our test secret key
tidal kettle
Hello! To clarify, is this approach working for other connected accounts, or is this the first time you're attempting this? Also, can you provide the request ID showing that error? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
clever crane
We 've not tested using this approach for another account as this is the first using the terminal sdk. Here is the request id
req_lWXquJhCRVtlI7
tidal kettle
Looking...
Ah, yes, this is expected behavior. Terminal currently requires an explicit test mode connection between your platform and the connected account to create a Connection Token in test mode. This account was created in live mode and has only a live mode connection, so you'll only be able to create a Terminal Connection Token in live mode for this account.
This is something we're planning to improve in the future, but we don't have a timeframe for that change.
clever crane
Ok thankyou for clearing that up for me!