#thomask_webhooks

1 messages ยท Page 1 of 1 (latest)

sharp arrowBOT
#

๐Ÿ‘‹ 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/1275521737718759445

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

tribal flowerBOT
#

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.

sharp arrowBOT
fallow oxide
#

I would familiarize yourself with these docs, as they mostly address each of these questions: https://docs.stripe.com/stripe-apps/events

This is basically just Connect webhooks which are documented in the above docs.
The only difference between regular webhooks and these connect webhhooks is your app will need to request read permissions for each related object (https://docs.stripe.com/stripe-apps/reference/permissions#object) and event (https://docs.stripe.com/stripe-apps/reference/permissions#event)

balmy wharf
#

Everything that is a payment in stripe has a payment intent associated these days right?

obtuse bloom
#

Correct

balmy wharf
#

So I can basically get all revenue listening payment_intent.succeeded

#

And for "negative revenue" I should listen for charge.refunded and dispute related webhooks

#

I should *still listen

#

Like the olden days

obtuse bloom
#

Yep depending on how your integration uses the API, you can choose the events accordingly.

balmy wharf
#

Yeah I'm building an app, so it should work for everyone, regardless on how they're integrated with Stripe

obtuse bloom
#

๐Ÿ‘

balmy wharf
#

I have another question: It is not possible to request optional permissions right?

#

My use case is as follows: There are some cases where we need to access the checkout session. However, the checkout session can expose quite a bit of sensitive information. Would be nice if customers could opt in to specific permissions in order to unlock more functionality. Chrome extensions for instance have a similar system

#

If this is not possible, than I would like to make a feature request for this

obtuse bloom
#

I don't think there's feature for optional permissions today, no..
We can file a feature request.

If you want to track this yourself then you can file it via writing in using our support form:
https://support.stripe.com/?contact=true

balmy wharf
#

Ehm so about my case before. I think it often makes sense to get the client_reference_id from the checkout session. However, I don't see a way to get the original checkout session. I would need its id, which I don't see how to get. The search endpoint also doesn't seem to allow to search Checkout sessions. Am I missing something?

obtuse bloom