This is an update on my surprised report of problems with the ebay-paypal connection and how they hadn’t done a proper path for users when an error occurs, as mentioned in the previous article.

A week later they have created such a path.

The error is still occurring for me, but now I get a pretty page when the error occurs (it is still occurring and I still dont know what the problem is), and on this page a link that takes me to the old integration method between ebay and paypal. Exactly what they should have done in the first place.
Except it still doenst seem to work right because when I follow the link paypal considers me a new account, even after I log in, and wants me to enter card details. Thankfully I have found out that if i take 1 item at a time things work…

But to me it is fine - there will always be weird errors and things, and the thing is to not leave the user out in the cold, as I was with a text error pointing me to an unserviced email address…

Although I suspect they havent quite done it the right way, I suspect they have added exceptions to catch the error within the application and handle it within the coded app, but that for any unplanned error people might still be getting the basic text error. I hope not but human nature and development pressures being what they are…

Anyway to me the ideal way is to both
a) check the result of any transaction within the application and catch any error, and handle a recovery path within the application
and
b) not assume there won’t be fundamental errors that the code can’t catch (or that havent been thought of) which then push the user back to the server layer - and to therefore provide a path for the user on these standard error pages when that happens