Configuration: Waivers

Setup Checklist

This section is a comprehensive and high level summary of all tasks and prerequisites required for this feature to function properly. This section is purposed for use after an administrator is familiar with configuring this feature as an “audit” checklist. For detailed set-up instructions, jump down to “Prerequisite Tasks” and “Detailed Setup Guide” and then follow up with this checklist to ensure all steps are completed.

Prerequisite Tasks

This section describes all requirements that must be completed before you can begin setting up this feature. Once these tasks are complete continue to the next section.

POS Tasks

• POS Task that must be completed first

Infrastructure Tasks

• Infrastructure Task that must be completed first. Remove section if not required

Commerce Tasks

• AW Commerce task that must be completed first

Settings, Language Strings and/or HTML Widgets for this Feature

This feature may require updates to the following settings, language strings and/or HTML Widgets. Learn more about how to update and create Settings, Language Strings, and HTML widgets follow the links to the respective section.

Settings

• AW Commerce Settings that must first be completed

Language Strings

• AW Commerce Language Strings that must first be completed

HTML Widgets

• AW Commerce HTML Widgets that must first be completed

Detailed Setup Guide

Waivers

Configuring New RTP Waiver (Release of Liability & Resort Charge)

Both Authorization Profiles in RTP and Resort Charge profiles in RTP are configured using the waiver module in Aspenware commerce. Within this module, you can create waivers that link to Authorization profiles in RTP, so that when guests check out their waiver will be stored in RTP as an Authorization profile. What is configurable is the waiver text, the RTP Authorization type code, the dates the waiver is valid for, whether the waiver also collects cc information, or requires cc collection (only used in the case of resort charge authorization type), whether it requires an online signature (type to sign), how the waiver is presented in checkout - as consolidated for the household or independent waivers for each guest - and whether the waiver can also be signed in the my account area of the ecommerce store. Depending on the store setup, waiver signature can be saved to RTP either when the guest completes the waiver or when the order is sent to RTP. Aspenware also supports integrations into 1Risk waivers in the checkout process. 

Considerations before beginning

• Are you going to require e-signature on all waivers, just some, etc. (Can be configured at waiver level)

• Do you want to store waivers immediately on signing? (only configurable at store level)

• Do you offer resort charge? If so, setup resort charge waiver.  

• Do you offer direct to lift products, or DTL products that require a cc on file to purchase? If so, setup required resort charge/cc collection waiver. 

• Would your legal team accept consolidated waivers where all waivers are signed by a single user? 

• If a waiver is already valid for a user at the time of purchase, do you want to require guests to sign again? 

• Would any waivers be helpful to offer signature in my account for - could be signed by any guest not just those purchasing a product? 

1. Before setting up specific waivers, decide whether waivers should be stored to RTP at the time of signature, or when the order is completed and sent to RTP. IF waiver signature should be stored at the time of signature, set the following setting. Navigate to Configuration > Settings. Search: WaiverSettings.SignWaiverDuringCheckOut and set to true. If waiver signature should be stored at the time of order completion to RTP, set this setting to false. 

   1. Note: If a waiver is signed in my account, it will always go to RTP on signature. 

2. Go to the Aspenware Commerce Plugins > Waivers

3. Click Add Waiver. 

4. Fill in the following fields (Optional fields are marked with an asterisk here) 

   1. Title - Title of waiver

   2. RTP Authorization Type Code

   3. Collect CC Info - Check if setting up a waiver that enables resort charge functionality, meaning the guest can enter a credit card to add to their access card to pay for purchases at the resort. 

      1. Note: Currently only supported for Authorize.net and tokenized Payeezy

   4. CC Agreement Required - Check this if a product is required to have resort charge. Often used for direct to lift products that charge the guest automatically for every day skiied. 

      1. Note: Currently only supported for Authorize.net and tokenized Payeezy

   5. E-Signature Required - Check to force customer to type in name of the assigned user before checking off the waiver checkbox during checkout

   6. Display in My Account - Check if waiver should be able to be signed within My Account. Full configuration guide for waivers in my account

   7. Consolidate Release - If checked, any products that use that waiver will show in a consolidated view on the personalization step in the store, 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. 

      1. Example of consolidated releases

   

