Pay Pal’s First Developer Event to Show Off New API
July 6, 2009
Filed Under: in News
Author: Nate D'Amico
Welcome back. XenServer - Software download. Don’t pay for server virtualization. XenServer is FREE.
Online king of payments PayPal has been hard at work on their API for developers to take advantage of. Back at Sun's JavaOne conference last month in San Francisco a PayPal rep cam out on stage to talk up their new developer platform and an upcoming developer event to unveil details to the public.
The wait is just about over as PayPal will be holding their first developer event later this month on July 23rd at their headquarters in San Jose.
Developers interested in payment related solutions should be really excited for what they have to unveil. Leena Rao from TechCrunch was able to get her hands on the following document outlining the new program dubbed Adaptive Payments.
There have been many nipping at PayPal's heels over the past several years. Y-Combinator startup TipJoy, Facebook and their new payment platform, and Google's Checkout team will no doubt be taking notice of what PayPal has in store for developers.
With its huge credit card processing power and expertise as web services Amazon's Flexible Payment Service has so far emerged as a main competitor to entice developers allowing micro transactions down to 1 cent and powerful API abilities for re-occurring payments allowing almost any payment solution to be built on the service. One drawback of the service is that users that are submitting payments have to be signed up in Amazon's database and have a credit card on record.
SiliconAngle Labs will be on hand at the event to bring you more details and partaking in the developer hands-on lab section as well to see what Adaptive Payments is all about.
How has the re-occuring payments system improved?
I've always shied away from it in the past since it's been difficult to get information back from the API that indicated whether the payments had been cancelled.
I think most of the improvements are around the granularity of control that Amazon's, and PayPals soon to be provides.
I havent developed solutions on Amazons payment platform yet but from the looks of the payment API and what they refer to as their 'GateKeeper Language' you just define a payment type of re-ocurring and process the payments. Each payment will return an ID that you would store in a colum in your order table. A job that runs periodically could just poll the service using the GetTransaction call to get any status of potential failure.
[...] service (FPS). This should help steal some developer attention away from PayPal and their upcoming release of their new payment [...]