pamonrails

5 ms·

1.
by pamonrails 2y ago
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!
2.
by pamonrails 4y ago
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 resil
3.
by pamonrails 4y ago
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).
4.
by pamonrails 4y ago
No fake marketing :-)
5.
by pamonrails 4y ago
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 over
6.
by pamonrails 4y ago
Fair. That being said, we've come a long way by now. Lots of our users deploy Kill Bill in "cloud-native" environments these days (e.g. k8s). Also, we've deprecated JRuby support. Plugins are either written in Java or in
7.
by pamonrails 4y ago
We don't follow SemVer (yet?). We use even minor versions for LTS releases (e.g. 0.22.x) and odd versions for dev releases (e.g. 0.23.x). Kill Bill is very much stable now :-)
8.
by pamonrails 4y ago
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 l
9.
Introduction to Kill Bill using a fictitious vignette service(blog.doubleslash.de)
4 points by pamonrails 5y ago|0 comments
10.
by pamonrails 6y ago
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/ - Stri
11.
by pamonrails 6y ago
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
12.
by pamonrails 6y ago
This is a bit of shameless plug, but if you are looking to manage subscriptions outside of Stripe, and simply use Stripe for payment processing, take a look at Kill Bill, the open-source subscription billing & payments platform: https:
13.
by pamonrails 7y ago
Take a look at open-source solutions, specifically Kill Bill [1] (disclaimer, I'm a core contributor) It provides a subscription management platform with all the features you would expect out of the box (recurring billing, plans manage
14.
by pamonrails 8y ago
@pierre from Kill Bill here. Back in the days, we tried very hard to have a good native integration with the blockchain for recurring payments (see the "Extension for BIP-0070 to support recurring payments" thread on the bitcoin-d
15.
by pamonrails 8y ago
@pierre from Kill Bill here. First, regarding maintaining plugins in general, the project is over 7 years old now. We have everything from very small to very big companies using us (some of them have their logo displayed at http:/&#x2
16.
Kill Bill – Dwolla integration(killbill.io)
11 points by pamonrails 10y ago|0 comments
17.
Processing Payments at Scale(engineering.groupon.com)
5 points by pamonrails 10y ago|0 comments
18.
by pamonrails 10y ago
Here is the 2016 version: http://killbill.io/blog/having-fun-with-docker-stripe-and-ki... ;-)
19.
by pamonrails 10y ago
I'll echo what others said: run your own. Using a SaaS-based recurring billing solution has its drawbacks: * You are limited by the features offered by the provider for your pricing schemes (for example, most only offer basic forms of
20.
Kill Bill on Microsoft Azure(killbill.io)
3 points by pamonrails 10y ago|0 comments
21.
by pamonrails 10y ago
We do a lot of migrations from custom systems or SaaS integrations to Kill Bill (open-source subscription billing and payments platform) [0] and we've summarized our strategy and usual pain points in our migration guide [1]. You might
22.
by pamonrails 10y ago
Have you considered managing the subscriptions yourself? With Kill Bill[0], you can own the subscription piece while still delegating payments to PayPal and/or Stripe. [0] http://killbill.io/ - Open-Source Subscription
23.
Understanding payment failures(killbill.io)
3 points by pamonrails 10y ago|0 comments
24.
by pamonrails 11y ago
Removing support for credit cards in Kill Bill: http://killbill.io/blog/deprecating-support-debit-credit-car...
25.
by pamonrails 12y ago
There are third-party solutions which can take care of tax calculations for you - these can be plugged into Kill Bill. One of the main core values of Kill Bill is that you own your data: this is especially important if you focus on growth,
26.
by pamonrails 12y ago
Yes, it's mostly back-end. We do provide a front-end (a mountable Rails engine), but it's mostly for administrative tasks only (for your support team to handle refunds, chargebacks, upgrades and downgrades, etc.).
27.
by pamonrails 12y ago
Good point, we'll update the docs. Regarding PCI, it's up to you. You can run it inside your PCI environment or delegate it to your payment provider (via CC tokenization).
28.
by pamonrails 12y ago
You can still delegate PCI to your payment provider (via tokenization). SafeKiddo[0] just launched using Kill Bill + Braintree. [0] https://www.safekiddo.com/
29.
by pamonrails 12y ago
@pierre from Kill Bill here. I saw the DO button post this morning, pretty cool indeed. We've recently been playing with Docker to standardize our deployments. Pushing an image to DO should be easy. http://killbill.io/b
30.
Integrating Kill Bill with Apple Pay(thekillbillstory.wordpress.com)
1 points by pamonrails 12y ago|0 comments

More ›