---
title: Entered checkout data survives errors and… · Rubric
description: Preserve every non-sensitive field — name, address, phone, email — across validation errors, session-level failures, and backward or forward navigation…
url: https://rubric.design/ux/checkout.entered-data-persists-through-errors
format: agent view of this page
updated: 2026-11-16
---

[UX guides](https://rubric.design/ux/) / [Cart and checkout](https://rubric.design/ux/topic/checkout) / Entered checkout data survives errors and back-navigation

# Entered checkout data survives errors and back-navigation

Usually high · How serious this usually is when it goes wrong. Not a score.

## 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

- Checkout
- Forms

### Disciplines

- Conversion
- Trust

### Devices

- Desktop web
- Mobile web
- Mobile app

## 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.

[Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents)

## Related guides

- [Optional add-ons offered and removable at the cart](https://rubric.design/ux/cart.optional-add-ons) · Usually critical · Offer optional extras — fast-track entry, parking, insurance, meal or seat upgrades — on the cart.
- [Shipping cost resolved at the cart](https://rubric.design/ux/cart.shipping-cost-visible) · Usually critical · Show the real shipping cost on the cart, before the user enters payment details.
- [Cart total includes taxes and mandatory fees](https://rubric.design/ux/cart.total-includes-taxes-and-fees) · Usually critical · Make the total on the cart the amount that will actually be charged.
- [Guest checkout available without account creation](https://rubric.design/ux/checkout.guest-option) · Usually critical · Offer guest checkout as an equally weighted option at the first step of checkout, presented alongside sign-in rather than beneath it, and let it reach payment…
- [Promotion terms are stated next to the offer, not behind a link](https://rubric.design/ux/checkout.promotion-terms-visible-inline) · Usually critical · State every material condition of a promotional offer — minimum spend, product exclusions, geographic limits, expiry — inline beside the offer, in the same…
