Content Comparison

...

• Before setting up specific waivers, decide whether waivers should be stored to RTP|One at the time of signature, or when the order is completed and sent to RTP|One. If the waiver signature should be stored at the time of signature, set the following setting:

  • 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.’ 

...

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: This is the code fromRTP|One.

   3. 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. Resort charge functionality is currently only supported for Authorize.net and tokenized Payeezy.

   4. 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. 

   5. 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.

   6. 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.)

   7. 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.)

   8. 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.)

   9. Display in My Account: Check this box if the waiver should be able to be signed within My Account.

   10. 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.)

   11. 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.

   12. 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. 

   13. Start Effective Date: Enter the date that indicates when the release or waiver is valid. Typically, this is set to the season start pass sales launch date. (To test this feature, the date must be earlier than today’s date.)

   14. 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.)

   15. Custom Comment: 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.)

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

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

   18. 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.

4. 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.
Figure B	Consolidate Releases: For the consolidated waivers, there is no signature box, as the signed-in user is signing for multiple participants.
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.
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.
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.
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.
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.
Figure H	Custom Comment: If there are entries in this field, custom comments will be viewable in the guest’s authorization profile as shown.
Figure I	Custom Comment: This example shows the tokens entered in the Custom Comment field.

3. Assign Waivers to Products

1. Go to Aspenware Commerce > Waivers in Administration.

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.

...