Which should I implement first, PayPal or Google Checkout, on my eCommerce website? [closed]

问题

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 6 years ago.

Paypal and Google Checkout will take some time to implement so I'm wanting to know if anyone in the community has installed them and has a recommendation on which to do first. We use the .Net environment.

Verdict - Start with Google Checkout

• Great customer support,
• Great multi-language libraries,
• Simple, fast web interface.

Add Paypal Later

• More established, but sketchy reputation,
• More steps in checkout process than Google
  • Google - from merchant to Google
  • PayPal - from merchant to Paypal and Back to merchant (with express checkout)
• Varying-speed web administration tool that has many unorganized features buried

回答1:

Idealogically? Google Checkout. PayPal's customer service practices are awful.

Practically? PayPal. Shitty customer service aside, they're the closest thing the Internet has to a universally accepted payment solution.

回答2:

Paypal has more active subscribers, so you are more likely to convert more sales. Google Checkout is newer, and although many people have Google Accounts they haven't been converted into checkout customers, mainly because there aren't enough online stores that have implemented Google Checkout. Chicken and egg scenario (for Google).

From a developer's perspective I would say you are in for a similar experience regardless of which you choose. There are more developer resources and examples out there on the web for Paypal, simply because it has been available for a lot longer. Paypal offers some relatively simple integration options and google Checkout offers some rather nice order management tools that Paypal doesn't.

When using the Paypal testing suite, you'll find it clunky and a little painful, hence the original comment that was chosen not to be an answer:

Enjoy PayPal's sandbox test environment! It's about as fun as extracting one's teeth with a pair of pliers.

回答3:

Paypal is by far the most known. Choose depending on your user base of course, but if you should market it for "everyone", make Paypal available first.

回答4:

I used Google Checkout because it integrates with Analytics very tightly.

I just used the simplest way of integrating using HTTP POST requests to forward the last stage of my cart to Checkout.

Takes about 30mins to integrate it that way, though there are more complex ways to use it behind the scenes.

I found the admin interface simple but effective, and being able to analyse sales alongside user data is invaluable.

回答5:

I would suggest PayPal for it's ease of use and good developer docs. API access is gained using either NVP/HTTP or SOAP.

There are basically four services:

1. Website Payments Standard
   • transaction processed on PayPal's site
   • no need for PCI compliance or worrying about mishandling CC numbers
2. Website Payments Pro
   • includes Express Checkout (PayPal customers can check out at PayPal using their stored information such as billing and shipping addresses)
   • includes Direct Payment (accept payment info on your site and send it to PayPal via the API for processing; your customers are not aware of that backend transaction to PayPal)
   • you handle CC data and therefore must meet PCI compliance
3. Payflow Link
   • payment gateway where the processing takes place on PayPal
   • similar to Website Payments Standard
4. Payflow Pro
   • payment gateway where the processing takes place on your site
   • similar to Website Payments Pro

回答6:

At one point I was really upset with PayPal's user flow vs Google's -- but then I cleared my cookies and learned that the user-experience on both systems is almost exactly the same.

They both cookie people who have used them in the past , and present a different UX to the users based on that.

If you've used PayPal before or have a Google Account cookie ( ie: gmail or analytics ), then your users have one UX. If you don't, your users have another UX.

People with no Google accounts will be prompted to register with Google, just as they would with PayPal. TheDevelopers tend to have a Google account -- so they'll see the more streamlined option.

回答7:

Paypal because a bigger share of internet users know it or already have an account. Don't look at the cut they're keeping, look at how repelling or not it will be to your potential buyers. Better have 2 customers with a bigger transaction fee than only one with a smaller fee IMHO.

Also I might be mistaken, but I think that creating a user account is optional when paying with paypal whereas I think it's mandatory for google checkout. Nobody likes creating accounts everywhere.

回答8:

I use PayPal for my business website, and it works very nicely. PayPal is more popular than Google Checkout, so people are familiar with it. Also, you can pay/checkout using a Credit Card without creating a PayPal Account. I don't know if Google Checkout requires you to register before you can make payments.

回答9:

I'd like to say Google Checkout, but I also have to second Paypal. I believe they have a larger market share at this time.

回答10:

I found it pretty easy to integrate with Paypal, so it might take as long as you expect to complete those two.

/Allan

回答11:

I don't like paypal either, but they make it really easy to integrate into existing systems.

来源：https://stackoverflow.com/questions/67394/which-should-i-implement-first-paypal-or-google-checkout-on-my-ecommerce-websi