Show the cost before checkout

A situation worth working through

A supporter chooses an amount and reaches the last checkout screen. If the recipient, currency, or total is unclear, the person has to make a financial decision with incomplete information. Our preference is simple: the important details should be visible before confirmation, and the confirmation should describe what actually happened.

Let people make an informed choice

A supporter should understand the total before deciding to pay. A creator should know where to find the terms that affect their own receipts. Marketing language about joining for free should not make paid activity ambiguous.

Keep the explanation near the action

Rory’s product page says gift checkout shows the total and applicable charges before payment. It also points creators toward the pricing information relevant to their plans. The useful design question is whether the person can find the answer at the moment they need it.

Adding more explanatory text everywhere is not automatically clearer. Use specific labels and put detail where it helps the decision.

A practical check for creators

Review your public support invitation alongside the actual checkout. Remove wording that implies a different price, guaranteed receipt, or benefit than the experience provides. Link to current costs rather than copying a number into old posts that may remain online after terms change.

Keep the recipient visible

A person may arrive from a shared link or several browser tabs. The checkout should make it easy to confirm who receives the support. A familiar profile image can help, but the name and destination should also be readable. Do not rely on the visitor remembering every detail from an earlier screen or recognizing a cropped image alone.

Show the amount in context

Display the relevant currency and total where the decision is made. If a cost applies, explain it through current, maintained information rather than a vague promise of no fees. Avoid making people reconstruct the total from several disconnected labels. Clear presentation matters on small screens and with larger text, not only in a desktop design mockup.

Make completion distinct from progress

A loading state, a provider handoff, and a completed payment are different states. The person should not have to guess which one they are seeing. If there is an error, provide a clear next step without encouraging repeated submissions that could confuse the situation. Product copy should describe the actual state rather than offer reassurance unsupported by the transaction.

Words you can adapt

The example below illustrates the approach; it is not a customer message or testimonial. Change the details to match the actual situation. Keep the meaning accurate rather than copying a promise that does not fit your work.

A visually prominent button can make a checkout feel simple while the important information remains hard to read. Simplicity is not just fewer words. It is the ability to understand the decision without searching for hidden conditions or interpreting unfamiliar labels. A concise explanation in the right place can be more helpful than removing all context.

Try the approach on a real example

Use one real draft, page, or project from your own work for this review. Keep a copy of the original so you can compare it with the revision. The exercise is deliberately small: it should help you make a concrete decision, not turn into a complete redesign or a new obligation to publish every day.

First, write down who is arriving and what they already know. A regular follower and a first-time visitor may interpret the same sentence differently. Give the draft to someone who has not helped create it, or read it after stepping away for a while. Ask what the page appears to offer before explaining what you intended. That difference is often where the useful editing work begins.

Next, identify the one action or understanding the draft is meant to support. Underline the sentence that communicates it. If several unrelated requests compete for attention, decide which one belongs here and move the others elsewhere. Keep any relevant limits close to the invitation. A person should not have to discover a different meaning after following the link or sending a message.

Read every promise literally. Words such as always, immediate, exclusive, free, and guaranteed can create expectations that are broader than you intended. Replace them with a precise description where needed. Check names, dates, destinations, permissions, and any claim about a product against the actual current situation. A warm tone helps, but it cannot repair an inaccurate promise or a link to the wrong page.

Then inspect the material on a phone and without the surrounding conversation. Read the heading, caption, and main action in order. If an image carries an important detail, make sure the text explains it too. If the draft depends on an earlier post, add a short introduction or a relevant link. Someone encountering it through a share should not need a private explanation to understand it.

What to check afterward

Give a tester a specific task: identify the recipient and final amount without completing the payment. Then ask what the next button will do. If their answer differs from the intended action, the wording or hierarchy needs attention. Use test arrangements rather than unnecessary live payments when reviewing the flow.

Write down the outcome in plain language, including anything that remains uncertain. A useful review can end with a smaller change, a decision to wait, or a question that needs a better source. It does not have to end with a new post, a new tool, or a payment. Keep the lesson specific enough that you can use it the next time a similar situation occurs.