Overview: Standard Waivers (inc. Resort Charge)
- Sarah Holst
- Jakub Swihart
- Jenni Buonanni
This feature is supported for: RTP|One
This feature is not supported for: Siriusware
Key Terms
Authorization Type
The Authorization Type is the name given in RTP|ONE to a specific waiver or release. This type is assigned a code and is then assigned to a product. Once a waiver is signed, it will be recorded in RTP|One as Authorization type profiles for the designated guest.
Consolidated Releases
Within Aspenware Commerce, this refers to the option to bundle all releases for a household into one place for signature to expedite the process for the guest. During the personalization step, any products that use that waiver will show in a consolidated view, so the logged-in user will be able to sign all waivers for all members in the cart at one time. If there are any products in the cart which have waivers which are not eligible for consolidation, those waivers will behave as they did previously, where each member shows as an individual row on the personalization step, and each of those waivers must be signed for each member.
Resort Charge
The option for collecting a guest’s credit card information and storing it for their use within the resort. If resort charge is already enabled for the household member, meaning they have both a primary credit card profile on their account or inherited to their account, and they have agreed to the resort charge authorization type, then the household will be toggled on for resort charge and the configured credit card will be displayed for the household. Please see Payment Gateways Overview for a list of gateways that currently support Resort Charge.
Signature Block Panel
This refers to the highly configurable block beneath the text of the release where the guest agrees to the terms of the release and adds their signature.
Wet Signature
This is the capture of a guest’s actual signature, as opposed to a typed entry of their name in the signature box.
Feature Description
The following matrix presents feature functionality for Aspenware Commerce Native Waivers vs 1Risk Waivers. Items bolded below are only possible with Standard (native) Waivers. See the 1Risk Waivers documentation for more on 1Risk Waivers (coming soon).
Functionality | Aspenware Commerce Native Waivers | 1Risk Waivers |
|---|---|---|
Stored in RTP|One | Available | Available |
Stored in Sirisuware | Not present | Available |
Wet Signature | Available | Available |
Integration with Aspenware Arrival | Available | Not present (Pending future development) |
Integration with Aspenware Resort Tools | Available | Not present (Pending future development) |
Customer required to sign a waiver within checkout flow | Available | Available |
Customer able to sign a waiver after purchase complete | Available (However, no option to “skip” waiver in checkout and sign it later, it’s either during checkout or after. Post checkout waivers presented through waivers in my account, Arrival or Resort tools) | Available (However, no option to “skip” waiver in checkout and sign it later, it’s either during checkout or after. Post checkout waivers presented in confirmation email.) |
Initialed Paragraphs | Not present | Available |
Both Authorization and Resort Charge profiles in RTP|One are configured using the waiver module in Aspenware Commerce. Within this module, you can create waivers that link to Authorization profiles in RTP|One when guests check out. Many components within this module are configurable including:
Waiver text
RTP|One Authorization type code
Waiver validity dates
Credit card information collected with the waiver
Online Signature
Waiver presentation in checkout (Consolidated vs. Independent)
Waiver availability in the My Account area of the e-commerce store.
Depending on the store setup, the waiver signature can be saved to RTP|One either when the guest completes the waiver or when the order is sent to RTP|One.