Ahh the modern P/I/SAAS method of working.
What’s your resilience plan? Surely you have a plan if a supplier stops working with you? With 10M revenue it seems irresponsible to have all your eggs in one basket.
Ahh the modern P/I/SAAS method of working.
What’s your resilience plan? Surely you have a plan if a supplier stops working with you? With 10M revenue it seems irresponsible to have all your eggs in one basket.
Tens years ago I implemented a payment service for the ecommerce site I worked for. Our main fear wasn't that a payment provider would cancel our contract with 48 hours notice, but it was certainly something that concerned us. Our main goal was to work around instabilities as the PSPs at the time. They where nowhere near as stable as we would have liked. We also wanted to be able to add or move between PSPs in the future, to get better deals.
At any given time we had active contracts with at least two PSPs providing credit card clearing, as well as a few with "buy now, pay later" options and a few payment options for various local markets.
The service/gateway I build would take a order and return a list of payment options that would be valid. Valid meaning available in that country, valid in terms of total amount, insurance and so on. The customer could then pick whatever payment option they preferred.
We where able to turn on or off payment options with a checkbox. So if/when a PSP went down, we could just switch to our backup PSP. Sure the cost would be a bit higher, but that's preferable to losing the order.
Pushing $10M+ though just Stripe, and betting that they will never be down, never fail, and never decide that you violated some rule is nuts. I'm not even faulting Stripe, because other providers WILL do the same.