#matt_error
zinc breachBOT
👋 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/1364274580293681242
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
kindred delta
This usually happens when you're using older version of curl in your server. Could you try updating the curl version in your system?
icy grove
Sure, but can you explain why it is the case that this would have suddenly started happening?
kindred delta
Stripe SDK doesn't handle empty POST fields in older curl versions. The issue is likely the some instances in your server running on the older curl version whereas the those successful ones were on the newer curl version. This is a known issue: https://github.com/stripe/stripe-php/issues/1817
icy grove
We only have one server, and our curl version has not changed, so these facts don't align with the theory
kindred delta
Could you share which curl version your server is using?
icy grove
I don't have direct access to that information, but let me see if I can find it. Give me a little while
kindred delta
Sure! Let me know the version when it is available. You should be able to check by executing curl --version on your server, not local machine
icy grove
I don't have direct access to our production environment, so I'll have to check with our devops team.
Are you able to see the failed requests on your end?
If so, can you give us more info on them, since they don't show up on our dashboard so I can't see what data you're actually receiving from us
kindred delta
I don't see any 400 error for the detach API on your account in the past 7 days
icy grove
Okay, looks like it'll be about 30 minutes until I can get confirmation of the curl version
I can rerun the request right now if that'd help
Done
Request would've been a detach of pm_1R7sWCIVLuRzysjdP0ijXtvj
delicate spruce
Hi @kindred delta sorry for asking here. But does stripe provide Mbway payment method in Portugal?
kindred delta
Thanks! Let me check if I can find anything internally
zinc breachBOT
@delicate spruce looks like you're in the wrong place, this thread is for someone else's question.
- If you have your own thread please chat there.
- If you have a question or a followup to a closed thread use one of the buttons in https://discord.com/channels/841573134531821608/842637025524842496 to get help (we don't reopen closed threads).
Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.
icy grove
Thanks! Let me check if I can find anything internally
Sure, thank you
delicate spruce
How do I create one ?
delicate spruce
It's taking me to website with email
Looks like they automated everything now , before there used to be groups
kindred delta
@delicate spruce This channel is for technical integration questions. For the question on whether a payment method is supported in a specific country, please follow the instruction in #help to reach out to Support at https://support.stripe.com/contact
icy grove
Hey Mani, I understand that you want your question answered, but I'd appreciate it if my thread could be reserved for resolving the issue I'm addressing.
It seems like your question may be answered by looking at the docs here though: https://docs.stripe.com/payments/mb-way
If you need more help with that question, could you please direct those to your own thread or support via their email at
kindred delta
@distant river Checking our internal logs that it looks like your request didn't make its way past nginx, that explaned why it did not reach to Stripe server.
The 400 error was likely returned from nginx instead of Stripe API
icy grove
Ahh, yeah. Guess that explains why it didn't get into the logs
to be fair, the error says as much about it being returned from nginx
kindred delta
Ya! It'll be helpful to share your curl version in your current server, so that I can compare with one in your past requests
icy grove
Sure. I'm waiting for our devops to get into the office so I can get that info for you. I appreciate your patience and assistance
kindred delta
No problem! Happy to help 😄
icy grove
Are there any other issues you can see on your end for requests that aren't making it through nginx? I'm concerned that there might be other problems we're not seeing in the logs for the same reason
kindred delta
Only when the request makes through nginx and reaches Stripe, then we will have logs on our end. If the request doesn't make through nginx, we don't have any way to debug the issue unfortunately as the issue stays within your server that we don't have any visibility.
icy grove
I see, okay.
Looks like our devops just got in, so I should be able to get that curl version for you in a minute or two.
Side question though, we're seeing a lot of failed payments due to mandates not existing for payment methods migrated from sources via the automated tool. Is this expected for all of the migrated sources?
Alright, here's the curl info:
Curl RPM packages:
curl-debuginfo-7.29.0-59.el7_9.1.x86_64
libcurl-devel-7.29.0-59.el7_9.2.i686
libcurl-devel-7.29.0-59.el7_9.2.x86_64
libcurl-7.29.0-59.el7_9.2.x86_64
curl-7.29.0-59.el7_9.2.x86_64
python-pycurl-7.19.0-19.el7.x86_64
libcurl-7.29.0-59.el7_9.2.i686
Result of curl --version
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.90 zlib/1.2.7 libidn/1.28 libssh2/1.8.0
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz unix-sockets
Ah, interesting. Same curl version as the issue you posted earlier.
zinc breachBOT
kindred delta
This curl version is the same as those on successful detached requests, e.g. the last successful one - https://dashboard.stripe.com/logs/req_x4zSpU7YJyCCii
However, you had SDK upgrade from stripe-php 15.9.0 (pinned to Stripe API version 2024-06-20) from stripe-php 16.5.0 (pinned to Stripe API version 2025-01-27.acacia). The one that failed had identical error as the issue reported using 2025-01-27.acacia on curl 7.29.0
icy grove
I see
Alright, I suppose I'll try to implement the fix noted in the issue you posted above to see if that resolves the issue
kindred delta
In your test env, are you able to reproduce the issue?
icy grove
Unfortunately, no because it's not identical to production so this is just guess-and-check development :x
kindred delta
Will it be possible to upgrade the curl version in production server to check the issue can be solved?
icy grove
Possibly, but that might cause other unforseen issues
kindred delta
From the thread, upgrading to curl 8.7.1 should solve the issue. I tested this curl version on my local machine and this code works fine