#Klauz-webhook
1 messages ยท Page 1 of 1 (latest)
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
so this event is the result of a Payment Link
i.e it's coming from someone making a payment via https://dashboard.stripe.com/payment-links/plink_1KQTaSRKGL6J7oUzH9mc19EI
those won't have metadata, since that only exists on the CheckoutSessions that you create yourself via the API
๐ค ok thanks and how does that happen?
how does what happen exactly?
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?
you must have shared it with them
i.e. you created that link on your dashboard, and then you have shared that or posted it on your site somewhere for customers to click and make a payment with it (https://stripe.com/docs/payments/payment-links)
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?
then yeah, it's the Standard account creating their own links probably. You still get their webhook events
you can just ignore them then
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?
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.
well you can do Destination-style subscriptions(https://stripe.com/docs/connect/subscriptions#transfer) where you run the subscription on your platform and just transfer funds to the account instead, but a) that makes you liable for refunds/disputes and b) you generally should only use that model with Express/Custom accounts instead of Standard