| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Tip |
|---|
This feature is supported for: RTP|One only?? |
| Warning |
This feature is NOT supported for: {example 1} and {example 2} |
Key Terms
| Excerpt |
|---|
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. } |
...
Feature Description
Both Authorization Profiles in RTP and Resort Charge profiles in RTP|One are configured using the waiver module in Aspenware commerceCommerce. Within this module, you can create waivers that link to Authorization profiles in RTP, so that |One 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. . Many components within this module are configurable including:
Waiver text
RTP|One Authorization type code
Waiver validity dates
Credit card information collection with the waiver
Online signature
Waiver presentation in checkout (Consolidated vs. Independent)
Waiver availability in the My Account area of the e-commerce store.
Depending on the store setup, waiver signature can be saved to RTP|One 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. |One.
Section Links
| Child pages (Children Display) | ||
|---|---|---|
|
...