When comparing Wepay vs Stripe, the Slant community recommends Stripe for most people. In the question“What are the best online payments APIs?” Stripe is ranked 1st while Wepay is ranked 2nd. The most important reason people chose Stripe is:
Stripe is very simple for developers to integrate into their application as it is a "works out of the box" solution with a fantastic API. The Stripe API is incredibly simple to setup, for example creating a new charge with Ruby is simply: require "stripe" Stripe.api_key = "vtUQeOtUnYr7PGCLQ96Ul4zqpDUO4sOE" Stripe::Charge.create( :amount => 400, :currency => "usd", :card => { :number => "4242424242424242", :exp_month => 1, :exp_year => 2014, :cvc => 314 }, :description => "Charge for test@example.com" )
Ranked in these QuestionsQuestion Ranking
Pros
Pro Advanced Fraud Detection
WePay has developed world-class technology for detecting online fraud which takes the burdon off their customers. WePay utilizes their users social presence to establish identity and reputation which enables them to optimise risk and availability of funds.
This results in fewer instances of merchants having to deal with chargebacks and drastically reduces the need to freeze accounts.
Pro Full Featured
Not only does WePay offer an API but they also provide a fully featured set of embeddable payment buttons. The payment buttons enable you to accept donations, sell tickets and host a store.
Unlike Paypal, everything (including the checkout process) happens on your site, which helps to reduce churn by up to 50%.
Pro Customer Service
WePay takes a more holistic approach to customer service when compared to competitors such as Stripe as they provide full support to developers and payers.
WePay has a great reputation for customer support and have a dedicated team to support their users over phone, live chat, and email.
Pro Simple Integration
The WePay API is simple to integrate yet flexible enough to handle multiple use cases. The API has the following use cases:
Traditional Payment Gateway - Allows you to easily start accepting payments in your staging environment in minutes. No minimums, no contracts and none of the headaches traditionally associated with payment gateways.
Marketplace - Creates financial accounts for your merchants, this allows developers not to have to worry about aggregation laws and other relegation red-tape.
The API also allows two main options when it comes to the buyer checkout process:
- Hosted Checkout - WePay handles all the PCI requires for you.
- Integrated Checkout - Enables the developer to build and host the pages to fully integrate the payment service into their product. This is especially useful for mobile applications or businesses that want full control over the checkout experience.
Pro Very Easy to Setup
Stripe is very simple for developers to integrate into their application as it is a "works out of the box" solution with a fantastic API.
The Stripe API is incredibly simple to setup, for example creating a new charge with Ruby is simply:
require "stripe"
Stripe.api_key = "vtUQeOtUnYr7PGCLQ96Ul4zqpDUO4sOE"
Stripe::Charge.create(
:amount => 400,
:currency => "usd",
:card => {
:number => "4242424242424242",
:exp_month => 1,
:exp_year => 2014,
:cvc => 314
},
:description => "Charge for test@example.com"
)
Pro Very competitive fees
Pro Great Documentation
Pro Supports online marketplaces
Stripe have recently announced support for online marketplaces. This means a service can now enable their users to seamlessly collect payments using the Stripe API.
Cons
Con Flimsy tech
Based on people that I've spoken with their API doesn't work very well.
Con They have very complicated and expensive pricing for marketplaces
See here.
Alternative Products
