Designing Against AI Fraud: Where Friction Belongs in Your Product

A practical anti-fraud playbook for product teams, based on real account takeovers and the move to passkeys at Pleo.

Date & Location
(
)
Track
Type
Talk
Language
English

About this Session

For designers, PMs, engineers and leaders. No security background needed.

AI has made convincing fraud almost free. A tailored phishing email takes minutes, and a deepfaked CFO can join your video call. Attackers no longer break the encryption. They target people and the flows product teams design: login, account recovery, admin resets and support calls. That makes fraud a product and UX problem, and under new EU payment rules a P&L problem too.

Nicole Michaelis shares what Pleo learned from real account takeover incidents and a forced move to passkeys: a strict login is not the same as a secure one.

You will leave with:

  • A friction budget: match friction to how irreversible an action is, instead of spreading it everywhere.
  • The UX cost of six defences: what passkeys, risk-based checks, cool-downs, verified channels, freezes and warnings each stop, and what they cost your customers.
  • Three things to do on Monday: map your irreversible actions, make your own messages verifiable, and give security UX an owner and an incident playbook.

More Sessions

Check out more Sessions from this Track

No items found.