manytrickssw
Oct '14

Is there any way eJunkie can handle PayPal errors more elegantly? For instance, I've recently had several buyers email me along these lines:



"Hi, I tried to buy your app, and all I got was this:



10486

This transaction couldn\'t be completed.

This transaction couldn\'t be completed. Please redirect your customer to PayPal.

Error



Can you help?"



I did some web searching, and the problem isn't us, it's the user's credit card info in their PayPal account. But that error message is totally useless to a customer. Can't eJunkie parse the error and say something more reasonable?



PayPal has a page on this error, including examples of how it should be handled:



https://developer.paypal.com/docs/classic/express-checkout/htec_fundingfailure10486/



Is there some reason eJunkie isn't doing this? It would make for a much better customer experience.



thanks;

-rob.

  • created

    Oct '14

  • last reply

    Oct '14
  • 1

    reply

  • 1.2k

    views

  • 2

    users

  • 2

    links

E-junkie_GuruWebmaster & Support Guru
Oct '14

Normally we just report the exact error code and message returned to us from PayPal, so you can research that or copy-paste it to us for troubleshooting. Since it appears that particular error has a recommended recovery method, I'll refer this to Development for further research to see if we could handle that more gracefully.