To prepare for the Payment Card Industry (PCI) mandated security upgrade deadline of June 30, 2018, PayPal plans a series of tests to verify that our API endpoints meet the latest security standards. Please see HERE for more details. Please direct any questions HERE
Upcoming Change to PayPal Subscriptions Beginning April 30th, 2018, changes will be made to the way PayPal creates, manages, and displays subscriptions. Click here for an FAQ related to the upcoming changes being made to PayPal subscriptions.
Hello, i am trying to use CreateRecurringPaymentsProfile for subscribe purpose but i am trying to test in sandbox api but i am facing 500 internal server error i am adding following information api:- https://api-3t.sandbox.paypal.com/nvp Method :- post Body :- USER:xxxxxxxxxxxxxxxxxx PWD:xxxxxxxxxxxxx SIGNATURE:xxxxxxxxxx METHOD:CreateRecurringPaymentsProfile PROFILESTARTDATE:2018-23-1T00:00:00Z DESC:RacquetClubMembership BILLINGPERIOD:Month BILLINGFREQUENCY:1 AMT:10 MAXFAILEDPAYMENTS:3 ACCT:xxxxxxxxxx CREDITCARDTYPE:VISA CVV2:123 FIRSTNAME:xxxx LASTNAME:xxxx STREET:FirstStreet CITYanJose STATE:CA ZIP:95131 COUNTRYCODE:US CURRENCYCODE:USD EXPDATE:022023
There are many reasons why an API call to the Sandbox endpoints will receive a 500 Internal Server Error. One of which is if you are attempting Direct Payment Recurring Payment on a Sandbox account that is not setup for Pro or Recurring Payments.
From the Sandbox Account Creation Page on the PayPal Developer site:
Try your API call again after you have ensured that the Sandbox Account is upgraded to Pro. If you receive DPRP disabled, this means that your Sandbox Account is not setup for Recurring Payments.
Since all Sandbox Endpoints were updated to only support TLS 1.2 connections when communicating in https, you will also need to ensure that you are communicating with the highest level of TLS available.
In case you need it here is the information on the TLS 1.2 upgrade.
I have upgraded to pro and enabled but still i am facing this error