Re:Stripe is no longer a suitable payment processor
by siwatanejo on Thursday August 03, 2023 @11:55PM
(#36995313)
> since you now have two providers that could potentially ban you
But less chances that they both ban you roughly at the same time. So if A bans you, you move to B and start integrating C. Once you have integration with C ready, you then support B&C in production.
If in the future B or C ban you, then do same as above with D.
BTW, what would be your first choice for a $StripeAlternative nowadays?
Re:Stripe is no longer a suitable payment processor
by AndroTux on Saturday August 05, 2023 @05:54PM
(#37016633)
Good question. Probably PayPal, even though I would consider them to be even looser with the ban hammer than Stripe. But when speaking internationally, they probably support the most payment methods? Adyen and checkout.com also look quite comparable, but I don’t know how their APIs hold up.
The big difference is that with a payment processor it's much harder to diversify than, let's say, AWS. If done well, I can quickly switch to another cloud provider without my users even noticing. For payment providers, this is not possible. The user has to at least re-enter their credit card information, which is going to be a big problem for a lot of companies.
But let's say you did it. You finally moved away from Stripe to $literallyDoesntMatter. Now, a few years down the line, $literallyDoesntMatter also bans you, because it turns out, you are still a small business and the new provider also doesn't care about you. Now what do you do?
Serious question: How would you, as a small business, try to diversify your payment provider? Would you go through the effort to support and implement two payment providers and use them roughly equally, so that if one goes down, only 50% of your customers need to migrate? But then you have essentially doubled your risk of getting banned, since you now have two providers that could potentially ban you. What other options are there?