1. Validate Signature - DO NOT USE UNTIL FIX FOR CHECKING EXPIRATION DATE IN PLACE

   1. To require customers to always sign (or resign) do not check “validate signature” 

   2. To have Aspenware Commerce check RTP for an existing waiver profile and mark already-signed waivers as signed, check “validate signature” 

   3. If a waiver is already signed and this is turned on for a waiver, this is what the personalize waiver signing step will appear like for a guest with a valid authorization profile.

1. Start Effective Date - to test, must be earlier than today’s date. 

2. End Effective Date -  to test, must be later than today’s date. 

3. Link Text - N/A

4. 1Risk ID - If configuring a 1Risk waiver see 1Risk waiver setup configuration guide

5. Text area - Enter waiver HTML here.

   1. To enter HTML, go to Tools> Source Code  in the editor. Paste waiver HTML in the Source Code text box. Entering HTML in the standard text box, and not within the Source code editor, will not display the authorization details on the site correctly.

1. Save the Waiver. 
   

   

Assigning Waivers to Products

1. Go to the Aspenware Commerce Plugins>Waivers page in Admin.

2. Click Assign Waiver to Products.

3. Select the waiver(s) that should be applied to each product from the Assigned Waiver drop down(s). Each product can be assigned up to four waivers. 
   If an add on product requires a separate waiver, then assign the add on product the desired waiver.

Waiver Signing in My Account

For resorts on RTP, waivers can be signed in my account. Guests can login to the ecommerce site, go to my account and sign waivers for themselves and other members of their household without requiring checkout

In the waiver plugin, waivers can be set to show in my account by checking “Display in My Account” when editing a waiver. If a waiver is set to show in my account, and is already signed by the household member, then the waiver will show as signed in my account, but if the waiver is not yet signed, waivers can be signed here and will be recorded in RTP as Authorization type profiles for the designated guest. The following settings and language strings should be set up and edited to turn on the feature and to customize copy on the waiver signing screen in my account. 

Resort Charge in My Account

For resorts on RTP and have Auth.net as a payment provider,  resort charge can be setup for households in my account. Guests can login to the ecommerce site, go to my account and setup resort charge for themselves and other members of their household without requiring checkout

In the waiver plugin, waivers can be set as “resort charge waivers” by checking both the “Is Resort Charge Waiver” and “Collect CC Info” settings when editing a waiver. 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. 

The primary credit card setup for resort charge for the individual and household can be added and updated from this screen and RTP will be updated. If a household member is not setup for resort charge, they can be toggled on for resort charge. This will both add the primary credit card to their profile and add the resort charge authorization type agreement to their profile. The following settings and language strings should be setup and edited to turn on the feature and to customize copy on the resort charge screen in my account. 

Note:  Resort charge in my accountis not supported for tokenized credit currently and only supported for Auth.net. If Payeezy, Square or Braintree is your payment provider, this feature should not be enabled. 

How to activate/inactivate waivers to be signed on personalization step

This setting will affect whether an authorization profile is created in RTP as soon as the waiver is signed (and prior to checkout/order processing). If using 1Risk waivers set this value to true

*Note: This setting applies to all waivers (even if using both 1Risk and Aspenware Waivers)

1. Navigate to Aspenware Commerce > Settings > Search “WaiverSettings.SignWaiverDuringCheckOut”

   1. To ensure an authorization profile is created during the personalization step: select “Edit” and set value to "True"
      
      

      

      
      

DELETE CONTENT AFTER THIS LINE

go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.

How-to Guide of this page can be found here: [Internal] Configuration page Setup Guide

Real Example of this page can be found here: https://aspenware.atlassian.net/wiki/spaces/DB/pages/edit-v2/1037172926