[nhangen]

It seems to me that Stripe has gone from easy to cheer for underdog, to payment processor that wants to eat the world (ala Facebook).

I love that they are constantly innovating, but every time they do, I have to refactor my product, and then decide how much of my current product's custom functionality can be replaced by Stripe. Then I have to decide if I want to double down on Stripe (at the peril of other integrations), or create a wacky payflow that acknowledges dozens of additional gateways.

I don't want a single product that does everything. I want a great product that does a few things really well. This is starting to kill my love affair with Stripe.

[madamelic]

>This is starting to kill my love affair with Stripe.

More and more I feel Stripe catering to the non-engineers who just want a simple workflow at the expense of customization.

I still dislike v3 for the fact it tries to push me to use their own interface.

I was happy hooking your library up to my form. I know I can "customize" it (change the css classes... wooo) but it completely replaced v2 with no way to get that functionality back.

I wish Stripe would have "full tricycle wheels, we charge a bunch" or "barebones, we get out of the way and charge you very little".

[markwcollins]

I think the changes in v3 might have been for PCI compliance reason as much as anything

[hdolinski]

payment processors such as Stripe use this strategy to make even harder for you to switch for a different provider, if you ever feel like it. (payments industry expert here)