[PayPal Direct] PayPal REST API Live issue - using nopCommerce 3.9

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
6 years ago
Hi,

I am now using nopCommerce 3.9.
My PayPal is business account and it's PayPal Pro.
I already generate an app and got the REST API clientid and secret.
It ran well in sandbox environment, but when I turn it to "Live", It failed.

The log shows error message:
Error while placing order. Error 1: Payment error: PayPal error: Unauthorized payment. (UNAUTHORIZED_PAYMENT).

I search the answer thru internet but the solution is limited.
Here's the similar situation Iink with pic for reference.
https://stackoverflow.com/questions/47037283/nopcommerce-paypal-direct-unauthorized

I asked PayPal Technical Support. They reply 2 solutions,
PayPal Payments Pro
OR
Braintree Payments
But I already have PayPal Payments Pro, need guys help here, anyone had the same problem?
Thanks.
6 years ago
Could it be an SSL issue?
6 years ago
I got the answer from nopCommerce Premium Support about this


nopCommerce Premium Support Replied:

we contacted PayPal support in order to make sure that the plugin is outdated. Probably it will not be out of the box anymore.

Meanwhile if you want to use PayPal direct you have 3 choices:

1. Create an integration by yourself

2. Request a quote on the following page - http://www.nopcommerce.com/requestquote.aspx

3. Find a plugin on our marketplace: https://www.nopcommerce.com/marketplace.aspx?searchterm=paypal
6 years ago
We also consider removing this plugin in the next version - https://github.com/nopSolutions/nopCommerce/issues/2876. Still thinking about...
5 years ago
Hi Andrei,
We are using Paypal Direct payment in our 3.4 webshop (ie. customers entering their card data in our webshop not leaving the website)

For those interested: allowing this payment method requires a PayPal Pro account, and PCI DSS compliance, - which is not that difficult as it may sound. It also has the advantage of that being PCI-compliant is also very useful to be GDPR ready (a must do from May 2018) at the same time, many security requirements are overlapping each other.


As PayPal will not support this API anymore (deadline June 2018) we are desperately looking for a solution. We plan to upgrade to 4.0 / 4.1 at the same time.

Could you please give us a clue if you are 'still thinking' to upgrade the plugin (please do it!), or you gave up on this and removing this plugin from 4.1 altogether, so we must look for another solution now.
5 years ago
libor wrote:
Hi Andrei,
We are using Paypal Direct payment in our 3.4 webshop (ie. customers entering their card data in our webshop not leaving the website)

For those interested: allowing this payment method requires a PayPal Pro account, and PCI DSS compliance, - which is not that difficult as it may sound. It also has the advantage of that being PCI-compliant is also very useful to be GDPR ready (a must do from May 2018) at the same time, many security requirements are overlapping each other.


As PayPal will not support this API anymore (deadline June 2018) we are desperately looking for a solution. We plan to upgrade to 4.0 / 4.1 at the same time.

Could you please give us a clue if you are 'still thinking' to upgrade the plugin (please do it!), or you gave up on this and removing this plugin from 4.1 altogether, so we must look for another solution now.


Hello,

We can help you upgrading your nopCommerce website to latest version of nopCommerce as well as we can also offer to integrate PayPal plugin with its latest API support.

Thank you,
Atul
5 years ago
According to the following, in the last sentence there it says the REST API will still be alive and well:

_PayPal currently accepts both GET and POST HTTP methods on our classic NVP/SOAP APIs, used for Express Checkout, Website Payments Pro, MassPay and Button Manager. Starting from June 2018, PayPal will only allow the use of the POST request method for these APIs. This change will not impact the behaviors of our other API products, such as REST and Adaptive APIs._

Source:
https://www.paypal.com/en/webapps/mpp/discontinuation-get-method

Is the GET method the whole issue? It sounds like an altogether different API?

Anyone have a better source for this news and what the official word is?
5 years ago
We were in contact with Paypal and received this blurb today:

"Rest API DCC was already deprecated, which is why we have to whitelist accounts using the product. Anyone whitelisted will be able to process Rest API Direct Credit Cards, with no issues."

Therefore, if you get whitelisted, you should be good, at least for a while. But, I imagine there will be a cut off date for whitelisting and generally doesn't sound like a solid plan moving forward.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.