#thepera
1 messages · Page 1 of 1 (latest)
Hi there
Hmmm so you are starting to see a 500 error on your end when trying to catch a card decline?
Yes, the normal operations still work as expected (like when we use a non declined card the payment intent is successfully created)
Hi 👋 just wanting to make sure we're all aligned here. The 500 that you're referring to, is that being returned by the Stripe API, or is that surfacing somewhere else?
I believe this is the root of the error:
PHP Fatal error: Uncaught GuzzleHttp\Exception\RequestException: cURL error 3: (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) in /app/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:201
What happened leading up to that?
This is the complete logs we have:
url heroku/router: at=info method=POST path="/v7/customers/cus_O4OgesspznfxXX/paymentIntents/create" host=url request_id=2348b78f-04fc-43fd-a0c4-13fc76206216 fwd="70.73.97.77" dyno=web.1 connect=0ms service=1456ms status=500 bytes=221 protocol=https
url app/web.1: [12-Jun-2023 13:31:09 America/Edmonton] PHP Fatal error: Â Uncaught GuzzleHttp\Exception\RequestException: cURL error 3: Â (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) in /app/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:201
url app/web.1: #1 /app/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(105): GuzzleHttp\Handler\CurlFactory::finishError()
I have replaced our url with just "url"
this part:
/v7/customers/cus_O4OgesspznfxXX/paymentIntents/create
just making sure, this is pointing to a Stripe API? If so, I think the v7 should be replaced with v1
ohh no that is our own server versin
oh gotcha, so it's your server that is responding with the 500?
at the end it is correct
Sorry, I'm not sure I'm following, what is correct?
What I'm trying to determine now, is where that 500 is being surfaced. Whether that is being returned to your server by a request it is making to our API, or if it is being surfaced internally within your server's logic.
The 500 is coming when we hit our server endpoint. It seems to only fail when we call the Stripe API for a failed payment and Guzzle errors out when trying to catch the error.
Hm, is the code running on your server crashing when the endpoint is called then?
yes it is
What is the error being surfaced there?