4 Commits

Author	SHA1	Message	Date
Matt-Yorkley	e686a4f627	Move raising of errors when payment intent state != "requires_capture" out of PaymentIntentValidator service ... When we're fetching the payment intent via PaymentIntentValidator in StripeSCA#purhcase (to capture it), we want it to fail loudly if it's not in "requires_capture" state. We're now also re-using the same PaymentIntentValidator service to check if payment processing was *successful*, in which case we need it *not* to fail loudly if the state == "succeeded", eg != "requires_capture".	2021-05-16 12:19:04 +01:00
Maikel Linke	fce8d3a2f8	Record invalid payment states for debugging ... We observed invalid payment states in Bugsnag but we don't actually know in which state the payment intent was in. From the context we can guess that it was "succeeded" but it would be good to validate this. And in the future it would be good to know if there are other invalid states we can end up in. The notification to Bugsnag happens in another part of the code.	2021-03-22 16:35:22 +11:00
Luis Ramos	b54b981740	Improve readability of PaymentIntentValidator and cover with specs	2020-03-02 17:30:12 +00:00
luisramos0	95c1b7f7a6	Extract PaymentIntentValidator from StripeSCA gateway	2020-03-02 17:30:12 +00:00