Stripe vs SlimPay: What are the differences?
Developers describe Stripe as "Payments for developers". Stripe makes it easy for developers to accept credit cards on the web. On the other hand, SlimPay is detailed as "Provides a smart recurring payments API and solution ideal for organizations". It enables merchants to facilitate acquisition, increase the consumer lifetime value and maximize revenue through card and direct debit payments.
Stripe and SlimPay can be primarily classified as "Payment Services" tools.
Some of the features offered by Stripe are:
- Full-stack payments- You don’t need a merchant account or gateway. Stripe handles everything, including storing cards, subscriptions, and direct payouts to your bank account. Stripe.js lets you build your own payment forms while still avoiding PCI requirements.
- An API that gets out of your way- It’s so easy, we’ve embedded a bunch of examples right here. Copy some of these requests into your terminal and check out what happens. With wrappers in Ruby, PHP, Python and more, you can get started in minutes.
- Pricing like it should be- 2.9% + 30 cents per successful charge. No setup fees, no monthly fees, no card storage fees, no hidden costs: you only get charged when you earn money.
On the other hand, SlimPay provides the following key features:
- Enroll your customers
- Collect your payments
- Monitor your activity
What is SlimPay?
What is Stripe?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose SlimPay?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using SlimPay?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
To accept payments on updown.io, we first added support for Stripe which is by far the most popular payment gateway for startups and for a good reason. Their service is of awesome quality: the UI is gorgeous, the integration is easy, the documentation is great, the API is super stable and well thought. I can't recommend it enough.
We then added support for PayPal which is pretty popular for people who have money on it and don't know where to spend it (it can make it feel like you're spending less when it comes from PayPal wallet), or for people who prefer not to enter a credit card on a new website. This was pretty well received and we're currently receiving about 25% of our purchases from PayPal. The documentation and integration is much more painful than with Stripe IMO, I can't recommend them for that, but not having it is basically dodging potential sales.
Finally we more recently added support of BitPay for #Bitcoin and BitcoinCash payments, which was a pretty easy process but not worth the time in the end due to the low usage and the always changing conditions of the network: the transaction fees got huge after price raise and bitcoin because unusable for small payments, they then introduced support for BCH and a newer Bitcoin protocol for lower fees, but then you need a special wallet to pay and in the end it's too cumbersome, even for bitcoin users, to pay with it. I think unless you expect a bit number of payments using cryptocurrencies it's not worth implementing this solution, and better to accept them manually.
Running a subscription service with just direct calls to Stripe or similar payment gateways is possible but also needs dedicated person(s) for decent amount of development and maintenance.
Plus features like updating card details, invoice history - all these can be built. Again, more dev work and resources.
Use of subscription platform like Chargebee or Recurly is definitely a great help here.
Chargebee offered a simple pay-as-you-go transparent pricing and almost trivial signup process.
Google Analytics is a great tool to analyze your traffic. To debug our software and ask questions, we love to use Postman and Stack Overflow. Google Drive helps our team to share documents. We're able to build our great products through the APIs by Google Maps, CloudFlare, Stripe, PayPal, Twilio, Let's Encrypt, and TensorFlow.
Stripe has been developed for web users not by banks just moving bank apps to web. Their APIs are easy to use and understandable and they have support for lots of languages.
They are also incredibly flexible and it's possible to do things with Stripe that other providers don't allow (for example implementing annual billing it's difficult to get authorisation as a start-up - even if it's only $20 a month, that's $240 annually which means there's a year to charge-back - so implement it as a one off payment, which does mean doing annual billing yourself, but there's a year to get it right).
They also have fantastic start-up deals (if you know the right accelerator or other provider) easy to get transaction fees waived.
They also have engineers at hand to help you with any issues, who actually know the product.
I love Stripe. They were super, super easy to set up — it was less than 5 minutes and I could already put test payments through my app! They take a huge chunk off of small transactions (if you're only charging $3, you only get $2.61), so they kind of make you raise prices on small fees. However, I love not having to worry about security or managing anything, just getting paid!
Integrating Stripe to your app is dead simple.
It removes all the hassle of integrating with a payment gateway.
Its API is developer-friendly and intuitive, reliable, and works all the time.
It’s my payment gateway of choice.
Stripe is used as one of our payment-gateways included in our shop-solution. We only use the credit-card features of it and don't accept any bitcoins (yet).
Payments? Stripe. There's pretty much no other option that's as easy or pretty to work with out of the box, you just plug it in and watch the fireworks.
CC handler for our membership system. It was an easy choice for how quickly we were able to implement it, as well as the disputed payment process.