#Klauz-webhook

1 messages ยท Page 1 of 1 (latest)

jovial lion
#

hi, can you share the specific event ID evt_xxx instead?

mellow badge
#

Sure, here is the last one: evt_1KQTgXRKGL6J7oUznCipMVy3

#

failing ^

#

and here is the last one succeeding

#

evt_1KRC8CRIhFORG6XepkBwmG5i

#

I suspect that the ones failing are retries

jovial lion
#

those won't have metadata, since that only exists on the CheckoutSessions that you create yourself via the API

mellow badge
#

๐Ÿค” ok thanks and how does that happen?

jovial lion
#

how does what happen exactly?

mellow badge
#

where did the users get those links?

#

we're only using checkout sessions in our integration, is there some automatic process on stripe side that sends emails with the link maybe?

#

if so, in which cases?

jovial lion
mellow badge
#

pretty sure we don't do that

#

since I can't access the payment link you sent, and other in the events I'm assuming it was created on the user side

#

does standard accounts have that power?

jovial lion
#

they do, yes

#

ah ok, didn't realise Connect was involved here

mellow badge
#

sorry my bad I did not mention it

#

yes it is in the connect context

jovial lion
#

then yeah, it's the Standard account creating their own links probably. You still get their webhook events

#

you can just ignore them then

mellow badge
#

ok thanks for the answers, this is getting a bit messy

#

because we have subscriptions management on our side and turns out a standard account can do it on their side too

#

and we still receive some of that ๐Ÿ˜ฌ

#

like they can archive products/prices etc too

#

any way to prevent it?

#

since it's connect we create those objects on their behalf, maybe we should hold them on our main account?

jovial lion
#

not really! The subscription runs on their account and they have some level of control over it. It's not really in their best interests to archive your products though, so not sure why they'd do that.

jovial lion
mellow badge
#

spot on, we used to do that exactly with express but had to switch to standard bc of liability indeed

#

ok cheers for the help, will just ignore all of this ๐Ÿ™ˆ