The guideline
Preserve every non-sensitive field — name, address, phone, email — across validation errors, session-level failures, and backward or forward navigation within checkout. For payment fields, retain the card type and masked last digits across navigation and recoverable errors, but always clear the CVV immediately after submission or on reload to stay within PCI DSS scope, and say so briefly if a field is cleared for that reason so it reads as a security rule rather than a bug.
Common failures
- When users navigate backward in checkout—to review shipping or adjust quantities—their entered card details vanish, forcing them to retype all payment information when they return to the payment step within the same session.
- When a session-level error occurs—such as a failed submission or network hiccup—the payment form clears all card details, forcing users to re-enter their card number, expiration date, and CVV from scratch. Non-sensitive fields like billing name and address are also lost, amplifying frustration.
- When a checkout form detects an error, previously entered information is cleared, forcing users to re-enter their name, address, payment details, or other data from scratch. This violates basic form resilience principles and creates unnecessary friction at the point of conversion.
Where it applies
Pages
Disciplines
Devices
Why it matters, how to fix it, and the research behind it
Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first.