#ash_code
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/1387098290939629568
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
Yes you would still use your Publishable key here.
Can you tell me more about what "not working anymore" means exactly?
Are you seeing a specific error?
so when i try to create a connectionToken according to the documentation, it returns a secret. But in our older application, we dont get any secret, instead we get a publishable api key (terminal 3.3.0). When we use this api key as the connection token, it doesnt fetch locations, but when we use secret, it fetches locations.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
earlier, in our old app, it never returned any secret
we used the api key as our connection token
Is this using the Javascript SDK?
android
native code
we checked the github for stripe android
and we found out secret is now mandatorily required to fetch locations
Gotcha, as far as I know you should always have been using your Publishable key to initialize the SDK and then call your backend for a Connection Token.
But I'm double checking
So there are 2 steps:
Init terminal - in which we pass the connection token
This connection token - earlier - publishable api key, now secret key
What do you mean by:
- earlier - publishable api key
You could never create a Connection Token with your Publishable Key... that would have removed the security it provided.
it was possible during 3.3.0
i remember that it was removed for security concerns like u said
so im trying to find a proof of where is it in the changelog
so that i can present to my product team that secret key is needed for the terminal now
can u pls provide that for me? if possible?
I would greatly appreciate it
I'm looking but I don't believe this was ever possible. Do you have a request ID where you created a Connection Token with your Publishable Key?
If this was the case then it would be documented here: https://docs.stripe.com/terminal/references/sdk-migration-guide?terminal-sdk-platform=android
I'm quite skeptical this ever was the case so would love to see an example request.