Which PayPal API and product shall be used for card payments with auth and capture -


how shall integrate custom shopping cart app paypal accept indirect credit card payments without forcing buyers register @ paypal?

there's custom shopping cart web application , task has been set replace current credit/dept card payment paypal. goal let customers pay cards via paypal. however, there constrains:

  1. customers should enter credit cards details (number, expiry date, secure code) not in shopping cart's page, paypal's page,
  2. every payment must consists of authorization (blocking total sum) , subsequent capture if ordered items available , can delivered,
  3. customers aren't forced create / login paypal account if wish pay via card.

the trouble i'm confused number of possible options @ paypal. choice between rest api , classic api isn't problematic, choosing proper product whole list (like classic api products or rest api products) isn't obvious paypal newbie. other similar questions point dodirectpayment (but don't know if it's best choice) or suggest website payments standard (i'm not sure if they're still available). considering express checkout, the demo seems force create paypal account.

expresscheckout designed used in concert direct credit card acceptance method (such paypal's dodirectpayment, or non-paypal credit card acceptance method), although can configured guest payments. why demos of normal configuration handle paypal account creation; that's normal usage.

one key question need ask whether want have access credit card information & "merchant of record" or not.

yes: doing gives flexibility, require go through merchant vetting , carries security obligations (pci) if using solution tries distance actual raw card numbers (e.g. collecting them via paypal or braintree code , immediatly encrypting & tokenizing them). in short: if want full access card, have legal obligations re: handling account access technology can reduce not eliminate.

no: if content treat customer's card information @ arms length through paypal, via legal structure of paypal account (whether user has paypal account or doing "guest" payment on paypal give paypal credit card one-time use) can reduce vetting & security constraints (no pci requirements @ all).

if want (or need) access customer's card [yes above] "classic" api solutions either dodirectpayment (for when collect card info) or hosted sole solution (for when paypal collects card info on page). hss meets 3 of requiremens above; ddp fails requirement #1.

if can live access customer & payment not card account [no above] can use website payments standard, or ec guest checkout option; both meet 3 of requirements.

all of above solutions not still supported, have tens or hundreds of thousands of integrated merchants , biggest/mainstream ways in paypal payments handled.

if prefer newer products & in first category above (real card access, not guest payments) can use braintree or restful apis. these newer products don't yet have flexibility & coverage older products, hey, less complexity can thing long have need. these products designed around plugins web pages rather entering card information on paypal's site, however, don't meet first requirement.

you can payflow (several variants) or adaptive payments or or or.... in general advise picking either well-established or new-and-growing options being better supported & more future-proof.


Comments

Popular posts from this blog

searchKeyword not working in AngularJS filter -

sequelize.js - Sequelize: sort by enum cases -

user interface - how to replace an ongoing process of image capture from another process call over the same ImageLabel in python's GUI TKinter -