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.
What does this mean?
Important: The use of the PayPal REST /payments APIs to accept credit card payments is restricted.
It is not clear. What does restricted mean exactly. Restricted from who? No longer available to new merchants? i have to re-write a bunch of custom code using braintree? We already have a PayPal account using PayPal HERE. Why another service?
Solved! Go to Solution.
I am not sure what PayPal is doing here. I see that they are pushing Payflow Pro or Braintree. Neither option seems to be viable given how easy the Rest API was to implement.
Braintree wants their own UI or Drop In. Why can everything be server side? and Payflow Pro want to conver my PayPal account over to manager.paypal.com. I need to keep using that account for PayPal HERE.
What are my options?!
What about when I store the card as token and then from that card token i do the payment. In that this payment API is going to work. Because right now in my sandbox account everything is working. But on live account it show me unauthorized payment.
Is this problem because of restricted. or I have to enable future payment API and payout API for this??