No it wasn't. I couldn't remember the pin from my other card off the top of my head because I've been using Monzo for many months. I've learned from my mistake, I hope Monzo has too.
What would that be then? This outage is not Monzo's, but the processor's, affecting any card issuer that users it - a function Monzo has stated [0] it will do for itself without a third-party when it offers full current accounts later this year.
Calling this Monzo's failing is like complaining that Trello went down earlier in the week (due to the S3 outage). It's perhaps even less fair, since I imagine using multiple AWS regions is easier and more common practice than using multiple card payments processors. (Though I am just speculating on the latter point.)
No offense but I am gonna stay with my current bank ;)
When Monzo is actually capable of replacing your present bank, i.e. it offers current accounts, this issue won't exist.
> current accounts should be held to the same standards as an average todo-list app?
If your present bank used the same card payments processor, it would be experiencing the same outage. That's my point, not that it doesn't require more stringent certification than Trello.
> So you are saying that my credit cards and
There's no credit cards and the company's stated no plans to ever offer any, preferring to instead ask What problem makes you seek a credit card, and rethink what a modern solution looks like.
> No offense ... ;)
Why would I take offence? I'm just a user, no skin off my back if you're not ;)