#flyingzergling_webhook-sub-cancel-source
tired nightBOT
👋 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/1448761564172779751
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
mint wadi
Hi 👋
Do you have a more recent example event? we don't store logs for events longer than 30 days so I can't see the event payload
Unfortunately there isn't a clear way to identify if the cancelation comes from the Customer Portal. One thing you could do is append metadata to the cancellation requests that you generate using the API. that way you can at least differentiate those requests from the rest.
timid sierra
Ok, the tricky thing is we have three channels. If we add metadata to our API, we still cannot differentiate cancellations from stripe customer portal and chargedesk
mint wadi
Correct. I don't know what the integration with Chargedesk looks like and whether or not it would support adding metadata there too
timid sierra
Ok, I will discuss with my team and see what we can do with chargedesk. Thank you for your help.
mint wadi
Happy to shed what 💡 I can 🙂
tired nightBOT