UNPROCESSABLE_ENTITY error at checkout using credit card

  • Resolved A Z

    (@ahmedzeidan)


    2 years, 6 months ago

    Hi there,

    Getting this error at the checkout for 1 random customer, address is complete and no discount is being used. Not sure why this is happening. i even saw the recording and the behavior is normal until the user submits the credit card information to process the order then gets this error. I am using the latest beta release (1.9.3-rc2) to overcome the caching issue explained earlier.

    Failed to process the payment. Please try again or contact the shop admin. [UNPROCESSABLE_ENTITY] The requested action could not be performed, semantically incorrect, or failed business validation. https://developer.paypal.com/docs/api/orders/v2/#error-PAYMENT_DENIED CreditCardGateway.php:405 [UNPROCESSABLE_ENTITY] The requested action could not be performed, semantically incorrect, or failed business validation. https://developer.paypal.com/docs/api/orders/v2/#error-PAYMENT_DENIED OrderEndpoint.php:313 Order status changed from Pending payment to Failed.

    2022-08-31T10:51:31+00:00 DEBUG POST https://api.paypal.com/v2/checkout/orders/4HH94590WY3543251/capture
Response Debug ID: c0df471206d40
Response: Array
(
    [code] => 422
    [message] => Unprocessable Entity
)

    Any insights to resolve this would be great. Thanks.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @ahmedzeidan,

    Are you using the PayPal Card Processing or the standard card button?
    Lately, there have been more reports than usual about the PAYMENT_DENIED error, but I’m not seeing where this would be related to the latest update.
    The best way to find out more about the cause of this error is reaching out to the PayPal MTS with a copy of this log file (primarily the Debug ID).
    The MTS can better judge why the PayPal system would deny this payment.

    In the past, this could happen, for example, when the PayPal security system blocks a payment after fraudulent activity is directly or indirectly associated with the card.
    I can’t tell you which details the MTS can provide for this case, but from our perspective, this error is thrown by PayPal and should not be impacted by different plugin versions. At the very least, the MTS should be able to confirm whether this error was correct to be thrown or not.
    We are working on displaying more user-friendly error messages, but that’s all the plugin could do when PayPal provides this API response.
    But if the MTS does find the integration to be (partially) responsible for this error (which we are seeing right now), please let us know.
    Thank you!

    Kind regards,
    Niklas

    Thread Starter A Z

    (@ahmedzeidan)

    Thanks @niklasinpsyde, this message came back when the user was attempting to use the credit card processor and not the PayPal button. I have contacted MTS and awaiting their feedback.

    Other transactions are going through very well so I suspect that the payment was denied due to another unfamiliar reason.

    Will keep you updated here with MTS response on this.

    Thanks again for the help always ??

    Thread Starter A Z

    (@ahmedzeidan)

    PayPal MTS came back to me with no precise support and they referred me to the normal PayPal support to investigate the error further. Their feedback was that this transaction has a Rejected Payment issue, that is all they said.

    So I guess we can close this support thread, it could be a potential fraud transaction and PP rejected the payment. I just hope that PP would throw back the right error message.

    Thanks @niklasinpsyde again.

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Thanks for the feedback, @ahmedzeidan!
    The MTS is the best contact for all technical questions regarding PayPal. The regular merchant support usually is better at providing payment-, or account-specific support.
    It’s not always easy to judge which department is better equipped to answer certain questions. Additionally, PayPal is often tight-lipped about declines to protect the buyer’s privacy. It’s not necessarily the merchant’s business to know the details of why a payment was rejected as the reject usually happens for a good (but undisclosed) reason.

    The integration displays improved error messages for some API responses, but there are still many “raw” responses (incl. PAYMENT_DENIED) which could be better. For the following updates, an effort is being put into providing more user-friendly error messages & order notes.
    But a fairly generic error is all that could be displayed from the integration level as the causes for the same API response can often vary.

    If anything remains unclear, don’t hesitate to reopen the thread or create a new one.
    Thank you!

    Kind regards,
    Niklas

    Thread Starter A Z

    (@ahmedzeidan)

    Thanks a lot @niklasinpsyde, well said and explained.

    Have a good one… and keep up the great work.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘UNPROCESSABLE_ENTITY error at checkout using credit card’ is closed to new replies.