Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
[TEMPLATE] Feature Landing Page
[TEMPLATE] Feature Landing Page
nopaneltrue

Tip

This feature is supported for: {example 1}, {example 2}, and {example 3} RTP | One only??

Warning

This feature is NOT supported for: {example 1} and {example 2}

...

{Paragraphs, pictures, attachments, etc go here}

Feature Description

This section contains a paragraph or two describing the feature and how it enhances the functionality of Aspenware Commerce. Include here business use of the feature both from the resort perspective and from the guest perspective 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. 

Child pages (Children Display)
page[TEMPLATE] Feature Landing Page

...