#niravpatil_api
mild ravenBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- niravpatil_api, 13 minutes ago, 7 messages
oblique parcelBOT
đ 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/1242220035712221204
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
signal junco
Hi there
hybrid thunder
Hey
signal junco
Since the authorization was created on a connected account, the approval/decline call should come from the connected account as well. You can use the Stripe-Account header and pass the connected account's ID to approve/decline as the connected account
Still, note that approval/declines via an API call will be deprecated. I recommend looking into migrating to using webhooks for authorizations: https://docs.stripe.com/issuing/controls/real-time-authorizations/direct-webhook-migration
@hybrid thunder just flagging that I deleted your message since it included a secret key. I understand it was a test key but still, we discourage sharing secret keys altogether