#Jasperste
rocky lance
slender pilot
Hi! Let me help you with this.
Could you please share an example of each of such events?
undone wedge
Yes. This is an event created by our platform evt_3Nt8kdR0wWrgcTMM19roIfRU
And this is an event created by the merchant by doing something in the Stripe dashboard evt_3Nt8oBR0wWrgcTMM11hdogZi
We are trying to see if we can ignore the latter
slender pilot
I would suggest using the PaymentIntent metadata for this.
undone wedge
How does the page at https://dashboard.stripe.com/acct_1LLkLHR0wWrgcTMM/test/events/evt_3Nt8oBR0wWrgcTMM11hdogZi know the source?
One is source API and one is source dashboard
jade mortar
Hi there 👋 the source associated with an Event indicates where the request that caused the Event to be generated came from. Whether that was a request made by the API, a dashboard action, or an automatic Stripe process.
undone wedge
Yes. I was wondering if you can find that in the event. We would like to differentiate between source API and source dashboard for example when receiving events
We can use the payment_intent.metadata, but it feels like it's already present somehow since the Stripe page knows it as well
jade mortar
Oh, like you want to look at that programatically? I'm double checking, but don't think that's possible. I believe only the dashboard surfaces the soruce information for an Event, I don't think that's available in the API.
undone wedge
Yes. we are listening to events (coming via the webhook) and want to ignore those coming from the dashboard since we are not interested in processing them
jade mortar
Gotcha! Unfortunately I'm not seeing that detail provided in the Event that is sent currently. I think that's a good idea though and will file feedback with the appropirate team that this is something you'd like to see added in the future.