I'm wondering if it's possible to use Paypal Adaptive Payments in the way that Kickstarter.com are using Amazon Payments to collect/fundraise.
For example: A user sets up a project. People pledge $5 to that project, and if it meets a goal, the system then automatically extracts the money from everyone, and puts it into user who created the projects paypal account. Is this possible using Paypal?
Are there any good PHP libraries supporting Adaptive Payments, if this is possible?
I was also looking for the same answer since I am working on a similar crowdfunding platform as Kickstarter is, but I need to use PayPal.
After a lot of Googling and reading about PayPal's Adaptive Payments API I found out that it's possible by using the Preapproval API and then if the project is funded I can use Chained Payments to send the money to the project creator and to also retain a small fee (a percentage) for using the crowdfunding platform.
If you are looking for some PHP libraries you can found 2 versions at the links below.
One is a library for the CodeIgniter framework and the other one is a PHP API class that can be used anywhere. So, here are the links:
CodeIgniter Library - http://www.binpress.com/app/paypal-adaptive-payments-pro-codeigniter-library/140
PHP API Class - http://www.binpress.com/app/php-paypal-pro-adaptive-api-class/612
I see now that your question is 2 years old, I just hope this answer helps others looking for answers regarding PayPal's Adaptive Payments API.
Yes, it is possible using the Adaptive Payments Preapproval API. When someone 'pledges' would be when you set up the preapproval, and then you can run that preapproved transaction at some future time without any additional interaction required.
PayPal has developed a PHP SDK with libraries and examples to get you started.
If you're going to use PayPal, there's a good Ruby gem: adaptivepayments-sdk-ruby
This answer is a couple of years late but better late than never! The one downside to using the Adaptive Payments Preapproval API for a Kickstarter type of system is that you can't guarantee the "pledge" will be valid when you go to make the withdrawal, since it is possible for the user to cancel their pledge at any time.
I've been working on a crowdfunding project similar to kickstarter. I started out using paypal's adaptive payments for this kind of thing but I eventually switched to wepay's preapproval api. I'm glad I did. For one thing, their documentation is clearer and better organized with good examples in PHP, Ruby and Python.
Related
I'm implementing a PHP Web application that uses PayPal for payments. I'm using for all the things the REST API.
My problem is how can I get the list of withdraws from PayPal API?
I'm going to use the functionality to withdraw to a bank every day, but I will need to see, with the API, those withdraws...
Any idea? I'm a little bit lost after spending two days searching and trying page on google.
Thank you in advance,
Rui
I don't think the REST API supports it yet. The Classic API does, though, with the TransactionSearch API.
Our PayPal PHP SDK will make this very quick and easy for you to setup.
We need to create flexible billing plans for our customers, in which the timing and amount of the billing is flexible and should be determined by us. Just like a "utility bill" but with flexible charge date. Also, there's no purchasing involved upon agreeing of the customer, just his approval for us to charge his PayPal account.
After researching it we decided to go with "referenced transactions". I've read its documentation and the flow seems to be clear.
However, when I attempt to implement using PayPal's PHP REST SDK, I can't seem to find the methods that implement that flow, or some other description on how to achieve our needs using this SDK. For example, I can't find SetExpressCheckout in the PHP REST SDK.
Can anyone point out how we should implement our business needs as described above (1st paragraph) using the PHP REST SDK? I'm very aware of the rather good PayPal REST API documentation.
Thanks!
Unfortunately Reference Transaction is only available with the Classic APIs.
The only similar REST API is called "Future Payments". Unfortunately this API has only been implemented for the PayPal Mobile SDK. You cannot use it outside a native mobile app...
I'm afraid your only solution is to implement the PayPal Classic API with Reference Transaction.
I developed a website that is currently using PayPal Adaptive Payments to manage transactions between different users. I saw that paypal is renewing apis from classic to rest apis. It is really complicated to understand all that stuff. My question is about Adaptive Payments classic api...is there already a rest api that substitutes adaptive payments classic or not? Is there any better system to allow dynamic payments between different users?
Thank you!
Short answer: if your website already uses Adaptive Payments and is meeting your needs there's no compelling reason to switch. The Adaptive Payments APIs will do most of the things PayPal's other, competing APIs do, and some things those APIs won't. Only change if you're redoing your site anyway, or you need specific functionality the current APIs don't offer. You havn't listed any specific gap or need in your question so I can't say more.
Background: broadly speaking, PayPal has developed three generations of APIs:
The original set, including products like Express Checkout, are
pretty squarly focused on web (and mobile) "checkout", the dominant
paradigm of a decade ago for the purchase of goods and services on a
merchant site.
The second set, which includes Adaptive Payments, was
intended to be more flexible (hence the "Adaptive" name) and address
payments that might not be "just" checkouts. For example
multi-merchant marketplaces.
The third set is PayPal's RESTful APIs,
which are designed primarily as a technology refresh to replace
earlier APIs. The RESTful APIs are still being developed and do not
yet offer all the functions of the previous APIs, but are likely to
get more investment and development going forward; as such -- and
because they use newer, more industry-current integration styles --
they may be a good choice for new integrations.
(I work for PayPal and wrote a chunk of the first API set but am not an official company spokesperson, so consider this informed but not authoritative.)
I am creating a website for auctions using Paypal. Clients pay a small fee to participate,
and when the offer falls on someone, the others recover their money.
How do I implement DoAuthorization, DoCapture and DoVoid (NVP) methods in php? I didn't find any tutorial for this case.
Did you take a look at the code samples here? There are PHP samples for all 3 of these on this page, for both DoDirectPayment and the Express Checkout API's. The SDK's are also very useful as they have all of the code samples as well for PHP. Between the samples and the SDK's, these will give you a working example, something to build off of.
This question already has answers here:
Closed 12 years ago.
Possible Duplicate:
Credit card payment gateway in PHP?
I am looking for a solid credit card solution and we are not interested in PayPal. I am currently unsure about the volume of transactions. Someone suggested merchantone but after looking at some reviews i have my apprehensions. Idealling something around a ~2% transaction charge, with some monthly fees.
What do you guys suggest, we need a flexible API which we can utilize easily with PHP. Any recommendations will be helpful.
The Authorize.Net payment gateway API is by far the easiest to use. They provide sample code and there are good classes and tutorials out there, too.
To use Authorize.Net you would need a separate merchant account. There are lots of providers out there and their rates and fees will vary. But all of them work with Authorize.Net. Your merchant account provider can set you up with them or you can choose from any of their resellers to get an account.
I've done custom integrations with PayPal's PayFlow pro, Firstdata (used to be LinkPoint), and authorize.net... and would have to say authorize.net was by far the best to work with. Their API is heaps less complicated than FirstData's (in my opinion), and they generally have better support.
How about Authorize.net?
http://www.authorize.net/
Or google checkout?
http://checkout.google.com