The idea
Pain of paying concerns the salience and experience of spending, but a smoother checkout should not hide the fact that money is being spent. The comparison holds the plan and total constant while contrasting a repeated multi-screen process with a consented saved payment method and one explicit confirmation; saved details remain changeable and removable. Use the framework to separate avoidable effort from information that protects understanding, retaining visible fees, a clear final price and meaningful confirmation instead of treating fewer clicks as the only measure of a good checkout.
Use it thoughtfully
- Remove repeated information and unnecessary payment steps.
- Display the complete total before explicit confirmation.
- Keep saved payment details voluntary and removable.
An example
In an illustrative mobile checkout, a returning customer uses a payment method they previously chose to save. The same total remains visible, and they can change the method or stop before confirming, so convenience does not become an unexpected charge or disguised consent.
A question to try
Which steps are needless friction, and which are necessary for understanding and choosing to pay?
A useful framework is a starting point, not a guarantee. Effects vary with the audience, product and situation. Use truthful evidence, respect customer choice, and test the result.