i'm working with windows store application and i'm using PayPal Windows8 checkout SDK its working fine for normal payments but i need to make a recurring payment.Let me know PayPal Windows8 checkout SDK is supported for recurring payment?.
https://github.com/paypal/Windows8SDK
It doesn't look like the PayPal Windows 8 SDK supports recurring payments right now. If you go down into the API Reference sheet for C# you'll see there is no mention of a property or event allowing an item to reoccur.
Further, the SDK promotes the Checkout.BuyNow API. BuyNow insinuates it's simply to be bought on the spot, which goes hand in hand with the entire SDK being called PayPal Checkout.
Version 1.0.0 went live yesterday and they seem to have kept semi regular updates in developing for it. I can anticipate reoccuring payments being a heavily requested feature so I'd either check in on it from time to time or find another SDK/API that can help you.
Have fun!
Related
I spent like four weeks coding a plugin to work with PayPal Express Checkout instant update. It was working perfectly in the end with shipping and taxes updating as expected.
However, two days ago, the checkout layout got changed automatically from the classic one to the mobile-responsive version. Previously when I had the callback for instant update defined it automatically used to switch from the mobile-friendly version to the classic version. Now that is no longer the case and the instant update features don't seem to work at all with the mobile-friendly checkout.
Is there anything I can do about it or has PayPal stopped supporting instant update just when I finished my plugin?
I have the same problem..
UPDATE..
After emailing PayPal tech support they finally replied..
Unsupported features
In-Context Express Checkout does not support:
Parallel payments or multi-seller payments
Callback / Instant Update API operations
Billing agreements that use the deprecated SetCustomerBillingAgreement API operation
Seamless checkout for a Log in with PayPal integration
So yes, they stopped supporting instant update with Express Checkout, though they haven't removed the documentation as of yet.
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 am using the Paypal API Payments Pro to set up recurring payments on my website using credit/debit card, everything worked perfect on Sandbox but on live it gives me error DPRP is disabled for this merchant. I have called Paypal several times and all they do is confuse me and they never let me talk to their technical team. i have alreday purchased the additional recurring billing service with Paypal Payment Pro. This is what i get as response from Paypal.
{"TIMESTAMP":"2013%2d08%2d27T17%3a18%3a08Z","CORRELATIONID":"6xxxxxxx65e8","ACK":"Failure","VERSION":"86%2e0","BUILD":"7xxxx78","L_ERRORCODE0":"11586","L_SHORTMESSAGE0":"DPRP%20is%20disabled%2e","L_LONGMESSAGE0":"DPRP%20is%20disabled%20for%20this%20merchant%2e","L_SEVERITYCODE0":"Error"}}
DPRP stands for DirectPayment RecurringPayments. With the old Payments Pro you had to pay $30/mo for Pro itself and then another $30/mo on top of that for recurring payments. Until you were approved and agreed to the additional $30/mo you would get that error. So what it essentially means is you don't have DPRP enabled on your PayPal account right now.
You mentioned that you already signed up for Recurring Billing. It sounds to me like you're on the new version of PayPal Pro which uses the PayPal Manager and the PayFlow Gateway. This is a separate API from DoDirectPayment or CreateRecurringPaymentsProfile. So they've got you enabled for PayFlow, but you're trying to use the old API.
What you need to do is either re-develop your stuff using the PayFlow API or get PayPal to set you up on Website Payments Pro 3.0, which is the old version that used DDP and CRPP. If you tell them you've already developed everything using that API they should go ahead and turn it on for you so you don't have to redo everything. The thing that could be troublesome is the fee structure of DPRP. Again, it's $60/mo when you get it all enabled, but the new one is cheaper. They can redo the fee structure for you to match what you get with PayFlow, and if you can get in touch with the right person, they will, but sometimes that can be tough.
If you have a bunch of trouble getting somebody to help you contact me directly and I can get you in touch with one of my contacts at PayPal that will help you out.
If you happen to be using PHP you might be interested in my PHP Class Library for PayPal which makes the PayFlow integration very simple if you decide you just want to redevelop your stuff.
If you're interested in a better understanding of the different Payments Pro versions you can take a look at this article I wrote not long ago.
In my company we are creating a platform (iOS, Android, Web) that accepts payments via PayPal.
For this we are implementat Express checkout of paypal.
Basically, the solution was implemented until Apple reject the application due to libPaypalEC.a (this uses the UID of the device.)
Once the web version and android run smoothly, is there any quick solution for iOS without the use of the library and any change in the API?
For example, is there any way to get the "drt" without being through the use of the library?
PayPal SDK and MPL are not a solution to my problem, since I find myself in a non U.S. territory and require payment by credit card.
Thanks in advance
The only solution provided by PayPal was to use the Express Checkout instead of the MEC. T only change is that the token(dtr) is sen t null. This library was discontinued by them because of the new Paypal´s SDK for mobile platforms.
My client wishes to keep customers within their site when making PayPal payments. I understand they need to upgrade to a PayPal Pro (or Advanced) account to achieve this. However, before I advise them to do this I want to be sure it won't break their existing website between now and when the new code is implemented. Does anyone know if it is "safe" to upgrade from Standard to Pro without breaking the current implementation or should I advise they create a new account for the Pro integration.
Thanks in advance.
There would not be any issues when upgrading from Website Payments Standard to PayPal Pro/Advanced. You can still use standard and Express Checkout with PayPal Pro/Advanced.