#pitxardo_code
indigo nightBOT
👋 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/1245017892056076413
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
abstract notch
Hi 👋 what is the error you're seeing?
abstract notch
@digital garnet checking to see if your still around to tell me more about your concern?
abstract notch
Hm, that doesn't tell me as much as I'd hoped 😅 does the new key belong to the same Stripe Account as the old key?
digital garnet
yes, same account
so, if I use the URL from original message with the Secret API Key, it works, but if I replace by a generated RAK, it fails
abstract notch
Found mention of the error here:
https://docs.stripe.com/connect/oauth-reference#post-deauthorize-error-codes
My guess offhand is that RAKs may not be supported there.
digital garnet
mmm....
I'm just trying to change this because I got an email few months ago saying that Stripe will require RAK for all gateway connections with Spreedly
abstract notch
I don't think that's referring to this part, unless you're the one maintaining the Spreedly provided integration.