The main difference is that the source code is available under a FSL license and after two years converts to the apache 2.0 license... compared to Stripe where the core part of the system is closed source and proprietary
Ok but it integrates with Stripe, right? If you still need Stripe anyway you may as well use their features directly rather than go through an indirection layer?
It’s actually better to use a buffer layer so your own payment logic is platform independent, eg if stripe bans you accidentally you can easily use another payment provider
I agree it would be great in this situation but currently it only supports Stripe, and they don't mention plans of supporting any other payment platform.
That being said, this does not look to be targeted at small businesses and that problem is one that is only faced by small businesses. Small operations need to have every payment system they can get their hands on (lest one of them throw the ban hammer). A killer feature for smaller operations would be multiple payment integrations.
* Control the templates of your pdfs
* Control the templates of your emails
* Control how your emails are being sent
* It makes having multiple subscription items a lot easier.
* It allows you to define tax rates on a customer and product level
* It allows you to define tax rates on a country and state level
* Have multiple brands on the same account
Also, it's a lot cheaper than Stripe Billing even the cloud hosted version is. Stripe Tax is even more expensive.
Again maybe I'm missing something but since it's built on top of Stripe, I would expect that it does more than just Stripe. Otherwise I don't see why I would try to install this?