Check what “cancel anytime” means for your actual orders
Only if the promise identifies what can be canceled and the actual procedure supports that meaning at every stage it covers. Separate ending a recurring agreement from canceling an existing order, stopping fulfillment, canceling an incomplete payment and refunding a completed one. Compare the public wording with the merchant’s accepted procedure and the payment method’s supported actions. Narrow an overbroad claim before using it for new offers, and review existing promises against the policy and records that accompanied those orders.
For: A research-only merchant reviewing cancellation wording on product pages, recurring offers, checkout and policies.
Read the sentence where the buyer sees it, including the offer heading and the text around the cancellation claim. Identify whether it describes a recurring agreement, the next planned order, an order already accepted, or a payment. A broad promise can leave the buyer expecting all of those to stop even when the merchant’s intended procedure addresses only one.
If the store offers recurring supply, compare the published cancellation wording with the actual agreement and configured cancellation procedure. Record the effective event, any already-created order, and any payment already taken. Do not assume that ending future recurrence also reverses a current order. If there is no recurring agreement, remove subscription terminology from the explanation rather than borrowing a subscription policy for a one-time sale.
Walk the claim through the stages the business actually reaches
For each covered offer, identify the real stages at which the business receives a cancellation request: before payment completes, after payment but before fulfillment, and after goods have been handed off. At each stage, record the action staff can perform and the evidence that confirms it. Use the store’s real workflow; a stage that does not exist in that workflow should not become an invented policy condition.
Check the request route as well as the eventual action. A route that accepts messages at any time does not demonstrate that an order can be stopped at any time. Record who can act, which order stage they must check, and how they confirm the result to the buyer. Where fulfillment is controlled by another party, use the actual handoff procedure to establish what can still be stopped instead of treating an internal status edit as that confirmation.
Describe the payment action separately
Stripe’s refund documentation distinguishes cancellation of an incomplete payment from a refund after a payment succeeds. Refunds go back to the original payment method. Some early refunds appear as reversals, where the original charge disappears instead of a separate credit appearing. These distinctions mean that a promise to cancel an order should explain the applicable money-handling process without implying every payment can simply be undone in the same way.
The buyer’s bank display is a separate outcome. Do not make instant arrival part of an unrestricted cancellation assurance just because staff can submit a refund promptly. Stripe also documents that cancellation of a refund itself depends on the refund type and state; it is not an unlimited undo function. Use the real provider’s rules for the actual method, and leave a missing procedure unresolved rather than publishing an unsupported capability.
Make the public scope match the accepted procedure
The FTC’s truth-in-advertising guidance requires truthful, nonmisleading and substantiated advertising across media. Apply that principle to the whole offer: the headline, nearby conditions, policy page and checkout should describe the same cancellation scope. If the accepted procedure ends future orders but leaves an existing paid order to a separate decision, the short claim should preserve that distinction. If a promised stage cannot be supported, the merchant must resolve the procedure or correct the offer; this worksheet does not decide which obligations the business may change.
Keep the prior wording and the policy version attached to existing orders. Changing the public page does not establish what was promised earlier or settle an outstanding cancellation request. For a Prism website-review consultation, bring the affected public URLs, recurring-offer terms if applicable, and a nonsensitive stage map of the accepted procedure. The consultation sets the pages, questions and deliverables; legal obligations and payment-provider decisions remain with the appropriate advisers and provider.
Cancellation-promise scope
Use one actual offer and repeat the comparison for each order stage its promise covers. Write only supported procedure in the final column. An unsupported stage requires a merchant decision about the offer or procedure; a page edit alone does not resolve earlier promises or existing requests.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Cancellation-promise scope. The last column is for temporary notes.
Scope to check
Records to compare
Question the comparison must answer
Your finding or correction
Promise text
Records to compareExact wording and surrounding offer text from the product page, recurring offer, checkout and policy.
Question the comparison must answerWhat would the buyer understand can be canceled, and are the public versions consistent?
Recurring agreement status
Records to compareActual agreement, recurrence status, effective cancellation rule and any order already created.
Question the comparison must answerDoes the action stop future recurrence, affect an existing order, or require separate actions? Mark not applicable where no recurring agreement exists.
Before payment completion
Records to compareReal order stage and the provider-supported action for the incomplete payment.
Question the comparison must answerCan the merchant perform the claimed cancellation at this stage, and which record proves the result?
After payment, before handoff
Records to compareAccepted order procedure, provider payment status and the staff member authorized to act.
Question the comparison must answerDoes the process require a refund, and does the public explanation accurately distinguish it from canceling an incomplete payment?
After fulfillment handoff
Records to compareActual fulfillment record and agreed stop, return or other applicable procedure.
Question the comparison must answerCan the merchant still do what the promise says, or is a different order resolution required? Do not infer a stop from a store label.
Actual request procedure
Records to comparePublished contact route, responsible team, stage check and result-confirmation process.
Question the comparison must answerDoes accepting a request get confused with completing the cancellation?
Policy correction
Records to compareSpecific unsupported wording, proposed scope and merchant approval for publication.
Question the comparison must answerDoes the revised claim preserve the conditions buyers need at the point of the offer?
Earlier orders
Records to compareArchived offer and policy version associated with already accepted orders.
Question the comparison must answerWhich prior wording must be considered separately from the revised offer and any open request?
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
This comparison does not establish statutory cancellation rights, a lawful cutoff, or permission to change terms for existing orders. FTC guidance does not approve a particular phrase.
No subscription platform’s cancellation behavior is assumed. Use the actual agreement, configuration and provider documentation for the offer being reviewed.
Stripe payment and refund actions are specific to Stripe and the actual payment method and state. They do not establish fulfillment cancellation or research-only merchant eligibility.
Keep customer records, card data, bank details, credentials and private payment links out of the worksheet and public consultation form.
FTC truth in advertising — checked 2026-09-28. Advertising must be truthful, nonmisleading and substantiated across media, including the web. This supports comparing a public cancellation assurance with its evidence, not declaring a phrase legally sufficient.
Stripe refunds — checked 2026-09-29. Stripe distinguishes canceling incomplete payments from refunding successful payments to the original method. Early refunds can appear as reversals; bank display varies. Canceling a refund depends on type and state. These facts do not decide a store’s order or subscription cancellation procedure.
Prism features — checked 2026-09-21. An agreed website review can examine policies, marketing claims and differences between public pages and checkout. Findings are informational, not legal certification or processing approval.