Set clear rules before customers pay.
Attach a waiver to any class and define exactly what happens when a customer cancels. The rules are shown up front, acceptance is recorded against the customer who books, and refunds are applied automatically, so nobody is surprised after the fact.
Best for: businesses that need accepted waivers and fair, automatic cancellation handling, without chasing paper forms or arguing over refunds.
No more paper forms or refund arguments.
Waivers printed on a clipboard get lost, never get accepted, or end up tied to the wrong person. Cancellation rules that live in your head, or only in your confirmation email, turn every late cancellation into a negotiation.
FullClass moves both into the booking flow. The waiver is attached to the class and must be accepted before checkout completes, and your cancellation policy is shown to the customer before they pay. When someone cancels, the policy decides the refund, not a back-and-forth email.
Tiered by hours before the event.
Set thresholds based on how many hours before the event a cancellation lands: a full refund early, a percentage refund closer in, and no refund inside your cutoff. Save the policy under a name and reuse it across as many classes as you like.
Whichever tier applies is snapshotted onto an append-only refund log, so you always have a record of which rule was in force when the cancellation happened.
Liability waiver
RequiredWaivers that stick and policies that enforce themselves.
- Versioned waivers. Each waiver carries a version, so updating the wording never rewrites what an earlier customer actually agreed to.
- Attached to your classes. Add a waiver to a class and it shows up in the booking flow for every session of that class.
- Acceptance required to book. Customers must accept the waiver during booking. The checkout will not complete without it.
- Recorded against the customer. Each acceptance is stored against the customer who agreed to it, with the version they accepted and the time they accepted it.
- Tamper-evident record. Every acceptance stores a SHA-256 hash of the exact waiver text that was shown, so you can prove what each customer agreed to.
- Reusable named policies. Build a cancellation policy once, give it a name, and apply it to as many classes as you need.
- Percentage refund tiers. Define full, percentage, or no-refund tiers based on how many hours before the event the cancellation happens.
- Gift card and card split. When a booking paid partly with a gift card is canceled, the gift-card portion goes back to the card and the rest to the original payment method.
- Shown before customers pay. The cancellation policy is presented in the booking flow, so the rules are clear before any money changes hands.
- Append-only refund log. Every refund records the policy tier that applied at the time, snapshotted so the history can't drift.
From acceptance to settled refund.
Attach a waiver and a policy
Write your waiver and set your cancellation tiers, then attach them to the class. Every session inherits them.
Customers see the rules and accept
During booking, customers read the cancellation policy and accept the waiver before they can pay.
A cancellation evaluates the policy
When a customer cancels in the portal, the policy is evaluated automatically and the right refund is recorded.
Or cancel from the admin
Admins can cancel a booking with a full, partial, or custom refund, and the applied tier is logged either way.
Let customers cancel themselves, within your rules.
Cancellations run through the passwordless customer portal. The customer requests a cancellation, the policy decides the refund automatically, and it's recorded: no email thread, no manual math, and no off-the-books exceptions.
Related features
Your first booking page is live in minutes.
Start taking bookings in minutes. Add the widget, API, gift cards, and policies when you are ready.
30-day free trial · Cancel anytime