[doorsopen]

Maybe an uninformed question, but I tool a look at the documentation, the stripe plugin demo, and then looked at what stripe offers. As someone who uses neither but might be interested in subscription + shop type purchases, what do I get with KillBill+Stripe that I don't with just Stripe?

[jmacd]

You save .5% that are fees you would otherwise be paying to Stripe.

You also get to manage the data and where it resides, if that is important to you.

[bredren]

I didn’t realize there was a variable rate in stripe pricing. I had thought it was the same before volume for any payment product that involves cards.

[jmacd]

No. Stripe is a bit insidious (that's probably too negative of a characterization) in that way. Once you start using a product, the pricing for that product then gets rated on your bill.

Stripe billing is .5%, Invoicing .4%, Tax .5%, Rev Rec .25%, etc.

Products like Checkout are included in your prevailing rate (2.9% or whatever).

[bredren]

The definition can cover a fair amount of ground.

My experience with the product has been that it has made very clear attempts to provide the user ID for SaaS implementations of the payments system.

I first heard of someone who was using stripe to store all user data on the Running in Production podcast, I thought they were nuts.

But then I went to reimplement the services this year due to the deprecation the "legacy" popover modal on Checkoit.

The new version seems more about locking builders to stripe than it is about anti-fraud, checkout UX or developer experience.

It’s subtle but can be discerned from the implementation details and docs or lack thereof. In that way I would suggest the company has made some insidious decisions about the product.

On one hand, it’s hard to blame them, because before their API could be replicated and swapped out like S3.