Screen study · Reviewed September 23, 2026
Affirm account creation and identity checks
Distinct screens explain the SMS route, account details, a security check and an app passcode.
How should an account flow explain each step that asks for sensitive information?
The captured interface names the SMS channel, links terms and privacy information, explains the reason for an identity field and states what the passcode unlocks. The screenshots do not verify policy claims, security outcomes or the exact conditions that trigger each step.
Evidence and limits
Selected Affirm Aug 2026 exported iOS screens, shown as still references. No recording is attached; ordering, timing, intermediate actions, outcomes and alternate paths are not established.
Read the decisions
01 / Affirm · Aug 2026 · Still image
Pay over time introduction
What is visible
A navy welcome slide says Pay off your plans and mentions AutoPay and purchase management; it offers US location selection, Log in and Explore without signing in.
Design interpretation
Pair the financial proposition with a non-account route so browsing does not require immediate sign-in.
02 / Affirm · Aug 2026 · Still image
Open secure account sign-in
What is visible
A browser sheet on affirm.com asks for a mobile number, explains SMS verification and offers account creation or passkey sign-in.
Design interpretation
Make the verification channel and alternate access method visible near the primary action.
03 / Affirm · Aug 2026 · Still image
Begin account creation
What is visible
The account form explains that it needs basic information and shows a mobile-number field with a change-number link.
Design interpretation
Explain data scope before collecting it and let people correct the phone number at the field.
04 / Affirm · Aug 2026 · Still image
Enter a verification code
What is visible
A modal says a text was sent and presents a six-digit code entry area plus a route to request another code; the code value is not transcribed.
Design interpretation
Explain the origin of the code and provide recovery if the message does not arrive.
05 / Affirm · Aug 2026 · Still image
Explain an identity check
What is visible
The account flow requests the last four digits of a Social Security number and explains that this is an extra account-security measure.
Design interpretation
Place the reason beside a sensitive request; the screenshot cannot independently verify data handling.
06 / Affirm · Aug 2026 · Still image
Create an app passcode
What is visible
A minimal screen asks the person to create a passcode, with four progress dots and an explanation that it unlocks the app.
Design interpretation
Explain what a local credential is for at the point of setup.
What to question
- Phone and identity checks add friction; ask only when needed and explain retention and use in the product itself.
- A passcode gives a direct app-unlock explanation, but this archive does not establish device-level alternatives.
- A still cannot verify SMS delivery, identity decisioning or the safety of the underlying process.
Try an original implementation
Explore a three-step web onboarding pattern: choose a goal, set a pace, and optionally request a reminder. Go back to revise answers without losing them.
This React example uses native form controls, keyboard navigation and focus management. It is a separate prototype with original copy and styling, not a reproduction of the source apps.
Download React sourceRequires React and Tailwind CSS. Web only; not React Native. MIT license.
Import the named OnboardingExample component into a page. Replace the final preview with your application logic; this example makes no network requests.
Practice studio · Original web demo
Step 1 of 3
What would you like to practice?
Before you ship
- Name the verification channel before sending a code.
- Explain sensitive data requests near the field and link complete privacy details.
- Keep recovery and alternate sign-in routes visible when supported.
Validate these recommendations with your own users. No conversion uplift is claimed.