Is there a way to do Friends and Family payments or Peer to Peer payments using the latest version (v2) of the PayPal API? I see that there is a way using the classic deprecated API but am unable to find the same thing in the new one.
The Classic API is not deprecated. It is still very much in use and is continuing to grow, too, as they are still adding new functionality to it. It's not going away any time soon. I would recommend you just stick with it and run your "personal" payments that way.
Related
I am working with paypal first time.
I have a product and I want to integrate paypal with it.
I want to achieve the following tasks :
Client comes to my website and select a plan,which is a monthly recurring plan.
Then client is redirected to Paypal for payment.
Client makes payment.
Return backs to home page.
I have gone through the documentation of paypal and I have the following questions.
What should I use REST API or Classic Sdk, as I want to create Recurring Profile,Work with EXPRESS-CHECKOUT and REFERENCE TRANSACTIONS.
I have customers all over globe and it is stated in the documentation that, for the customers in Germany and China , I have to use REFERENCE TRANSACTION.
Some where in the documentation of Merchant SDK it is stated that the classic API's will be deprecated, so is it a good approach to use Classic SDK
I also wanted to track the transactions(payment) made by user, so that I can show him the amount that is deducted in each month in his profile details.
Please suggest a feasible solution to my problem.
Thanks in advance.
Here's what I use. I went to Web Payments Standard and created a Subscription button. (I like the unencrypted variety, but you can encrypt if you want.) In there, you set the terms of the subscription, as well as where to post the IPN message. When the IPN message comes back, you deal with it. You'll get a subscr_signup at the start along with a subscr_payment. Then, on renewals, you'll get a subscr_payment again. What I like to do is store every verified IPN message in the database for my customer.
For handling the management of those subscriptions for things like tracking info, refunds, subscription cancellations, and voids, you'll need to use NVP API, which is a very simple API. If you stored in a database every IPN message with all those fields, then you should be able to pass certain fields of those to the NVP API in order to get what you need done.
If you're worried about longevity of the APIs, then don't. All they do when they deprecate APIs is stop giving you good docs on them. They still let those older versions run. If they didn't, there would be major upheaval on the web with web commerce products breaking all over the place. However, that said, if you want to prepare for the future, then get on the Braintree Payments API because PayPal bought Braintree and that's the future of their API.
I am working for a company that is using Paypal pro. There are so many Paypal account types, API's, and SDK's that I am starting to get confused with it all. At developer.paypal.com, there is documentation for many different things. What API and/or documentation do I use to start integrating paypal into my website? What is the difference between all these different ones?
Any advice or help would be great, as I am stuck.
Thanks for your time!
Personally, I would avoid the REST API and stick with the Classic API for now. The REST API is very new and doesn't do (much) more than the Classic APIs do. In fact, the Classic API is much more mature has a lot more functionality, which is one of the reasons I still prefer and recommend it.
With PayPal Pro you will use one of two APIs depending on which version you have.
Website Payments Pro 3.0 - This uses the DoDirectPayment API
Payments Pro 2.0 - This uses the PayFlow API.
Payments Pro 2.0 is actually the newer version. If you're interested in more detail on that you can take a look at my article on the History of PayPal Payments Pro.
So those would be for direct credit card processing through your site / application from your own custom checkout page. To add PayPal payments to that, you would use Express Checkout APIs. Specifically,
SetExpressCheckout
GetExpressCheckoutDetails
DoExpressCheckoutPayment
If you are working with PHP this PayPal PHP SDK will make all of these calls very simple for you.
I have looked at the Paypal REST API and at classic API. I like the Direct card processing support the REST API offers and the ability to use the Vault from the REST API.
Only problem is our PayPal sales rep insists the REST APIs are not stable and should not be used and wants us to use PayPal payments Pro with this Class API .
We have a business account and only expect to receive payments in the US, which per this link should be supported just fine. We need to accept payments using a mobile app and website. The mobile app needs to support one time transactions and both (app and website) need to support transactions using stored credit card information (which is where the Vault feature seems really handy).
I clearly see a lot of REST API questions so now doubt its in use.
Question for devs using the REST API over the past 6 months:
has it changed in a breaking manner for you?
Is it reasonably available (99.9%) for your applications?
Does using the Vault REST API feature require a Payments Pro account?
The RESTful APIs would work for you based off of what you stated. Granted they are not to parity with the Classic APIs just yet but the features you were requesting (Direct Card and Vault) are good to go. Pro is not required for Vault with a US account.
Lastly, without knowing the full conversation you had with your Sales Rep, I can't comment on why they felt so strongly against the RESTful APIs. However, if you open up a ticket at www.paypal.com/mts with all of your integration requirements, we can help you out with the best options available.
I am working with PayPal integration for the first time and am confused regarding the two solutions. I need to accept direct payments. User enters credit card information and I use PayPal as the processor. I would also at a later point after release like to add PayPal Express Checkout for convenience. I have PayPal Payments Pro, which assigned me a Payflow account. Which documentation should I follow to accomplish both? There are so many assorted PDFs, many of which are over 100 pages, and I don't have a clear idea where I should start.
I would greatly appreciate a quick separation of services (XMLPay? DoDirectPayment?)
I am using C# / ASP.NET and already have the core and rest api libraries installed in my project via NuGet. I also have an app created and an ID+Secret pair to use.
I have called PayPal but the phone team does not have the proficiency to answer these questions and simply refers me to the documentation site. Hopefully a developer who has been down this road can steer me in the right direction. Thanks!
I would suggest the REST Apis, they support both direct credit card and express checkout depending on which funding instrument (CC vs PayPal) you pass in the pay request.
There is also a C# SDK provided to get you started, all info available at: https://developer.paypal.com/webapps/developer/docs/api/
For anyone running into this post in their search for more PayPal integration information (as I did), the C# REST API wrappers (provided by PayPal) are very useful, and they include full sample projects showing you how to perform most common tasks.
You can find them here: https://github.com/paypal/PayPal-NET-SDK
I used the PayPal sandbox last year when integrating a website with PayPal Pro and it was pretty straightforward. The new and improved version is confusing the heck out of me, though. Nowhere can I find an actual definition for what an "app" is (I'm not kidding, I can't find a definition anywhere) and I'm confused on what I need to do to access the sandbox.
Do I need to create an "app," or just create sandbox accounts?
It depends on which APIs you're using. Adaptive Payments and related APIs (Adaptive Accounts, Invoicing) require a "classic" APP ID. And REST APIs require a newer app to get credentials.
Classic APIs such as Express Checkout and Payments Pro do not require any app; merely an appropriate Business sandbox account.
So, start by figuring out which API you want to use, and then follow its documentation.