On: WePay Drops Prices, Rolls Out White Label Payments API

[aoprisan]

how does this compare to stripe?

[joelrunyon → aoprisan]

It's a less technical solution, but it's been really easy to setup.

Most of my projects from here on out are going to be either utilizing wepay or stripe and staying as far, far away from PayPal as possible.

[susanni_tsunami → joelrunyon]

2nd that. Had a nightmare early on with Paypal, chose WePay and never looked back. Lowered rates makes them now comparable to any service out there, including Stripe.

[lsh123 → aoprisan]

* Full support for platform use case including the easiest possible merchant onboarding and ability to charge "app fee" for services.

* Support for all experience levels from hosted pages to payment buttons to iFrame solution (full PCI compliance) to Credit Card Tokenization (PCI compliance required).

* Simpler Credit Card Tokenization API that allows you to immediately charge the user and store the credit card for later use.

[reitzensteinm → lsh123]

Sorry, but this is bad form.

If you're going to accuse Stripe of not being upfront with its customers, you should at least put a disclaimer that you work for WePay at the top of your post.

Being specific on the details wouldn't hurt, either.

[lsh123 → reitzensteinm]

I've been quoted as WePay employee on HN quite a few times including yesterday :)

Regarding PCI compliance, we have a very different opinion about security and compliance. You can compare these two articles and judge by yourself:

https://answers.stripe.com/questions/what-exactly-do-i-need-...

https://www.wepay.com/developer/security

[tptacek → lsh123]

I don't understand the point you're trying to make with your comparison. Stripe's answer to PCI compliance is "use Stripe.js to make sure credit cards don't hit your server and then send your QSA to us". Yours is...?

Stripe's answer is, as these things go, a very good answer.

[_pius → lsh123]

Full support for platform use case including the easiest possible merchant onboarding and ability to charge "app fee" for services.

IMO, this is the most interesting and differentiated part of the service as compared to, say, Stripe (which I use and love).

Who else offers turnkey support for building your own marketplace, not just taking payments from customers?

[barake → _pius]

Paypal, Amazon and WePay are the only solutions I've found for marketplace-style payments.

[DASD → barake]

Is Paypal considered a marketplace-style payment system?

Two other newcomers are BalancedPayments.com (Gittip.com which has been getting some attention on HN is using them now) and BancBox.com . I have not used either but they are on a shortlist for a project I'm working on.

[bitsweet → _pius]

poundpay.com

[gurglz → bitsweet]

It's now known as balancedpayments

[boucher → lsh123]

Not quite sure what you mean by "simpler," since it would appear to take exactly the same number of steps as our API does to store and then charge a credit card (and with virtually identical parameters).

[lsh123 → boucher]

With WePay:

1) Create "credit card" object from JS

2) Store the credit card ID in your database to charge customer later

3) Charge the customer

With Stripe

1) Create a single use token from JS

2) Create Customer object

3) Store the Customer ID in your database to charge customer later

4) Charge the customer

[boucher → lsh123]

Ah, I see. I was confused by mixing the non JS version of card creation into the middle of your documentation.