Pierre from Kill Bill here. This sounds like something that is be supported out of the box. I'm not sure I understand why the Stripe plugin needs to be rewritten, but feel free to reach out to our Google groups if we can help!
It really depends on your usecase, but some benefits:
* Lower cost (just pay for payment processing, not the subscription features)
* Ability to integrate with multiple gateways (to lower cost, support more payment instruments, higher resiliency, etc.)
* More advanced subscription features
* Ability to customize the system through custom code (plugins)
* Data ownership (easier to run analytics reports, since you own the subscription data)
FYI this is just a managed sandbox, to test things out. We don't offer Kill Bill aaS, as it goes against our value proposition (Kill Bill is a framework to build your own internal subscription billing and payments platform).
Thanks, now I know what it is, why don't you put this piece on top of the repo so everyone visiting know what it is and doesn't waste time with the marketing babble
FWIW the very vast majority of our users are integrated with either Adyen, Braintree, or Stripe (all open-source plugins).
I know of ~20 integrations with more advanced gateways/processors: these are closed-source plugins, but the overall community wouldn't benefit much from accessing them (e.g. it doesn't make sense for many companies to directly integrate with mastercard APIs).
Thanks for this gem of a link. I had a good chuckle all around but found this part particularly very funny:
Apache Kafka was named after Franz Kafka, who lived as an author in turn-of-the-20th-century Austria. Like the project named after him, he was slow to start, inconsistent in delivery, and left a mess of unpublished work after a tragically early death.
Kill Bill (note: I'm a co-founder) provides payment routing capabilities, so you can integrate with multiple providers (e.g. Stripe + Adyen) and shift payment traffic to go through one or the other dynamically. This is very common in large b2c companies.
That being said, to your point, this still requires either a vendor neutral vault for the cards or to tokenize them in all of the vendors. Possible, but still hard to do in practice.
Yeah,that's what I think too : It seems hard (impossible) to register user's credit card at each payment provider (Stripe, Adyen, etc) and then start a subscription at some place (Stripe) and automatically switch in case of issues. There is high probability that in this scenario, Adyen will see the credit card refused because it never did a single payment for, say, 2 years, and suddenly starts a 300$ monthly subscription.
And I'm not even talking about 3D Secure!
As mentioned in the comments, a solution would be to migrate from Stripe to a merchant account with a bank where your service is vetted upfront.
If you are looking to manage subscriptions outside of Stripe, but keep using Stripe for payment processing, take a look at Kill Bill, the open-source subscription billing & payments platform: https://killbill.io/
It sounds like you are looking for an entitlement system[1]?
In my experience, none of the SaaS providers mentioned help you with this, probably because it's very dependent on your product and business logic. Even with Kill Bill, which has an entitlement system[2], some amount of coding would be required to manage and enforce states like "max amount of users reached for that plan" (the logic would be abstracted from the billing though).
