This feature is supported for:
Standard Waivers: RTP|One POS
1Risk Waivers: Resorts that use either RTP|One or Siriusware and use 1Risk as their waiver management tool.
This feature is not supported for:
Standard Waivers: Siriusware POS
1Risk Waivers: Resorts that do not use 1Risk as their waiver management tool. Not recommended for resorts who use Aspenware Arrival or Resort Tools.
The following matrix presents feature functionality for Aspenware Commerce Native Waivers vs 1Risk Waivers. See the Aspenware Commerce Standard Waivers documentation for more on Standard Waivers.
Functionality | Aspenware Commerce Native Waivers | 1Risk Waivers |
|---|---|---|
Stored in RTP|One | AVAILABLE | AVAILABLE |
Stored in Sirisuware *NEW | NOT PRESENT | AVAILABLE |
Wet Signature *NEW | AVAILABLE | AVAILABLE |
Integration with Aspenware Arrival *NEW | 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 |
Use the links below to learn more about this feature and how it can be used at your resort.