...
The following matrix presents feature functionality for Aspenware Commerce Native Waivers vs 1Risk Waivers. Items bolded below are only possible with Standard (native) Waivers. See the 1Risk Waivers documentation for more on 1Risk Waivers (coming soon).
Functionality | Aspenware Commerce Native Waivers | 1Risk Waivers | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Stored in RTP|One |
|
| ||||||||||||
Stored in Sirisuware |
|
| ||||||||||||
Wet Signature |
|
| ||||||||||||
Integration with Aspenware Arrival |
|
(Pending future development) | ||||||||||||
Integration with Aspenware Resort Tools |
|
(Pending future development) | ||||||||||||
Customer required to sign a waiver within checkout flow |
|
| ||||||||||||
Customer able to sign a waiver after purchase complete |
(However, no option to “skip” waiver in checkout and sign it later, it’s either during checkout or after. Post checkout waivers presented through waivers in my account, Arrival or Resort tools) |
(However, no option to “skip” waiver in checkout and sign it later, it’s either during checkout or after. Post checkout waivers presented in confirmation email.) | ||||||||||||
Initialed Paragraphs |
|
|
Both Authorization and Resort Charge profiles in RTP|One are configured using the waiver module in Aspenware Commerce. Within this module, you can create waivers that link to Authorization profiles in RTP|One when guests check out. Many components within this module are configurable including:
...
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|One.
Section Links
| Child pages (Children Display) |
|---|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...