4 ms·
> It's also not that easy to just go rip out one processor > for another on a huge legacy code base. Unfortunately true. It's always a good idea to support
by xofer 13y ago
> It's also not that easy to just go rip out one processor
> for another on a huge legacy code base.
Unfortunately true. It's always a good idea to support more than 1 processor, ideally all used actively.
I've see many companies get burned by only having one. It takes ages to get another processor up and running.
- knighthacker 13y agoUsing more than one payment processor is definitely a smart move. Not only to avoid unpredictable consequences such as this acquisition, but also because it will give you a negotiating advantage as payment processing becomes more and more of a commodity.
- ante_annum 13y agoFrom an engineering perspective at my last job, having multiple also allowed us to abstract away the processors themselves into ways that made adding a new one pretty painless. If one went down, we just failover seamlessly.