This feature is supported for: RTP | One only??
This feature is NOT supported for: {example 1} and {example 2}
Key Terms
Key Term 1
{1-2 sentence definition. Confirm that key term is not defined in another section first. }
Key Term 2
{1-2 sentence definition. Confirm that key term is not defined in another section first. }
{Paragraphs, pictures, attachments, etc go here}
Feature Description
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.
Section Links
Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.