Security

Fin.my
Fin.my
Published in
2 min readDec 8, 2016

ARCHITECTURE :

  • 3 layers distributed protection
  • Encrypted digital identities are stored in Keychain (Remember Apple vs. FBI?)
  • Encryption key is kept on FinPay Server. No data is kept in FinPay server at all.

AUTHORIZATION :

The encrypted data is only authorised if authenticated by:

  • PIN or Fingerprint (Verify User)
  • A session token that is created during last app login (Verify User)
  • A one time password (OTP) that is randomly created every 30 seconds once the mobile device after verifying SMS verification code (Verify Mobile Device)

INSPIRATION & COMPARISON :

  • Intel TrueKey (Sync to Server)
  • Google Chrome Smart Lock (Sync to Server)
  • Other Web Browser with Password Storage (No or Unknown security)
Intel TrueKey Snapshot

OUR INNOVATION :

  • Sync to Server puts users at risk if database is compromised. Fin Mobile does not sync data to server. Therefore distribute the risk.
  • User encrypted data is safe as long as PIN/Fingerprint and Mobile device are not lost. Further distribute the risk.
  • The only chance for user data to be comprised is when all three of the layers above are hacked at the same time.

--

--

Fin.my
Fin.my
Editor for

We are a fintech startup currently working on a mobile financial platform project. We resides in Cyberjaya, Malaysia.