I am looking into implementing Paypal Standard Payment product. The basic reason being "offsite payment" (i.e. we dont want payments being captured at our own site, but on paypal's own payment page via redirection).
However, previously I used to get it done via (now called) Classic API.. I wounder if the new REST API supports this offsite / paypal redirect standard payment method? This is because there is no mention of these classic products names on the REST documents (instead, they are listed in Classic API section only)
Secondly, does Paypal Standard (even via REST) support Direct Card payments? or only Paypal Account payment?
Thanks.
REST does not encompass all Classic API features. It's mainly for mobile development (although not exclusive to that), using OAuth, which is more familiar to mobile developers. Payments Standard is not an API product at all but it can be used in conjunction with API calls to a limited extent. Classic API has the Button Manager that lets you set up custom encrypted buttons that can start a Payments Standard payment.
REST does support direct payments and supports almost everything Classic does in that regard.
Related
Is it possible to attach payment methods to customers when PayPal uses the card checkout? I'm asking this because it seems like in order to have the PayPal buttons on the checkout, trying to use PayPal's hosted payment fields seems to not support having external customers with saved cards.
My goal is to have it so I can have the PayPal button along with the PayPal hosted fields for cards, and then if a user does checkout with the hosted fields, it will save their card somehow. This sort of functionality doesn't really seem to be supported by PayPal's API according to the docs unless I'm missing something.
I'm just trying to figure out a way if you can use previous cards in paypal's hosted checkout if that is possible.
Saving payment methods requires a feature variously called reference transactions or vaulting (the v2 vault API, not v1). The feature is not enable by default. The business owner should contact PayPal's general business support (not technical support) or an account manager to inquire about the reference transactions feature and explain the business need.
If approved for the feature, PayPal can then guide you on which API to integrate.
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've been asking myself if there is a possibility to use the standard payment page of paypal to redirect user to "Authorize" a payment using their Credit card (using "paymentaction" : "authorization" in the redirect form).
Having IPN setup i could receive the auth_id.
Then later on "Capture" an amount (equals or less) using the Paypal REST API but using the "auth_id" received through IPN ?
It seems the "authorization_id" received through Paypal REST API "Authorize" is the same length. Somehow i suppose it is the same value.
Before implementing such i wonder if anyone tried this before ?
Thank you
You can do this using the standard (Website Payments Standard) page to creat the authorization paired with the "classic" authorization API, but you cannot mix the classic and REST APIs as you described.
The REST APIs store different/additional information on PayPal's server side, so in general you cannot manipulate transactions created through classic APIs via REST APIs (and vice versa is also complicated and generally not advised).
I am a bit confused about the REST and Classic API and which one serves my business case best. My requirement is to be able to send money to one or many customers by just using their email addresses. No need to receive Payments, just to send...Additionally i do not want approvals, i just want to send the payment and the payment to be executed, since i am performing a receiver email validation via the getVerifiedStatus call.
I know there is the Mass Payment option and the Adaptive Payments option however for consistency i need to use only one API. Which API covers my needs?
This isn't yet covered well by PayPal's new REST APIs. But the MassPay api (with # of payments = a set, or just 1) can definitely do what you want. Check PayPal's handling of exception cases that is built into the MassPay product to ensure it meets your requirements; if it does then this is a great answer. The adaptive payments pay() can also definitely work; to determine which works for you will require evaluating the underlying PayPal products moreso than the APIs. They do NOT work entirely the same way....
I would stick to classic API for now as it's much more mature than the REST API is. For your situation I'd go with Adaptive Payments, specifically the Pay API. Since you are the app owner and the payer, you can simply trigger payments however you want to anybody you need.
In my application I have implemented the Paypal website payment standards. But when I use it I can't retrieve details for recurring users. Can I use the API to do the job? Is this a valid or meaningful method?
no you can't retrieve the standard subscription. But you could use the paypal API to make the recurring payments.
http://www.codeproject.com/Answers/526264/How-to-create-recurring-profile-with-express-check#answer1
the above link will provide you the code to create it.
Tip:-
The mentioned code first create a Sales account and then convert it in to the recurring account
With standard subscriptions you can't access those via the API. If you want to work with subscriptions via the API you'll need to use the Recurring Payments platform instead of Payments Standard.