Why save a customer's card at the first sale

What this step is

Step 37 (Part VI, Build the machine) is marked easy difficulty and often skipped in the matrix, despite being the thing two other steps in the same part (order bumps, one-click upsells) depend on.

It is skipped for an ordinary reason: it looks like plumbing rather than a decision, and a checkout that only charges once never surfaces the gap.

Why it gets missed, and what it costs

Save the payment method at the first purchase, with consent. An order bump or a one-click upsell depends on it later and cannot be added after the fact. Skip it, and every later offer has to ask for a card again, which collapses the upsell close to zero.

The checkout's own rule matters here too: the server owns the price, not the page. The browser sends an identifier, the server looks up the amount, and nobody can set their own total by editing the page. That is also what makes a later price change a one-line edit instead of a rebuild.

What done looks like

A buyer who completes the first purchase has a token on file, consented, ready for a same-session order bump or a later one-click upsell, with no second payment form in sight.

The field count on the checkout itself stays under eight: for a digital asset, an email address and a payment method, nothing else. Account creation never happens before purchase; the account gets created after payment and the credentials get emailed.

Where it breaks

Building the order bump or the upsell first, discovering the saved-card step was never wired in, and shipping a second checkout form instead, which is exactly the failure this step prevents.

Forced account creation before purchase is one of the three most commonly cited reasons for cart abandonment in published studies, alongside unexpected costs and no visible total, which is also the argument for keeping the field count low.