Documentation Index
Fetch the complete documentation index at: https://developer.prove.com/llms.txt
Use this file to discover all available pages before exploring further.
Context
Pre-Fill only delivers value when customers finish the flow and understand how their data is used. Friction, vague copy, or weak consent erode completion and trust before verification ever runs. The Prove Standard℠ CX requirements describe how screens, language, and consent work together so onboarding stays coherent—for the customer, for risk controls, and for downstream Pre-Fill use of verified data.Terms
These labels appear throughout the Pre-Fill CX material:- Prove Standard℠ — A set of frontend and customer-experience (CX) patterns Prove recommends so onboarding stays high-converting, legible, and aligned with how possession and identity steps should feel end to end.
- Pre-Fill — Using verified attributes to populate your forms so customers repeat less manual entry after a successful identity path.
- MobileAuth℠ — Prove’s possession-oriented authentication path (silent where the product allows it), often upstream of or alongside Pre-Fill depending on your flow.
- Informed consent — Clear, upfront terms and privacy disclosure so customers know what data is collected, for what purpose, and what happens next before they commit to the next step.
Why these requirements exist
Prove Standard℠ CX is not decorative layout guidance: it encodes why certain patterns show up again in successful Pre-Fill programs.- Friction and conversion — Heavy or confusing steps (especially around phone entry, possession, and handoffs) correlate with abandonment. Requirements keep the path short and legible so more customers reach verified state—the precondition for Pre-Fill.
- Simplicity and cognitive load — Dense legal walls, inconsistent labels, or parallel “extra” paths make it harder for customers to know where they are in the journey. Requirements favor plain language and predictable sequencing so attention stays on the task, not on decoding the UI.
- Trust and informed consent — Pre-Fill depends on customers accepting a legitimate data exchange. Visible security posture, honest data-use explanation, and accessible policies reduce perceived risk and support meaningful consent—not just checkbox completion.
- Regulatory and program fit — Jurisdictions and partner programs impose expectations on disclosure, minimization, and evidence of consent. The CX requirements align the experience with those constraints so technical success (verify → pre-fill) is not undermined by process gaps upstream.