#skammerens-datter_unexpected
limber shoreBOT
👋 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/1481922810061525022
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
clever hollow
Hi! Can I get your account ID please?
hushed yarrow
Yes, sorry: acct_1ITAgFGppVLMkw06
clever hollow
Where are you seeing the error message?
hushed yarrow
Stripe Dashboard -> Developers -> API keys -> Standard keys -> Secret key
It says both "Limited access: This key has not been used to create transfers, payouts, or update payout destinations for over 180 days. This key's access has been limited and cannot be used for certain actions like creating payouts or transfers." and also "Used 17,087 times in the last 28 days" ...
limber shoreBOT
hushed yarrow
In the PHP SDK I am also getting: "Uncaught (Status 403) The provided key 'sk_live_*********************************************************************************************OaqLxZ' does not have access to account 'acct_1Lc8MsGfgc4mQkxw' (or that account does not exist). Application access may have been revoked."
vast sonnet
👋 Hi there! I'm taking over for my colleague. Let me take a look
hushed yarrow
Thank you
vast sonnet
In the PHP SDK I am also getting: "Uncaught (Status 403) The provided key 'sk_li...
So I don't see any payouts or transfers created using that API key in the past three months
Which endpoints are you trying to call and getting an error just now? Is there a request ID in the response?
hushed yarrow
No errors in the request log for the live secret key. Our product Venjue uses that api key for payments using Connect as we are a platform. There are payouts and transfers happening daily using that key...
vast sonnet
Can you share the request ID of a successful payout?
hushed yarrow
I can see that we're POSTing to payment_intents, setup_intents, subscriptions/, accounts/, account_links, and more, but the payout and transfers are happening from the payment_intent itself, which facilitates the transfer, platform fee and payout, rather than an endpoint directly.
If this simply means, that those are still happening, but we are just not able to use the endpoints directly due to us never using the endpoint directly, then there is no issue. But, if the key can no longer do payouts and transfers, that is another story. I am unsure, from the error message, how the key is limited...
Could you tell me its limitations, and if so, if payouts, transfers and platform fees are still working from the payment_intent endpoint?
vast sonnet
Got it, that makes sense. The limitation here is just from explicitly making transfers or payouts. Other functions still work fine, including Connect transfers as part of a payment
hushed yarrow
Okay, so there is nothing to worry about?
vast sonnet
It looks like we placed these limits on the API key at the start of January, so I imagine you would have noticed if it was causing issues
Yeah, nothing to worry about
hushed yarrow
Okay, that is great to hear.
vast sonnet
It's an automated restriction we place on keys, to guard against the case where your key gets leaked or stolen, so that somebody couldn't then move money around
hushed yarrow
Super. Thank you for your help!