Failed orders

same here, some customers warning us they can’t pay, intermitent errors with this plugin have existed during the last months with no definitive solution

after switching back to WooCommerce PayPal Checkout Gateway, one of our customers which was unable to pay when Woocommerce PayPal Payments was active, has finally managed to pay, so this is a clear evidence that Woocommerce PayPal Payments is not working properly

I also experienced these problems throughout the last week. It was incredibly time-consuming to deal with all the issues it’s caused and I ultimately had to deactivate and revert to Paypal Standard while I look for another solution.

Hi,

we have also the same issues, too. Some orders are flagged with Could not process order. Order status changed from Pending payment to Failed nothing else.

Are you guys having the issue specifically with the “card processing” credit card form at checkout? I just responded to a similar post. The Paypal system is being extremely particular with how billing addresses are typed. If something is abbreviated a certain way that the system doesn’t like, it will decline the payment. Very big issue & causing lost sales.

@wooq123 yes, the problem is with card payments. Whatever issue it is, it is rather new one. Didn’t have it until about second half of December last year. Downloaded latest update to 1.6.5 today and the next order came failed again! ??
Does somebody knows if the old PayPal gateway still ok to use?

Hi everyone,

Apologies for the trouble with credit card payments through the PayPal Card Processing.
We are investigating the reports about these failed orders and are working to improve the behavior and extend the error logging for our next update.
As of the latest version 1.6.5, the plugin is fairly strict about processing orders and in return is generous with setting a failed status if not everything went as anticipated during a payment.

Two things we would be interested in:
– Can you consistently reproduce the behavior or does it occur intermittently?
– If it can be reproduced, does the behavior persist with only WooCommerce and PayPal Payments active?

Instrument declined is a response from PayPal that is usually beyond the influence of the plugin as the payment has been declined by the bank of the cardholder. The card could be blocked, or the 3D Secure auth could have failed. For now, it’s difficult to say for us, that’ why extending the logging is a high priority for us. But the PayPal MTS should be in a better position to provide insights about declined payments if you share your plugin log files with them.

Anyway, if you encounter any issues, then the default credit card smart button may provide more consistent results for now while we are investigating with PayPal eventual issues on PayPal’s end. We have seen potential issues with the PayPal Card Processing on more complex sites that have many active plugins. Improving the overall stability and compatibility with third-party plugins is our highest priority for the moment.

But if you have any doubts or concerns, the previous PayPal Standard or PayPal Checkout plugins are still available as of now. But please be aware that both these integrations will soon be no longer supported. They will continue to work on a technical level, but if any questions or issues come up, then upgrading to PayPal Payments will likely be the first recommendation.

Kind regards,
Niklas

If I instruct the customer to use the paypal checkout button and the guest checkout feature, there is no issue with declines (this is if I catch them before they abandon the site entirely out of frustration). When the a card is processed through the credit card form on the checkout page, it’s HIGHLY sensitive to the way the billing details are typed and declines at a very high rate. I cannot find any distinct errors in the log file. However, I do frequently see these lines in the log:

Response Body: {“name”:”AUTHORIZATION_ERROR”,”debug_id”:”3e0f1******”,”message”:”Authorization error”,”information_link”:”https://developer.paypal.com/webapps/developer/docs/api/#AUTHORIZATION_ERROR”,”details”:[{“name”:”REFUSED_MARK_REF_TXN_NOT_ENABLED”,”message”:”This merchant account is not permitted to create Merchant Initiated Billing Agreement”}]}

The logs are riddled with constant “[code] => 201" "[code] => 200" "[code] => 204" messages also.

We are having the same issue on our site with the PayPal Card processing. We have never ran into issues with PayPal standard, but since upgrading to PayPal Payments 1.6.5 we are getting all failed orders. Almost all credit cards are failing on the first attempt, we have only managed to produce a successful payment with a test order after adjusting address details many times. Unfortunately we have just enabled logging now, however we have lost numerous sales since upgrading. We will be reverting back to PayPal standard if possible, until this plugin actually works. Offering the separate card processing without logo is a great feature (the only reason we updated despite the atrocious reviews) but it has cost us too much in lost sales.