• Resolved GLWalker

    (@glwalker)


    I recently had 2 orders come in with this error note:

    PayPal Pro payment failed (Correlation ID: a46dfb5be7639). Payment was rejected due to an error: (10434) “10434-Value of Custom element has been truncated.” Order status changed from Pending Payment to Failed.

    Both orders were using PayPal Pro, and on both the customer had wrote an order comment that exceeded 256 characters in length.

    I am assuming that the order comment is the custom element referred to in the error report. I do not know if the order comment passes through to PayPal using the Pro payment method without looking in the code, but again, I am assuming it does.

    I’ve used a jquery snippet to add and enforce a maximum character length on the #order_comments text area and shall await further orders from long winded customers to verify. However, if this is the case, then perhaps the plugin should have a method to add a maximum character length to the comments form?

    Thank you.

    https://wordpress.org/plugins/paypal-for-woocommerce/

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

    (@angelleye)

    Yes, the customer note gets passed into the CUSTOM parameter that PayPal provides because they don’t have a parameter specific to customer notes, unfortunately.

    According to the error, though, it was simply truncated. This leads me to believe the API response came back with a SuccessWithWarning, so the money should have still been transferred.

    Do you have logging enabled in the plugin? Can you provide the log from /wp-content/uploads/wc-logs/ on your server?

    Thread Starter GLWalker

    (@glwalker)

    I did not have logging enabled, I just switched it on and will provide if or when the error happens again.

    The status of the orders was set at Pending, with no record of the transaction recorded inside the PayPal dashboard.

    Plugin Contributor angelleye

    (@angelleye)

    Ok, yeah, please keep logging enabled and provide that if this happens again. I need to see what the actual response was.

    Thread Starter GLWalker

    (@glwalker)

    I have not seen another such error code come through yet, but I see you did make adjustments for such with the latest update. Well done, thank you.

    Plugin Contributor angelleye

    (@angelleye)

    Glad to hear it! Let me know if anything else comes up. Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Error 10434’ is closed to new replies.