#TomHS
celest plover
Hm yeah that doesn't look right
Can you share a request id here so I can take a look?
gritty nova
req_yF5uZmy8sGkBEb
I can see that the request is made outside of test mode, but I can't see why. I'm using test platform keys
celest plover
Do you have the account id of that oauth created account?
gritty nova
The account was already created, acct_1MpC0fEJn4gk91Tf
waxen pelicanBOT
celest plover
Got it. Give me one moment to look into this now. Discord has been quite busy, so apologies for the delay here
gritty nova
👍
celest plover
Ah ok so this is a fairly common error when attempting to test the OAuth flow, and it can be a bit confusing. The issue here is that you shouldn't t try to activate the account at all when testing the flow. Instead, there is a link at the top of the page that appears only in Test mode. If you use your Development client id ca_XXXX you will see this (attached image) at the top of the page. You can click this button and it will automatically bypass the activation form and continue with the next step of the flow. Then, you will be redirected to your redirect url with a unique authorization code ac_XXXX and your code can finish the connection. Another thing to note is when you go through the OAuth flow, you should make sure that you are logged out of your own Stripe dashboard first.
gritty nova
Oh
Has that changed?
If I try and link one of my older accounts it seems to work just fine
celest plover
With test bank details?