Monzo for Android - Beta Channel Changelog šŸ•µļøā€ā™‚ļø

SC95, why do you say the app isn’t secure enough? Things that are a significant security risk, like setting up new payments are protected by the card PIN to provide 2FA.

Wouldn’t it be a bit silly to then protect that same card PIN by only the app? I’m not saying the OnFido process is brilliant for this, the fingerprint verification on iOS is a much better option here, and I wish they’d gone that route on Android, but still… don’t take it as a sign the app isn’t secure enough. It’s secure enough for its function, but it isn’t secure enough to protect the card PIN since the card PIN then, in turn, protects functions requiring more security than the app alone.

I actually consider it very well-designed overall. It uses real security where needed, with none of the ridiculous security theatre most banks have. Great job, Monzo!

I have been against extra layers of security and have had a lot of arguments on this here so don’t think you got my point. I am saying it feels like Monzo don’t feel that App is secure enough hence these long-winded security and identity procedures.

I have found Monzo COps pretty rigid about these even when they don’t make sense so bit annoyed with my experiences these days with Monzo a bit.

1 Like

Sorry, I was referring more generally to people’s complaints the app isn’t secure enough. But, did you read what I wrote in detail? Basically, the app can’t protect the PIN because the PIN is used to protect things the app isn’t considered secure enough to protect. This is very reasonable.

I’m not saying OnFido is the right answer, I think they got this balance a lot better on iOS…

1 Like

I understand what you said and agree but like you said just don’t agree with the whole process they need to speed up Android development I guess it’s just is not pretty and necessary.

1 Like

I hope this is replaced with Fingerprint verification when it’s ready for Android. I hate taking selfies, let alone a selfie video. (Not to mention fingerprint is a lot faster).

1 Like

And cheaper for Monzo. I find it amazing they implemented it this way, there must be some concern with the Android biometrics API for them to not only hold it up this long, but to spend time implementing this…

2 Likes

Surely just enabling fingerprint/pin unlock on Android would be much easier?

3 Likes

You’d think so… the API doesn’t look that tricky to implement… Android 6.0 APIs  |  Android Developers

Exactly what I have been trying to make sense… But can’t WHY this why not just leave as it was and spend time on some other useful stuff like biometrics verification instead.

Then there is this fee Monzo have to pay for this service… We are being told topups cost Monzo, overseas withdrawals do aswell hence fees but they are happy to spend on pretty lame implementation for a PIN recovery :face_with_raised_eyebrow:

2 Likes

I’ve used a number of smaller company apps which have this. Even the much smaller Loot.io app has Android fingerprint unlock.

Agreed 100%, though PIN recoveries are, to be fair, quite rare things.

That’s what’s really confusing me… looking at the API documentation, it’s a seemingly simple thing to implement. Perhaps Monzo doesn’t trust it for some reason?

I’m sure there will be a reason, maybe relating to FCA approval.

Don’t forget development cost :robot:

That’s what I’m wondering. Technically, it’s seemingly far simpler than integrating the OnFido process.

The call to the OnFido process is, at least on the surface, a far bigger piece of development…

I think they’re planning the overall experience so just like Targets, they don’t want to build something then re-make it.

@SC95 OnFido was already developed as part of Account Verification, Fingerprints/PINs would be new.

Not really, it’s just an API call either way, and probably far more testing with the OnFido stuff… All the ā€œnewā€ bits - the actual PIN recovery screens and all that would be very similar.

What I mean is, they’ve programmed & tested OnFido integration, but not Fingerprints for Android. And Fingerprints are not universal.

Fingerprints not being universally supported is an issue, yes - but testing?.. I don’t see it. They have to test how either one behaves with the new PIN recovery screens anyway. Remember, they’re not writing a fingerprint auth system, just asking the one Google has given them to check a fingerprint.

I am not expert but don’t most biometric security implementation come with a fall back on a PIN or password so if a phone doesn’t support biometrics it can automatically go onto PIN I know not too great but most new Android phones now are equipped with biometrics

3 Likes

The client-side API may be easy but we would need to rebuild a significant chunk of the service to support it. There are big changes coming to authentication and trusted devices coming to both platforms though! :lock:

As for the current PIN recovery flow, everybody is currently being put through the entire full flow every time. We will be iterating on this early next year but committed to shipping the very first version in Q4 2017 to comply with changes to PIN security requirements (from January, this system through the app will be the only way to retrieve your PIN, though there will be other verification options).

Additionally, there are a few assumptions in this thread that while it is not within my authority to call out specifically, are not true. :sweat_smile:

2 Likes