#nel
1 messages ยท Page 1 of 1 (latest)
Can you share an example request where you see this error?
https://stripe.com/docs/api/request_ids / https://support.stripe.com/questions/finding-the-id-for-an-api-request
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
eg req_123
Sorry @karmic scaffold but any request to that account ends in 403 and there is no request id in that case...
Gotcha -- can you share the account id?
The account id is : acct_1M6c7qQM849fSYpD
Ok thanks, looking at this.
Can you share an example request snippet (the code you're running) -- make sure to remove any secret keys or private info
Is it possible you're making the request using keys for another account you have access to, rather than the account this express account belongs to?
If I'm using another account (listed in the connected accounts) it works fine.
Example with request id : Request-Id: req_paDD4gI44XzxwV
As an example of failure (but all requests related to the account will fail) this request fails:
http -a s_k_l_i_v_e_XXXXXXXXXXXXXX: https://api.stripe.com/v1/accounts/acct_1M6c7qQM849fSYpD
๐
Sorry for the delay! Taking a look
Okay so yeah looks like you are using OAuth here
And I can see on that account an internal error that we log that indicates the OAuth Token was consumed twice by your integration. When this happens, the account gets disconnected from the platform
Which is why it seems that it is "deleted"
We highly recommend using Connect Onboarding flow (https://stripe.com/docs/connect/express-accounts) instead of OAuth as it immediately solves this issue since you are creating the Account instead of connecting it via OAuth
However, if you want to keep using OAuth then you will want to debug your integration to ensure you aren't consuming the OAuth token multiple times.
@fluid salmon tagging you just to ensure you see the above info
I'm not sure to understand how we can "consume" and what triggers this "consumption", I'm going to investigate.
Thank you for your answer, I may get back here with more information.
Sounds good. The "consumption" of the token is this step in the flow: https://stripe.com/docs/connect/oauth-express-accounts#token-request