Need advice about which tool to choose?Ask the StackShare community!
Dwolla.js vs Stripe: What are the differences?
Dwolla.js: Bank account verification in just a few lines of code. Dwolla provides bank transfers for your application that look and feel like your brand. Leverage our powerful yet simple API and get up and running with a minimum of four endpoints; Stripe: Payments for developers. Stripe makes it easy for developers to accept credit cards on the web.
Dwolla.js and Stripe can be categorized as "Payment Services" tools.
Some of the features offered by Dwolla.js are:
- Secure, ready-to-use payment tools
- Powerful, custom payment solutions that are easy to get up and running.
- Real-time functionality
On the other hand, Stripe provides the following key features:
- 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.
Stripe or Paddle for payment processing for SaaS?
we used Stripe + Chargebee once and will NEVER use them again (they charge too much (300usd/month while offering way fewer integrations than Stripe)
Furthermore, Chargebee doesn't support managing disputes. We still need to go to stripe for that.
Looking forward to hearing your thoughts
I'd recommend you check out Recurly. They are one of the leading solutions in the recurring billing space, but also support one-off orders. Recurly answers most common e-commerce use cases, will also give, out of the box, rich plan/subscription management functionalities to all the teams within your organization. They also come with great documentation, and SDKs, which from an Engineering standpoint, made it a very enjoyable pilot to work on, at the time. You'll also get great visibility/BI/analytics for free, allowing you to monitor the health of your business. Your Finance team will also get all of the data that they want. Without having you write any line of code. As you did touch upon integrations, they integrate with major payment gateways, including their own, support webhooks, integrate with Segment and therefore any tool that integrates with Segment, which makes this solution one of the most extensible one you'll find. Eg. Triggerring some Email Marketing "journey" (workflow) in AutoPilotHQ based on certain events.
Hi Folks,
I represent Showwcase, which is a network built for coders.
We're introducing a paywall for content creators on the platform to start accepting payments from their Followers for premium and unique content over and above the general free content. We are internally considering either Stripe or PayPal to handle this for us.
If we take the pricing out of the debate, what's the go-to choice when choosing which to integrate? Our current standpoint is that Paypal has wider consumer adoption, and since most creators are individuals, it makes sense to just use Paypal because they already have an account. However, our business uses Stripe, and so it makes it easier if both the platform (Showwcase) and creators to be on the Stripe platform. That being said, if creators don't already have an account, they will need to sign up with Stripe on the spot, which is a friction point.
I would like to hear the pros and cons in developer environments as well as any other things we might not know.
PayPal is a dinosaur and a nightmare to work with, both in terms of API as well as on the business side. We support both because our A/B tests showed a material increase in conversions by offering both, but I would drop PayPal in a heartbeat if I could. Stripe is a joy to work with.
I prefer Stripe for developers' ease of integration and PayPal for providing the simplest user experience (i.e., improved revenue.) In my experience, neither platform requires a user register to pay via credit card. However, as noted, many people have a PayPal account, which allows quick and easy payments through a "more" trusted name.
I used Stripe and Paypal and settled on Paypal for the customer. However, the PayPal web hook back end is a complete mess (at least in PHP). Unless they have improved very recently, PayPal web hook integration is poorly documented and barely supported with bits and pieces of important code on GitHub and elsewhere. I can't speak for other languages. But given the popularity of Paypal (i.e., improved revenue), I decided to keep using Paypal after I got the web hook integration worked out.
Stripe is strong because of their security. It is difficult for the programmer to install it, and in my case was impossible since my hosting provider did not have up-to-date software that it requires. I had to use another program on top of it as the shopping cart instead of using Stripe's shopping cart. But Stripe integrates with everything if you can get it to install, and is stable.
The big reason to go with PayPal is the 6 months same as cash or multiple payments over weeks for your clients. Some clients need this and you will lose them without PayPal. PayPal may change their policies, so in my opinion, PayPal is not as stable as Stripe. Some clients refuse or can't use PayPal, where Stripe is available to everyone with a credit card.
In summary, I set up both for my clients. And I used Zoho for everything else - shopping cart, accounting, CRM, banking, etc. It integrates with both Stripe and PayPal and pretty much anything else you use.
Be sure to read the Terms of both Stripe and PayPal, and I think that will help you with your decision.
We use GoCardless to simplify the way clients and partners pay for our services. What intrigued us is the quick and easy ACH feature that gives our clients the option to log in with their bank account and shoot the funds directly to our account. The fee, compared to Stripe is less. Stripe and PayPal charge 2.9% + 30c and Stripe also forces the client to enter in all of their payment details manually and then if the payment doesn't work, the client has to try all over again. GoCardless charges 1% + 25c which is much more reasonable dealing with the large projects that we are currently working on.
We integrate GoCardless with Xero to easily send out quick invoices, receive the funds and track all revenue in one place.
With COVID-19 looming over us, businesses are, more than ever, looking for ways to set up online payments.
And having recently gone through implementing both Stripe and GoCardless to get monthly subscriptions set up and automated on my company website, I felt there was no better time to write this blog post!
If you're currently looking at working with a Payment Gateway provider API, or you're currently working with one but are not a fan, are looking to automate things a bit more, or are just generally thinking about changing, then you should have a read of my latest blog post where I compare Stripe and GoCardless.
I compare APIs in depth, specifically the subscription checkout flow that both offer (they're very similar, with some BIG differences).
There are plenty of code examples on how to set it up in a Node.js environment and right at the end, I rate each API based on the following factors:
- API ease of use
- API documentation
- Payment pages
- Costs / fees
- Security
- Developer appeal
- Customer experience
- Free Trial
So feel free to check it out, and I hope you like it. Please leave any feedback as it is very helpful. Thanks!
Stripe was made with developers in mind first so the extensibility of it is great! This makes it very easy for us to integrate and automate as much as we need with its APIs and SDK. It allows a lot of customization of exactly what we need to build our applications. They also manage all of our customers from a tax and accounting perspective which makes it easy from a business standpoint.
Pros of Dwolla.js
Pros of Stripe
- Easy setup302
- Developer friendly292
- Well-designed api248
- Great documentation191
- Clear pricing169
- Secure75
- Reliable74
- Full integration with webhooks63
- Amazing api43
- Great customer support38
- Easy11
- Credit cards never hit your server - no pci worries6
- Recurring billing5
- No merchant account/gateway required4
- BitCoin3
- Easy to integrate3
- Support for SCA (Strong Customer Authentication)2
- Fast UI2
- Great app2
- Beautiful1
- Connect1
- Checkout.js1
- Great UI1
- So easy to use1
- Payments without own backend (using Stripe Products)1
Sign up to add or upvote prosMake informed product decisions
Cons of Dwolla.js
Cons of Stripe
- Connect4
- CANNOT withdraw USD to a Canadian Bank Account2
- Does NOT have a currency conversion option like Paypal2
- They keep 25% of the income for 60 days2
Sign up to add or upvote consMake informed product decisions
What is Dwolla.js?
What is Stripe?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Dwolla.js?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Dwolla.js?
What tools integrate with Stripe?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+31
+46+42+25
+44
+20
+35