Page Comparison

Insert excerptWaivers (Standard and 1Risk)Waivers (Standard and 1Risk)nopaneltrue

Setup Checklist

Insert excerptSet-up ChecklistSet-up Checklistnopaneltrue

Setup Checklist

Prerequisite Tasks

1. POS Tasks

• The Authorization Type needs to be set up in RTP|One and you need to copy down the code. It should be set to active, ‘Display Online’ needs to be checked, a comment should be defined, the ‘Age Range’ should be set as ‘18-no maximum age’, the authorization text HTML should be configured, and the override security level should be set to 0.

• The Authorization Type needs to be assigned to the product component.

2. Infrastructure Tasks

• If lift access needs to be blocked before a waiver is signed, ask your Aspenware Representative about getting Aspenware’s Auto-Hotlist product installed in your environment.

• To support the wet-signature feature, RTP|One must be on v2016 or later.

3. Commerce Tasks

• Products need to be created in Aspenware Commerce. For help setting up products, see detailed instructions on setting up products.

4. Settings and Language Strings for this Feature

Settings

...

Info
NOTE: If a waiver is signed in My Account, it will always go to RTP|One

...

on the

...

signature

...

• Go to Configuration > Settings. Search for ‘WaiverSettings.SignWaiverDuringCheckOut’

  • If waiver signature should be stored at the time the waiver is signed on the personalize step of checkout to RTP|One, set the Value to ‘True.’

  • If waiver signature should be stored at the time of order completion to RTP|One, set the Value to ‘False.’ 

Info
NOTE: If a waiver is signed in My Account, it will always go to RTP|One on the signature.

...

.

• There are several settings that are used for configurable features listed below in the Detailed Setup Guide below. See the table below for reference regarding these settings.

Feature and Configuration Step	Setting	Value
4. Enable Waiver Signing in My Account	customersettings.hidewaiverstab	True/False - Shows and hides waiver signing in my account
5. Resort Charge in My Account	customersettings.hideresortcharge	True/False - Shows and hides resort charge in my account

Language Strings

• There are several language strings that are used for configurable features listed below in the Detailed Setup Guide below. See the table below for reference regarding these settingslanguage strings.

Language Strings

• There are several language strings that are used for configurable features listed below in the Detailed Setup Guide below. See the table below for reference regarding these language strings.

Detailed Setup Guide

...

1. Review Considerations Prior to Configurations

2. Configure New RTP|ONE Waiver (Release of Liability & Resort Charge)

3. Assign Waivers to Products

4. Enable Waiver Signing in My Account (Optional)

5. Enable Resort Charge in My Account (Option if using Authorize.net)

6. Configure Signature Panel Text

1. Review Considerations Prior to Configuration

...

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, set up resort charge waiver.  

...

Do you offer direct to lift products, or DTL products, that require a credit card on file to purchase? If so, setup the required resort charge/credit card 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? 

...

Detailed Setup Guide

1. Review Considerations Prior to Configurations

2. Configure New RTP|ONE Waiver (Release of Liability & Resort Charge)

3. Assign Waivers to Products

4. Enable Waiver Signing in My Account (Optional)

5. Enable Resort Charge in My Account

6. Configure Signature Panel Text

1. Review Considerations Prior to Configuration

• 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, set up resort charge waiver.  

• Do you offer direct to lift products, or DTL products, that require a credit card on file to purchase? If so, setup the required resort charge/credit card collection waiver. Consider that this functionality is not supported for all payment gateways. (Currently supported in RTP|One for Heartland and Payeezy if tokenized RTP|One, and Authorize.net if non-tokenized)

• 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? 

2. Configure New RTP|One Waiver (Release of Liability & Resort Charge)

1. Go to the Aspenware Commerce > Waivers.

2. Click Add Waiver to open the Add waiver page.

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

   1. Title: Enter the title of the waiver. This name will be visible to guests at checkout.

   2. RTP Authorization Type Code:

...

1. 1. 1. For a non-Resort Charge Waiver enter the POS Authorization Code

      2. For a Resort Charge Waiverenter 35735

   2. Collect CC Info: Check this box 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. This stores the credit card or tokenized credit card in RTP as the primary Credit Card Profile.

...

1. 1. Check this list to make sure that resort charge functionality is

...

1. 1. available for your payment gateway.

   2. CC Agreement Required: Check this box if the guest must sign the resort charge waiver and provide a credit card for storage. If unchecked the waiver is optional and just a checkbox. This feature is often used for direct-to-lift products that charge the guest automatically for every day of skiing. 

   3. E-Signature Required: Check this box to require the customer to type in the name of the assigned user before checking off the waiver checkbox during checkout.

   4. Enable Agree Checkbox: This enables/disables Agree Checkbox which enables a checkbox on the waiver allowing the guest to indicate that they agree with the terms of the release/waiver prior to signing. (See Figure D below.)

   5. Enable Wet Signature: The checkbox enables the capture and saving of a guest’s digital signature in their RTP|One authorization profile. (See Figures E and F below.)

   6. Capture Waiver HTML: This checkbox allows for the capturing of the waiver HTML will save the HTML for the waiver (including their signature) in their RTP|One Authorization Profile. (See Figure G below.)

   7. Display in My Account: Check this box if the waiver should be able to be signed within My Account. The setting “Validate Signature” must also be checked for this to function properly.

   8. Consolidate Release: Check this box if you want to allow for a consolidated view of the waivers during the personalization step in the store. (See Figures A, B, and C below.)

   9. Is Resort Charge Waiver: When checked the waiver will appear in the “Resort Charge” tab of My Account. Waiver appears on this screen when the guest makes a change to their credit card.

   10. Validate Signature: Check this box if you want Aspenware Commerce to check RTP|One for an existing waiver profile and mark already-signed waivers as 'signed.”

       1. To require customers to always sign (or resign) do not check Validate Signature. 

