Daily iOS
Security

Layered defense for transfers

You're designing the transfer feature of an iOS banking app. Which layers of defense would you put on the client and the server to protect a single transfer request?

How would an interviewer hear this answer? You'll see whether they'd move on, dig in, or say no, and which sentences would trip you up. Your score doesn't change.
See the short answer

TLS with certificate pinning on the wire, the token in the Keychain behind a device-lock access control and biometrics, and a client-generated idempotency key on the request to stop duplicate retries, while every one of these stays secondary: account ownership, balance, limits, and approval are the server's final call.

Share a question