#claudius_api
regal boneBOT
👋 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/1404454989270880316
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
plain gull
Hi, since you're not integrating with Stripe directly I am unable to assist further here, https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/stripe
You will need to reach out to them directly as a next step as Chargebee owns the integration. We do not have much control since they own this integration.
void hamlet
Hey @plain gull , thanks for the quick reply. I'm aware of your and CBs docs. But apparently CB is not.... My hands are bound, I can't do anything myself.
Can you please extend the deadline?
plain gull
I can't do that I'm sorry, we are not able to offer any extensions. Please re-connect with Chargebee on this
void hamlet
Can you point out problematic payments? CB claims they migrated everything. I'd like to give them some tangible homework. Or are you sending those deprecation warnings indepdently of actual setup?!
plain gull
You can look at the Dashboard under the developer section to find these. I see https://dashboard.stripe.com/logs/req_60OGoQddZworHe for instance.
void hamlet
but that's a credit card payment, isn't it? those are affected as well?!
plain gull
You're right, that should not impact. I went through more logs but I think your best next step is to reply to the email that you recieved to ask for an example here.
regal boneBOT
void hamlet
your mails are coming from notifications@, which is apparently another name for noreply@ 😉
forwarding it to support@ leads to the same auto-reply. there's no way to contact stripe with context (anymore).
rancid cypress
Hi there 👋 jumping in as my teammate needed to step away. I'd suggest reaching out to our Support team to start a support case for this matter:
https://support.stripe.com/?contact=true