...

1. 1. 1. The setting “Display in My Account” must also be checked for this to function properly. If you do not want to show the waiver tab in My Account, ensure that the setting for “customersettings.hidewaiversigning” is set to True.

   2. Start Effective Date: Enter the date that indicates when the release or waiver is valid. Typically, this is set to

...

End Effective Date: Enter the date that indicates when the release or waiver is no longer valid. Typically, this is set to the season end date. (To test this feature, the date must be later than today’s date.)

...

Custom Comment: Can only be used on waivers that are not resort charge waivers. Options for custom comments include saving the Authorization Type Code {AuthTypeCode}, Signer Name {Signer}, Signed Date {SignedDate}, Browser Name {BrowserName}, and Brownser Version {BrowserVersion} Any words not in curly brackets will also show in the custom comments field. (See Figures H and I.)

...

Link Text: This text box is not used in the configuration.

...

1Risk ID: If configuring a 1Risk waiver please see the configuration instructions for 1Risk.

...

Text area: Enter waiver HTML in this field. To enter HTML, go to Tools > Source Code in the editor. A Source Code text box will appear. 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.

...

Click Save. 

...

1. 1. the season pass sales launch date. (To test this feature, the date must be earlier than today’s date.)

   2. End Effective Date: Enter the date that indicates when the release or waiver is no longer valid. Typically, this is set to the season end date. (To test this feature, the date must be later than today’s date.)

   3. Custom Comment: Can only be used on waivers that are not resort charge waivers. Options for custom comments include saving the Authorization Type Code {AuthTypeCode}, Signer Name {Signer}, Signed Date {SignedDate}, Browser Name {BrowserName}, and Browser Version {BrowserVersion} Any words not in curly brackets will also show in the custom comments field. (See Figures H and I.)

   4. Link Text: This text box is not used in the configuration.

   5. 1Risk ID: If configuring a 1Risk waiver please see the configuration instructions for 1Risk.

   6. Text area: Enter waiver HTML in this field. To enter HTML, go to Tools > Source Code in the editor. A Source Code text box will appear. 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. Click Save. 

...

Figure	Feature Description	Example (Click to Expand)
Figure A	Consolidate Releases: When Consolidate Releases is checked for a waiver, 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 that 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.	Image Modified
Figure B	Consolidate Releases: For the consolidated waivers, there is no signature box, as the signed-in user is signing for multiple participants.	Image Modified
Figure C	Consolidate Releases: The RTP|ONE Authorization Profile comment text shows the same information as it did previously for individually-signed waivers, with the signed-in user shown as ‘agreed for’ the other person.	Image Modified
Figure D	Enable Agree Checkbox: This enables the checkbox underneath the waiver that allows the guest to indicate that they are agreeing to the terms of the waiver/release before signing.	Image Modified
Figure E	Enable Wet Signature: This checkbox allows for the capture of a wet signature. When it is checked, the guest will see the signature box at right.	Image Modified
Figure F	Enable Wet Signature: When this checkbox is true, a guest’s digital signature will be stored in their RTP|One authorization profile. This figure shows how it will appear in RTP|One.	Image Modified
Figure G	Capture Waiver HTML: When this checkbox is true, Aspenware Commerce will capture the waiver HTML will save the HTML for the waiver (including their signature) in the guest’s RTP|One Authorization Profile.	Image Modified
Figure H	Custom Comment: If there are entries in this field, custom comments will be viewable in the guest’s authorization profile as shown.	Image Modified
Figure I	Custom Comment: This example shows the tokens entered in the Custom Comment field.	Image Modified

3. Assign Waivers to Products

1. Go to Aspenware Commerce > Waivers in Administration.

2. Click Assign Waiver to Products.
   

   Image Modified

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.

...

4. Enable Waiver Signing in My Account (Optional)

For resorts on RTP | One, waivers can be signed in my account. Guests can log in to the ecommerce site, go to My Account, and sign waivers for themselves and other members of their household without being required to check out.

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 | One as Authorization type profiles for the designated guest. See the Language Strings and Settings section above in this article for the specific strings and settings that should be set up and edited to turn on the feature and to customize copy on the waiver signing screen in My Account. 

5. Enable Resort Charge in My Account

...

The resort charge feature can be set up for households to manage in the store's My Account screen. Guests can log in to the ecommerce site, go to My Account and set up or edit resort charge for themselves and other members of their household without being required to check out.

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  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 set up for resort charge for the individual and household can be added and updated from this screen and RTP|One will be updated. If a household member is not set up 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. See the Language Strings and Settings section above in this article for the specific strings and settings that should be set up and edited to turn on the feature and to customize the copy on the resort charge screen in my account. 

Info
NOTE:  The resort charge feature in My Account is not supported for tokenized credit currently and only supported for Authorize.net. If Payeezy, Square or Braintree is your payment provider, this feature should not be enabled. payment gateways that support resort charge. Please see the list of payment gateway features to determine if this feature is available for your payment gateway.

6. Configure Signature Panel Text

Much of the text on the signature panel page is configurable using language strings. These strings are reference referenced above in the Setting and Language Strings section of this article. The red outlined areas in the sample waiver below show the areas that are configurable using these strings.

...

Insert excerptLike this Page ExcerptLike this Page Excerptnopaneltrue

...