PayPal NVP - Error Code 10006 - Version Error

[dcordes]

This error code just started showing up today. We are using the PayPal NVP implementation and are currently sending Version = 58.0 in our API call.

Does anyone know what version I should be sending? When I look at the documentation below, "version" isn't even an input parameter, so I have no idea what to do here.

https://developer.paypal.com/api/nvp-soap/do-direct-payment-nvp/

Thanks for any help.

[JoseMiguel7]

We have the same problem but our version is 65.1. We have started logging some errors since October 4th, however today all transactions are errors (Error Code 10006 - Version Error. Version is not supported).

[trepstar]

We're having the same error too.  We think it started happening 10/7/24 after 3PM.  We use old legacy classic ASP and a sample that paypal provided many years ago.  

We're using API_VERSION = "66.0"

[jerrycin]

Same problem here with error code 10006 for NVP. My first one was on September 30th, 2024 and I it has been increasing as some transactions go through and others don't. I was sending version 55 for the last 10 years. Now all transactions get the version error.  I changed my version to 200 and got one transaction through, and now get an 10401 "Order total invalid".  What is even worse is when I go to the developer part of paypal and look at the NVP docs they either come up as 404, or page timeout. Weird that the reference docs came up yesterday but not today, almost like my IP is being blocked on their developer platform or they took them down.  Called the main customer service number and they said they don't offer phone support on the API, they said send message through MTS (Merchant Technical Support) page for support and they will respond in 24 hours.  I sent MTS message with no response 5 hours ago. Wow this company really sucks.  I have been using the PayPal API for CC processing since 2000 with no issues until now.

EDITED: Well with no response or support from PayPal, I just finished converting all my CC processing code over to the new PayPal REST API and got credit cards processing again.  My gut feel after PayPal's non-response to support messages and that they are not even realizing NVP is down, that NVP is done and they won't bring it back. That is why I spent 4 hours implementing REST API today. Good luck everyone.

[dcordes]

Hi Jerry,

Yep, I had the same issue with the documentation yesterday. It would just sit and spin for a few minutes and then eventually I would see "I/O error" on the web page. Really frustrating. Like you said, the documentation is littered with 404s as well. Also very frustrating.

[trepstar]

Can you point me to which version of the papal API functions you used to redo this and which back-end you use?  i.e. which paypal API version document did you use?  We still have old classic asp server side.  Are there any code samples?    I'm not sure how we would plug any of this in.

[dcordes]

This is the API call that is currently failing for us.

https://developer.paypal.com/api/nvp-soap/do-direct-payment-nvp/

We are using version 58.0. We have also tried version 124.0 and 200.0 and both failed.

[sunstarjeff]

We're experiencing the same issue.  I noticed on the DoDirectPayment API Operation (NVP) page, it now has the following message:

https://developer.paypal.com/api/nvp-soap/do-direct-payment-nvp/

Important: PayPal isn't accepting new users for this feature, and we require existing users to upgrade to our Advanced Debit and Credit solution that supports EMV 3DS (3DS 2.0) for PSD2. Our Advanced Debit and Credit solution enables highly customizable custom-card fields and reduced PCI Compliance requirements. For more information, see Set up advanced credit and debit card payments.

Will there be any notice and time to embrace a different API or move to another platform, or Did PayPal just shut off the NVP API without any notice?

Has anyone received a response from PayPal?

[jerrycin]

In response to Trepstar above:

I have an Abobe ColdFusion backend that was using NVP that I converted to REST API yesterday.

Its similar in that you have to POST to a new PayPal url with a new Client ID/Client Secret they give you, get an Access Token back, then create an Order with that Access Token (name, card, expiration), then Capture the order (charges the card).  I just do basic Credit Card processing (pass in the name, number, expire date, amount, description) and its working for me now that I switched.  At some point everyone will have to switch, just wish they would have given me a month warning before killing NVP.

Here are the docs I used

https://developer.paypal.com/api/rest/

https://developer.paypal.com/api/rest/authentication/

https://developer.paypal.com/docs/api/orders/v2/#orders_create

https://developer.paypal.com/docs/api/orders/v2/#orders_capture

Tech support finally did get back to me this morning with the standard "Unfortunately, the behavior which you are experiencing is caused due to some technical issue at PayPal end. Our engineers are currently working diligently on a solution to this problem. At this time, they have not yet let us know when they expect the issue to be resolved, but I have added your account details to our internal engineering ticket for further analysis and resolution."  This message came 20 hours after I messaged them.  They are probably on the other side of the planet, and my guess is the original NVP development team probably doesn't exist anymore and they are scrambling.

[dcordes]

Hi Jerry,

Thanks for notating what documentation you're using. I am also using Adobe ColdFusion.

Was there any sort of approval process from PayPal going live with the new REST API?

I am not confident in PayPal's ability to solve this issue quickly so I might take the same path you did.