News for hackers. Stuff that matters.
Re:TIFU by using Stripe as a payment processor for my small ... by Aeolun on Thursday July 28, 2022 @07:33AM (#32262962)
> My only consolation is that every other provider is just as terrible.

My experience with Authorize.net support was really good. Their tech stack/api was absolutely archaic, but you could talk to real humans.

Re:TIFU by using Stripe as a payment processor for my small ... by a2tech on Thursday July 28, 2022 @08:22AM (#32263324)
And the thing about their tech stack is its old..but absolutely workable. They have examples in pretty much every language, decent documentation, and support. And they are very slow to sunset things because their customers are slow moving traditional businesses. So code you write for a customer may work without tweaking for 4, 5, or even 10 years.
Re:TIFU by using Stripe as a payment processor for my small ... by creeble on Thursday July 28, 2022 @11:46AM (#32265928)
In my case, 20 years. No change in API calls in that time.

Very few errors, except in the early days. I hate them because of the complexity of the solution (I needed a relationship with a separate "payment processor" that has changed names/systems/owners five times in those 20 years) but I have had few problems with withholding etc.

But my monthly charges and individual charges are very consistent, and chargeback rate very low (but not zero).

Re:TIFU by using Stripe as a payment processor for my small ... by Aeolun on Thursday July 28, 2022 @08:49PM (#32271831)
At the time I championed switching to Stripe. If I’d known then what I know now I’d have never done so.
Re:TIFU by using Stripe as a payment processor for my small ... by kitd on Thursday July 28, 2022 @09:10AM (#32263786)
This looks really good. Apart from anything else, they have a fraud detection tool that you can configure to match your own requirements, and can control yourself what happens to payments when filters are triggered:

https://www.authorize.net/en-us/resources/our-features/advan...