Hey folks - Just an update…
Our team has confirmed that the issue was resolved and keyed-in payments began to work again as of September 2 at 5:42PM PT. We had been monitoring the issue over the weekend to ensure it was resolved before posting an update. We have been in contact with Worldpay to try to understand the source of the issue as it appears to have been on their end. We recognize this kind of issue has huge impacts on your business and will do everything in our power to work with Worldpay to prevent this from happening in the future.
In regards to adding other payment processors: We also have Stripe, Authorize.net, and PayPal. None are perfect, and payment processors, in general, can be…challenging to work with…it’s not unique to WorldPay. We’ve explored partnerships with others many times. For context, these are very time-intensive integrations to build so there are real opportunity costs in terms of other things we could build instead. The last time we were close to adding one, they were acquired by Worldpay right before we started 
So yes, I get it, it’s frustrating - but every time we analyze spending time on a new payment processor and weigh that against, say OS Patching or Policy Inheritance the answer is pretty clear. That doesn’t mean we won’t get to it, but it’s never felt like the #1 priority based on what MSPs were telling us, especially because I’m not sure the grass is greener on the other side 
Let me know if you have any questions,
Ian