back
2 comments
Great story, but I can't help but feel like the Uber Eats dev team was at fault here. Success should only happen when the API returns a success status at the very least. If PayTM was returning an error (as the author states) and they handled it as success, this is definitely bad form on Uber Eats's part. An API is not expected to always return the same error for unsuccessful responses; there are different kinds of errors
How can you accept anything other than explicit success as success when dealing with money? Seems that blame should be entirely on that side.