I'm using Stripe Elements plus Stripe Payment.
(Creating a payment intent using serverconnect, then using an inline flow on my button with confirmPayment.)
Card errors are dealt with by the Payment Element, but I can't work out how to handle other errors (like API / network fails).
Following Stripe's guidance docs, they recommend this:
"If an immediate problem prevents an API call from continuing, the Stripe PHP library raises an exception. It’s a best practice to catch and handle exceptions." (https://docs.stripe.com/error-handling#error-types)
Hoping someone can help me out?
The Problem: confirmPayment is run by App Connect, and I don't know how to grab those exceptions. The 'error' handing via dynamic events comes from the returned PaymentIntent data from Stripe, but doesn't seem to work if the call didn't work (api or network error).
You can view the response (with http code) in the network tab, but there's no way to access it in AppConnect that I can find.
(Same as this question, but that was for a SC flow: https://community.wappler.io/t/using-wapplers-stripe-elements-catching-response-errors/58298
It's a php site, and I'm using 7b20. (Can switch back to 6.8 if it helps!)
Bonus question: Is there a way to simulate api/network fails in Wappler? (I'm still figuring out all the things it can do!)