Stripe Checkout: Deciding Which Billing Fields to Collect When They Hurt Conversion

You are a product manager for Stripe Checkout, the payment page that Stripe hosts on behalf of merchants. Merchants are telling Stripe that making their customers enter billing details at checkout adds friction and is costing them conversions. How would you respond to this feedback? Explain how you would check whether the complaint holds up and where the problem sits, what you would change, if anything, and how you would know the change helped without causing new problems. ```hint Ask what each field is for Before deciding to keep or drop a field, find out what each billing field is used for today and who depends on it. The same field can protect one group of merchants and be pure friction for another. ``` ### Clarifying Questions - Which fields count as billing details here: cardholder name, email, full street address or only postal code, and which of them draw the complaints? - Does Checkout require these fields for every merchant, or can merchants already configure them? - Who is complaining: merchants with customers in particular countries, merchants with mostly mobile traffic, or a particular kind of business, and how many merchants is it? - Do we have field-level funnel data showing where customers abandon checkout, or only the merchants' reports? ### What a Strong Answer Covers - Validation of the feedback with checkout funnel data before acting, segmented by customer country, device and merchant type - An account of why each billing field is collected and what removing it would cost merchants and Stripe - A targeted response rather than an all-or-nothing switch, with friction fixes separated from the policy change - A test or staged rollout with a conversion goal and guardrails for fraud, disputes and payment acceptance - Closing the loop with merchants, including those who depend on the current behavior ### Follow-up Questions - The change lifts conversion, but disputes rise for one merchant segment a few weeks later. What do you do? - A large merchant wants full addresses on every payment while many small merchants want them gone. How does the product serve both? - How would you decide whether this work should come ahead of other items on the Checkout roadmap?