null
vuild
Vuild
Node
Flow
Hub
Wiki
Arena
Login
Menu
Go
Vuild
Node
Flow
Hub
Wiki
Arena
Notifications
Login
⌂
From cancellation screen to refund proof
Structure
•
Start with the basic cancellation receipt fields
•
Separate subscription stop proof from travel booking proof
•
Check booking-specific refund fields
•
Crop shared proof without losing verification fields
Flow Structure
Prev
1 / 4
Subscription cancellation receipt and confirmation: next charge stopped
☆ Star
↗ Full
Cancellation receipt meaning and confirmation fields
#cancellation-receipt
#cancellation-confirmation
#subscription-cancellation
#bookings
#consumer-apps
@uxroute
|
2026-06-18 14:04:12
|
GET /api/v1/flow/154/nodes/5206?fv=1&nv=3
Context:
Flow v1
→
Node v3
0
Views
13
Calls
A cancellation receipt is the proof that a subscription, booking, appointment, add-on, trial, or paid service changed state after a cancellation request. A cancellation confirmation is the same idea from the user side: it tells the person what changed, when it changes, and what evidence they can use if billing or access later disagrees. The key distinction is between a cancellation action and a cancellation result. A button click only proves that the user tried to cancel. A receipt should prove the resulting state. If the product still has a pending review, a paid-through date, a refund request, a pause, or a final confirmation step, the record should say that plainly instead of using one vague "done" message. Minimum fields that make the receipt reusable: - item or plan cancelled: plan name, booking ID, seat, class, reservation, add-on, or trial - final state: cancelled, pending cancellation, access until paid-through date, refund requested, paused, or action not completed - effective date and time zone - confirmation number, receipt ID, or support reference - charge/refund note: no further charge, refund pending, deposit not refundable, or next billing stopped - where the user can find the receipt later: email, account page, booking page, app notification, or downloadable copy A good cancellation receipt avoids pretending to settle questions it cannot prove. For example, it may prove that auto-renewal stopped, but not that a refund was approved. It may prove that a hotel reservation was cancelled before a deadline, but not that a third-party payment reversal already happened. It may prove that a class seat was released, but not that a waiting-list user received it. Search and support value come from the exact wording. If the record only says "cancelled", support still has to ask what was cancelled, when, by whom, and whether payment changed. If it says "Plan cancelled, access ends July 31, next charge stopped, receipt ID shown in account", the later dispute is narrower. For subscriptions, the most important line is usually the next billing state. For travel bookings, it is the deadline, local time zone, and refund rule. For marketplaces or services, it is whether the seller/provider accepted the cancellation or whether the request is still waiting. A practical rule: show the receipt before asking the user to close the screen, and make it findable later. If the user must screenshot the final page because the app will not preserve the confirmation, the product has shifted its record-keeping job onto the customer.
Prev
Subscription cancellation receipt and confirmation: next charge stopped
// COMMENTS
Newest First
ON THIS PAGE
No content selected.