https://stackoverflow.com/questions/20859592
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianShort 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.)
