• Resolved tougetuning

    (@tougetuning)


    Had a few customers getting this error yesterday although I can’t reproduce it. The failed purchases seem to all have no shipping/billing information passed from PayPal to our website.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor angelleye

    (@angelleye)

    Was this happening with Express Checkout? This error specifically means that the Payer ID was not available. This happens when caching / CDN services are conflicting with the WooCommerce checkout pages. If you’re seeing this a lot you’ll need to configure the caching system in WordPress or on the server directly (or both) so that it doesn’t conflict with WooCommerce in general.

    This is very common with WPEngine hosted sites if that’s where you’re at, by chance..??

    Thread Starter tougetuning

    (@tougetuning)

    Thanks, we are in WPengine and I believe we had them resolve this.

    One thing that’s been a reoccurring thing is that when a customers payment is declined the error shown makes it seem like it’s an issue with our website. It says “there was an issue with the payment gateway” or something to that effect. This is shown when it’s a customer data error such as no avs match, card number incorrect, card type not accepted.

    It would be really nice to have the error messages displayed so the customer knows what they need to fix.

    Plugin Contributor angelleye

    (@angelleye)

    There is an option in the plugin gateway settings where you can adjust the error message to use Detailed or Generic messages. It sounds like you have it set to Generic. If you switch that to Detailed it would display the actual error that PayPal returned to the user.

    Displaying detailed errors to the user on your site can invite fraudsters to use your site for testing stolen accounts / credit cards, though. For example, if they enter a stolen credit card and it fails because of AVS then the fraudster would know exactly what they need to do in order to get that stolen card working.

    Completely up to you, though, which is why we have the option in the plugin. ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Multiple Error Code: 10419’ is closed to new replies.