1. Home
  2. WHMCS + PayPal Billing Gateway
  3. FAQ
  4. Clarification on NVP/SOAP API / Discontinued use of GET Method

Clarification on NVP/SOAP API / Discontinued use of GET Method

In Q4 of 2017, PayPal has made some announcements / feature changes to their NVP/SOAP API and Reference Transactions documentation that require clarification from us on how our PayPal Billing gateway remains compatible and compliant with PayPal’s updated API and documentation.

Discontinued Use of GET Method of Classic NVP/SOAP

In the first half of 2018, PayPal will discontinue accepting GET HTTP requests – and only accept POST HTTP requests. Although earlier versions of our gateway did utilize GET HTTP requests, as of v2.6 and later of our PayPal Billing Gateway, we only utilize POST requests, so this announcement doesn’t affect current or continued use of our gateway.

Deprecated NVP/SOAP API

In PayPal’s own words:
While the NVP/SOAP API methods are marked as deprecated in favor of REST API they are still very much supported by PayPal.
The backbone of Billing agreements and Reference Transactions is very much a part of the REST API structure as well as the existing NVP/SOAP structure.
Here is the reference material for REST billing agreements: https://developer.paypal.com/docs/api/payments.billing-agreements

Currently, our REST API does not support Merchant Initiated Billing (Reference transactions). You may utilize the NVP/SOAP API for that. Our Adaptive Payments API has been deprecated and we are unable to create new applications for this. This API, however, is not related to reference transactions. The NVP/SOAP Merchant Initiated Billing still works and any merchant approved for reference transactions can still create NVP/SOAP credentials and use the system.

We apologize for any confusion the deprecation message causes. It only means that we are not implementing new features for that system at this point, but we are still supporting it and all current features work and are still available.

We are working on allowing reference transactions via the REST API and that will, hopefully, be available in the future.

Updated on December 26, 2017

Was this article helpful?