Stripe is wrongly suspending accounts

Re:Stripe is wrongly suspending accounts by ComputerGuru on Friday November 25, 2022 @12:24PM (#33744680)

My most important overhaul for our business was abstracting over payments and ensuring we weren’t dependent on any one processor for online checkouts. It doesn’t matter who you are with or how flexible they are, sooner or later, for logistical, account, network, or other issues, if you have only one payment provider it is going to be unavailable and you’re going to be losing money.

If you’re on the .NET stack, our abstraction [0] is over PayPal, PayPal credit card, Stripe, ChargeBee, CoinBase, Amazon Payments, and other providers that have since been replaced with no-op exceptions because the payment processors have gone under.

[0]: https://www.nuget.org/packages/NeoSmart.Payments/

[ Parent | on HN ]

Re:Stripe is wrongly suspending accounts by benbristow on Friday November 25, 2022 @01:06PM (#33745116)

Reminds me of PHP's Omnipay

https://github.com/thephpleague/omnipay

[ Parent | on HN ]

Re:Stripe is wrongly suspending accounts by handelaar on Friday November 25, 2022 @01:34PM (#33745368)

Omnipay does not support Stripe SCA and is basically abandonware.

[ Parent | on HN ]

Re:Stripe is wrongly suspending accounts by ComputerGuru on Friday November 25, 2022 @02:44PM (#33746056)

It’s nowhere near as comprehensive, of course. It only features the providers we’ve used ourselves.

I think abstracting over payment APIs has gotten so much more difficult this side of 2014 or so. They’re doing all they can to achieve consumer lock-in and trying mighty hard to each offer their own custom services that they try really hard to convince you need and can’t live without, and invariably there might be something in there you want to support in your abstraction, sometimes necessitating cascading architectural changes. This is probably the third “major overhaul” of the abstractions we’ve written as a result.

[ Parent | on HN ]