← Affirm
Complex day at Affirm

Lock down recovery sessions while shoppers replace their phones

You’re the security / reliability engineer. Your team is in the room. Printed Oct 8, 2026.

The recovery path preserves access at the same moment it can preserve the wrong session.

Device binding protects account ownership, while recovery must still work for shoppers who no longer have their old phone.

Who you’d be doing this for

“My payment is due tomorrow, and my old phone still shows me signed in.”

Nicolas Becker · Retail shopper

She uses the Manage tab to check and pay an upcoming interest-free installment after replacing her phone.

What is at stake

Some recovered accounts keep a valid session on an old device while others fail on a second attempt. You must weigh permanent session invalidation against shoppers reaching checkout and their upcoming payments.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • account ownership vs recovery access
  • irreversible containment vs shopper continuity
  • automated detection vs verified control evidence
  • checkout completion vs step-up friction

Why Affirm

Interest-free payment plans rely on shoppers being able to authenticate safely at checkout and manage scheduled payments after account recovery.

Written with these in mind

identity security engineersite reliability engineerauthentication platform engineer

Not your kind of problem? 45 more at Affirm, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.